Enable Lambda scope + bump tofu-modules to v4.5.2#7
Merged
Conversation
added 2 commits
June 23, 2026 17:54
- iam: separate the build workflow user into the build-user module and grant S3 publish permissions via s3-assets; ecr now receives build_workflow_group_name and the build credentials come from build-user (tofu-modules v5 layout) - bindings: register the S3 asset repository (asset/s3, bucket lambda-files-aws-services) and the AWS IAM provider (identity-access-control) that publishes the lambda assume-role by selector - agent: add lambda:GetFunction / EnableReplication* so CloudFront can validate Lambda@Edge function associations - scope config: add a Lambda@Edge function association (viewer-response) to the static-files scope configuration Note: tofu-modules refs point to the feature branch (feat/separate-build-user-from-asset-repositories); update to the released tag once nullplatform/tofu-modules#402 is merged.
- Bump all tagged tofu-modules refs (v4.3.0/v4.5.1) to v4.5.2; feature-branch refs left untouched - Add scope_configuration_lambda module in nullplatform layer (placeholder image + state bucket) - Remove extra_envs (ASSUME_ROLE_ARN_DEFAULT, PLACEHOLDER_IMAGE_URI_DEFAULT) from agent module; now provided via lambda scope-configuration - Run tofu fmt -recursive
agustincelentano
changed the title
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
aws-servicescluster (scope, S3 assets, Lambda@Edge).nullplatformlayer: placeholder image URI (235494813897...latest-amd64) + tofu state bucket.extra_envs(ASSUME_ROLE_ARN_DEFAULT,PLACEHOLDER_IMAGE_URI_DEFAULT) — now provided through the scope-configuration.tofu-modulesrefs (v4.3.0/v4.5.1) to v4.5.2. Feature-branch refs (feat/separate-build-user-from-asset-repositories) left untouched on purpose.tofu fmt -recursive.Applied
All three layers applied against the
Implementationsaccount (235494813897):infrastructure/aws— 3 changed (agent + base helm releases + tools namespace).nullplatform— scope_configuration_lambda created; bump = no further changes.nullplatform-bindings— recreated a zombieaws-iam-configurationprovider config (was 404 in the platform, removed from state and re-added); bump = no further changes.Notes
infrastructure/awshelm releases showsvaluesas(sensitive value)in the plan, so the per-key diff isn't visible — non-destructive (0 destroy).🤖 Generated with Claude Code