gcp bucket names must be globally unique about pcf-pipelines HOT 6 CLOSED

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

from pcf-pipelines.

This might instead have to do with failure to roll back

from pcf-pipelines.

from pcf-pipelines.

Yep, that should be a CHANGEME.

from pcf-pipelines.

Actually, I was thinking it was for something else.

terraform_prefix is something that's used as a prefix for all of the resources that are managed by Terraform. It has nothing, or should have nothing to do with a GCP bucket name.

Your error is due to something else. I just did a lot of fixes to the GCP pipeline; I'll ask you to update and re-run it and see if you still have the problem. I'll close this issue for now; if it's still a problem for you please re-open it.

from pcf-pipelines.

Also, the rollback job has been removed from the pipeline and the state is handled in a different way than previously. If you put the file in your S3 bucket at the root (instead of in the bucket/terraform folder), and rename it to terraform.tfstate (no version), it should pick it up automatically and allow you to run create-infrastructure again.

from pcf-pipelines.