feat(self-improving-mastra): explicit per-cloud models (GLM 5 / Gemini 3.5 Flash)#651
Merged
Merged
Conversation
…i 3.5 Flash) Replace the chat-default alias with explicit model IDs in the committed env files: - AWS: CHAT_MODEL=zai.glm-5 (z.ai GLM 5; GA on Bedrock, available in us-east-1) - GCP: CHAT_MODEL=gemini-3.5-flash (GA on Vertex AI) Refresh the README model references to match. GCP caveat: Gemini 3.x is served via Vertex's global endpoint and is not offered on-demand in every region (europe-west2 is provisioned-throughput only). Defang sets VERTEXAI_LOCATION to the compute region for explicit models (only the chat-large alias forces global), so the GCP deploy needs a location that serves gemini-3.5-flash: a full on-demand region, or a CLI change routing gemini-3.x to the global endpoint. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #648.
What
Switches the sample from the
chat-defaultalias to explicit per-cloud model IDs in the committed env files:CHAT_MODELzai.glm-5bedrock/zai.glm-5(z.ai GLM 5)gemini-3.5-flashvertex_ai/gemini-3.5-flashREADME model references updated to match.
Validation
us-east-1(theawsstack region).zai.glm-5is also Defang's existingchat-largemapping, so the LiteLLM gateway path (bedrock/zai.glm-5) is already exercised.docker compose configresolves the top-level model correctly for both stacks.gemini-3.5-flash(GA) is served through Vertex's global endpoint and is not offered on-demand in every region —europe-west2(the sample's GCP region) only offers Single-Zone Provisioned Throughput for it. Defang's CLI setsVERTEXAI_LOCATIONto the compute region for explicit models (only thechat-largealias forcesglobal, seefixup.go), so this GCP change won't deploy on-demand as-is.Options:
us-central1).gemini-3.xmodels to theglobalVertex endpoint (generalize the existingchat-largespecial-case).AWS is unaffected and ready.
🤖 Generated with Claude Code
Samples Checklist
✅ All good!