-
Notifications
You must be signed in to change notification settings - Fork 158
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
Failed to get existing workspaces... #52
Comments
Hi @walshe. Make sure |
hmm the one in env/dev right? required_version = ">= 0.12"
backend "s3" {
region = "eu-west-1"
profile = "default"
bucket = "tf-state-zoot"
key = "dev.terraform.tfstate"
}
} still getting that issue:
|
ok looks like it was something that was just cached.. have got further now. Btw these scripts depend on existing vpc and subnets already being in place right ? |
Yes @walshe, the template does assume that you have an existing vpc/subnets that will be passed in as input variables. It also assumes that the vpc/subnets will be setup to have outbound internet access so that ECS can talk to the ECR service. We should probably be more explicit about that in the readme. |
Hi..
im pretty new to TF.. seem to have run into the following issue .. any ideas?
➜ base git:(master) ✗ terraform state list
data.aws_caller_identity.current
data.aws_iam_policy_document.ecr
aws_ecr_repository.app
aws_ecr_repository_policy.app
module.tf_remote_state.data.aws_iam_role.role
module.tf_remote_state.aws_s3_bucket.bucket
module.tf_remote_state.aws_s3_bucket_policy.bucket_policy
➜ base git:(master) ✗ cd ../env/dev
➜ dev git:(master) ✗ terraform init
Initializing the backend...
Error: Failed to get existing workspaces: InvalidParameter: 1 validation error(s) found.
The text was updated successfully, but these errors were encountered: