Disable v2 APIs by default (configurable) #1212
Merged
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.
Link(s) to Jira
Description of Intent of Change(s)
By default, we'll disable v2 APIs, with the ability to enable them through deployment configuration in order to prevent access prior to full production availability and support.
In stage we'll also want to configure this to set it on via param.
Local Testing
Locally, you'll need to set your
.env
want to setV2_APIS_ENABLED=True
in order to exercise v2 APIs locally.Checklist
Secure Coding Practices Checklist Link
Secure Coding Practices Checklist