Repository navigation
[BREAKING][CDTOOL-1830 Add support for AI Firewall configurations - #886
Merged
Merged
Conversation
rcaril
commented
Oct 16, 2026
Member
Author
|
Adding both @kpfleming and @anthony-gomez-fastly as this is a breaking change. |
rcaril
commented
Oct 16, 2026
rcaril
commented
Oct 16, 2026
Not needed since we are auto-paginating.
kpfleming
requested changes
Oct 16, 2026
kpfleming
left a comment
Member
There was a problem hiding this comment.
Some small changes, along with the change from Failover to FailoverPolicy, but overall this looks very good!
kpfleming
approved these changes
Oct 19, 2026
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.
Change summary
This PR the AI Runtime Control packages in line with the latest AI Firewall release. Internal references linked here.
Virtual keys
tokens-per-minute limits, and a spend limit.
GetFailoverandUpdateFailoveroperations manage a key's failover policy.Rotateno longer requires an expiration. If omitted, the rotated key doesn't expire.Provider connections
GetBedrockSetupandGetVertexSetupoperations return the values needed toconfigure the cloud-side trust before creating those connections.
Sessions and usage metrics
requested before any failover.
Listnow pages through all results automatically, like the other listoperations.
All Submissions:
New Feature Submissions:
Changes to Core Features:
User Impact
Users can now manage Virtual Key security, rate limits, spend limits, and failover policies, and can create Bedrock and Vertex AI provider connections.
Are there any considerations that need to be addressed for release?
The following are breaking changes:
usagemetrics.Listnow returns[]UsageMetricinstead of*UsageMetrics.key.CreateInput.UserIDhas been removed.key.Rotateno longer requiresExpiresAt, and leaving it out clears the key'sexpiration.