Skip to content

CCM-17830: Double PROD rate limits #1068

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.

Sign up for GitHub

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

Open
lapenna-bjss wants to merge 1 commit into
base: release
Choose a base branch
from
Open

CCM-17830: Double PROD rate limits #1068

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions manifest_template.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ APIGEE_ENVIRONMENTS:
- name: prod
display_name: Production
approval_type: manual
global_quota: '12000'

@markpullan markpullan Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we change the defaults so that production is considered the default setup, and non-prod environments are a conscious deviation away from our prod config?

(Achieves the same goal, but aligns better to the philosophy of treating production as the standard and every deviation from prod as the special case, rather than prod itself being a special case)

global_ratelimit: '36000pm'
---
meta:
api:
Expand Down
Loading