Skip to content

Out-of-order dependencies issues with A-VALID-PROJECT-ID in bootstrap #935

Open
@eeaton

Description

@eeaton

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 create A-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

n/a

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogdocumentationImprovements or additions to documentationtriagedScoped and ready for workv5.0

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions