Repository navigation
release: 0.3.0 - #131
Open
tarannum-2002 wants to merge 17 commits into
Open
release: 0.3.0#131tarannum-2002 wants to merge 17 commits into
tarannum-2002 wants to merge 17 commits into
Conversation
Publish catalogs now name the BPP that serves them, and every transaction call (select, init, support, status) carries bppUri in its context so the request can be routed to that BPP. Both come from variables, never hardcoded hosts.
#121] The quick-start registry runs with authentication_enabled=false and the stack ships no Keycloak, so the token request could never succeed and the Bearer header on the writes carried nothing.
The two local environments differed in only two adapter URLs, so one API environment now covers single mode, with the multi-mode values in the descriptions and README. The registry collection shares just registry-host with it, so it gets its own file. registry-token, schema-name, schema-url and ticket-no are dropped from the environments: the scripts set them as collection variables, and an environment value, even an empty one, shadows those, so the token and ticket number never reached the next request.
…d status [#121] Matches the PMFBY folders, which are already named after the action they call.
…#121] The negative cases are not needed in the collection. The README request count is corrected to 38.
feat: add bppId and bppUri to the API collection and tidy its environments [#121]
feat: catch the DSS chart up with the app, and add a Photon chart
feat: add charts for the experience API and UI
feat: one chart per product, with everything it needs under it
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Everything on
release-0.3.0thatmaindoes not have: 17 commits, 136 files.mainis not ahead, so nothing is lost.What
charts/decision-support-system0.1.0 to 0.2.0, matching what DSS v0.2.0 reads: the model gateway, provider preferences, place search, schemes, redaction and translation settings, and traces.charts/photon, the place search DSS uses for names it does not know.charts/experience-apiandcharts/experience-ui, the chat API and its web client.charts/langfuse2.2.0 to 3.0.0 now carries its own Postgres and MinIO.charts/lite-llmbecomescharts/litellm0.2.0, with its own Postgres.bppIdandbppUriand tidier environments (feat: add bppId and bppUri to the API collection and tidy its environments [#121] #124).Why
Dev and staging deploy from
main, so the DSS, Photon, Experience, Langfuse and LiteLLM Applications that infra-automation now has (#30, #31, #32) can only find their charts once this is released.Testing
charts/lite-llm.Relates to OpenAgriNet/engineering-tracker#233