[Feature] UI - Config Guardrails should not be editable and guardrail info fix #16142
+200
−4
Conversation
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
…ition location fix
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
ishaan-jaff
requested changes
Oct 31, 2025
| raise HTTPException(status_code=500, detail="Prisma client not initialized") | ||
|
|
||
| try: | ||
| guardrail_definition_location = "db" |
There was a problem hiding this comment.
bro please have this be a literal. Do we not already have a literal for db/config
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.
Config Guardrails should not be editable and guardrail info fix
Relevant issues
This PR implements a feature on the front end to prevent users from being able to enter the edit page for a guardrail defined in the config file. Trying to edit a config guardrail will always result in an error. This also implements a fix on the back end where /guardrails/{guardrail_id}/info always returns
guardrail_definition_location = "config"Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🆕 New Feature
🐛 Bug Fix
✅ Test
Changes
Screenshot