Skip to content

Deployment state bucket will conflict if used elsewhere #1

Description

@cdriehuys

The deployment tool has a goal of being portable(-ish) but currently hardcodes the name of the bucket to store deployment state in. It should be configurable during the bootstrapping process.

Caveats

  1. If configurable, it becomes much easier to accidentally separate deployment states and end up with deployments from different machines "fighting" each other.
  2. We need some way to pass the state bucket to our Terraform configurations. Perhaps omitting the backend configuration from our Terraform files and creating an environment-specific backend.tf file during the deployment process could solve this.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions