We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootstrapping includes a lot of manual steps. Improving backend.tf and GCS bucket management will improve it significantly!
No response
Current advice from the official docs (see here) includes a snippet to bootstrap the initial remote state bucket nicely (see code here).
This repo advises for manual renaming and editing in README-GitHub.md of backend.tf.example.
Any reasons to not update to the proposed local_file approach?
Is there interest in developing this (relatively simple change) internally, or will a PR be considered for acceptance?
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
Sorry, something went wrong.
No branches or pull requests
TL;DR
Bootstrapping includes a lot of manual steps. Improving backend.tf and GCS bucket management will improve it significantly!
Terraform Resources
No response
Detailed design
Current advice from the official docs (see here) includes a snippet to bootstrap the initial remote state bucket nicely (see code here).
This repo advises for manual renaming and editing in README-GitHub.md of backend.tf.example.
Any reasons to not update to the proposed local_file approach?
Additional information
Is there interest in developing this (relatively simple change) internally, or will a PR be considered for acceptance?
The text was updated successfully, but these errors were encountered: