feat: select remote state backend - #2
Merged
Conversation
Contributor
OpenTofu TestOpenTofu test passed. View run output |
Contributor
OpenTofu PlanOpenTofu plan passed. View run outputNo changes. Your infrastructure matches the configuration.
OpenTofu has compared your real infrastructure against your configuration and |
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.
Summary
Select the applied
tfroot-awsTwilio state backend: configure the S3 backend with native locking, route CI through the dedicatedgithub-actions-twilio-stateOIDC role, and retain the no-provider/no-resource boundary.Fixes # N/A — validates the consumer half of the encrypted backend prerequisite before any Twilio credential, provider, phone-number, or webhook work.
Type of change
Validation
opentofu / testandopentofu / planpassed. The plan successfully initialized the dedicated backend under the scoped OIDC role and reportedNo changes.No local OpenTofu, Makefile, SOPS, state, import, plan, or apply operation was run. GitHub Advanced Security secret scanning is unavailable; the narrow diff was manually inspected and contains no credentials, decrypted values, tokens, state, or sensitive plan output.
Impact and rollout
Producer:
tfroot-awsPR #43 merged at5faa314d, and its main apply succeeded. It owns the dedicated private/versioned/encrypted state bucket and exact-repository OIDC role.Consumer: this root uses the existing
shared-workflowsaws-role-to-assumeinput; no shared-workflow contract changes. Its Makefile selects S3 native locking and removes the bootstrap-backend=false/-lock=falsebehavior. The PR deliberately leaves the Twilio provider unconfigured and adds no encrypted file, provider credential, resource, phone number, webhook, bridge credential, runtime map, allowlist, GitOps workload, Cloudflare route, or public endpoint.A confirmed merge submits the environment-gated main apply, which initializes the remote backend under the dedicated role. That is state-backend selection only, not Twilio provider activity. Rollback is a reviewed revert to backend-free initialization; the producer bucket is intentionally retained and protected by
prevent_destroy.Safety and secrets
AI agent materially produced this change; reviewers should confirm the exact OIDC-role input, native S3 locking, no static AWS credential path, and retained absence of any Twilio provider configuration or resource.