Prepare simulation gateway auth enforcement#471
Merged
Conversation
This was referenced Apr 29, 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.
Fixes #470
Summary
Prepare
policyengine-api-v2to safely enable simulation gateway auth enforcement.Current
mainalready contains the gateway-side auth dependency and the explicitGATEWAY_AUTH_REQUIREDflag, but it was still missing the CI/test/deploy plumbing needed to actually flip that flag on without breaking deploys.Changes
client_credentialstoken in integration CI and export it assimulation_integ_test_access_tokenGATEWAY_AUTH_CLIENT_IDandGATEWAY_AUTH_CLIENT_SECRETthrough the reusable deploy workflow where neededRollout
GATEWAY_AUTH_REQUIRED=1in thebetaenvironment and verify deploy + integration + auth smoke are green.GATEWAY_AUTH_REQUIRED=1inprodafter beta is green.Validation