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.
fix(sluice): use virtual key for deploy smoke #135
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
fix(sluice): use virtual key for deploy smoke #135
Changes from all commits
a0f4abeFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When prod runs in the default Entra mode, this wires the BFF's
LITELLM_GATEWAY_KEYto thedashboard-playgroundvirtual key instead of the master key. The dashboard admin page is restricted todashboard.adminbut its key explorer calls/key/listthroughdashboard/hooks/use-keys.ts; LiteLLM documents the master key as the Proxy Admin key (https://docs.litellm.ai/docs/proxy/virtual_keys), while the generateddashboard-playgroundkey inscripts/keys.yamlonly has model/budget limits. As a result, signed-in admins will no longer be able to list/manage gateway keys through the Entra dashboard and will fall back to seeing only that virtual key or a permission error. Keep the admin BFF path on the master/admin credential, or split playground/smoke traffic onto the virtual key separately.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win
Fix "Index out of bounds" evaluation error.
When a secret name is provided but
auth_modeis not"entra", the ternary conditionlocal.gateway_proxy_key_secret_name != ""will evaluate totrue. This causes Terraform to evaluatedata.azurerm_key_vault_secret.gateway_proxy_key[0]. Sincelocal.use_entraisfalse, the data sourcecountis0, causing an immediate "Index out of bounds" failure during plan/apply.Check the length of the conditionally created data source array instead.
🐛 Proposed fix
📝 Committable suggestion
🤖 Prompt for AI Agents