fix(iam): apply provider.rolePermissionsBoundary to ApigatewayToStepFunctionsRole#721
Open
fix(iam): apply provider.rolePermissionsBoundary to ApigatewayToStepFunctionsRole#721
Conversation
…unctionsRole The auto-generated ApigatewayToStepFunctionsRole did not inherit provider.rolePermissionsBoundary, causing role creation to fail in environments that enforce a permissions boundary policy. Apply it alongside the existing provider.iam.role.path handling. Fixes #395 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
commit: |
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
1 participant
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.
Summary
ApigatewayToStepFunctionsRoledid not inheritprovider.rolePermissionsBoundary, causingiam:CreateRoleto fail in environments that enforce a permissions boundary policycompileIamRole.js) already handled this correctly; this bringsapiGateway/iamRole.jsin line with the same behaviourprovider.iam.role.pathpattern already present in the same fileTest plan
should apply provider.rolePermissionsBoundary to API Gateway IAM role— confirmsPermissionsBoundaryis set on the generated rolenpm test— 498 passingCloses #395
🤖 Generated with Claude Code