Skip to content
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

Error: Error asking for state migration action: input is disabled #13

Open
geftactics opened this issue Jun 5, 2020 · 0 comments
Open

Comments

@geftactics
Copy link
Contributor

geftactics commented Jun 5, 2020

Seeing the above error, when I try and prep a second environment...

Steps to reproduce:

AWS_PROFILE=default ENV=prod REGION=eu-west-1 gmake prep

All looks ok at this stage, I can see S3 bucket created, and has an empty .tfstate file. We then move to prep the next environment...

AWS_PROFILE=default ENV=staging REGION=eu-west-1 gmake prep

During this run we see error mentioned in the subject. We can see S3 bucket for staging has been created, but is empty, and oddly, my prod s3 state bucket appears to have my staging .tfstate file in there.

If I edit the terraform init command that is being run to have input=true... We see the following:

Initializing the backend...
Backend configuration changed!

Terraform has detected that the configuration specified for the backend
has changed. Terraform will now check for existing state in the backends.


Do you want to migrate all workspaces to "s3"?
  Both the existing "s3" backend and the newly configured "s3" backend
  support workspaces. When migrating between backends, Terraform will copy
  all workspaces (with the same names). THIS WILL OVERWRITE any conflicting
  states in the destination.

  Terraform initialization doesn't currently migrate only select workspaces.
  If you want to migrate a select number of workspaces, you must manually
  pull and push those states.

  If you answer "yes", Terraform will migrate all states. If you answer
  "no", Terraform will abort

This is terraform v0.12.26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant