feat: authenticate Twilio provider from SOPS - #4
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
Configures the pinned Twilio provider to consume its existing encrypted account credentials only through SOPS process-environment injection. The root still declares no Twilio resource.
Fixes # N/A — validates live provider authentication before any phone-number inventory or inbound webhook change.
Type of change
Validation
opentofu / testandopentofu / planpassed. The credentialed plan initialized the remote backend, completed the provider's default credential validation through SOPSexec-env, and reportedNo changes.No local OpenTofu, Makefile, SOPS, state, import, plan, or apply operation was run.
Impact and rollout
Producer: merged credential delivery at
e325cba5supplies the only permitted SOPS ciphertext. Consumer: this PR adds an emptytwilioprovider block and runs OpenTofu itself insidesops exec-env; credentials remain absent from provider configuration, source, runner files, and GitHub Actions secrets. The existing runner and reusable workflow contracts already supply SOPS, jq, and the exact-repository AWS KMS role.The provider's default credential validation is enabled and passed during PR CI. No Twilio resource is declared, so neither stage can purchase a number, configure a webhook, alter messaging, or change the bridge. The documented pilot remains one future number per primary agent with an initially single, later-extensible sender allowlist owned by
kustomize-cluster; this PR does not select or deploy it. Rollback is a reviewed revert to the prior no-provider state; encrypted ciphertext remains protected by the existing KMS recipient in Git history.Safety and secrets
GitHub Advanced Security secret scanning is unavailable for this repository; the changed source was manually reviewed. AI agent materially produced this change; reviewers should confirm SOPS process-scoped provider authentication, the retained no-resource boundary, and the absence of bridge/runtime ownership crossover.