-
Notifications
You must be signed in to change notification settings - Fork 725
New issue
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
Out-of-order dependencies issues with A-VALID-PROJECT-ID
in bootstrap
#935
Comments
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 |
Hi, some triage to help out with initial project creation. A bootstrap project (before usage of this terraform landing zone) is useful to derive the billing and organizations id's as well. create project example
an evolving day0 example is in #940 |
TL;DR
https://github.com/terraform-google-modules/terraform-example-foundation/blob/44d51df886e165098ebbd13a02ac1b26ac9c2b6e/0-bootstrap/README.md
Written employment instructions in the bootstrap stage recommend use of
A-VALID-PROJECT-ID
as a billing and quota project for the terraform validator. This is poor usability and out-of-order dependencies, because the blueprint is intended for new environments that don't have existing projects, and does not have any prior instructions to manually createA-VALID-PROJECT-ID
.Expected behavior
If I follow the deployment instructions in a new environment, there should not be assumptions or dependencies about pre-existing resources in my environment. Where those dependencies are necessary, they should be enumerated as mandatory steps in the Prerequisites section.
Specifically, commands for terraform validator with
A-VALID-PROJECT-ID
should reference project IDs that have already been created somewhere in the instructions.Observed behavior
Following the flow as a greenfield customer, no projects have been created yet. I have to manually create a project and associate billing in a way that is not addressed in the deployment instructions.
Terraform Configuration
n/a
Terraform Version
Additional information
No response
The text was updated successfully, but these errors were encountered: