Open markchalloner opened 5 years ago
I just stumbled into the same issue. It looks like "env:" is the default workspace_key_prefix
that gets prepended onto your workspace name for non-default workspaces, as a prefix to the key.
In my case, it seemed easiest for me to use project-specific workspace_key_prefixes
rather than project-specific key
s, and I'm just using "state" for the key
for all my projects that share the same bucket, but ensuring they have unique workspace_key_prefixes
so that I can scope S3 permissions to just that S3 path.
If you hit this issue and nothing else is working, make sure the actual object is owned/accessible to the profile you're using.
In my case the state was pushed to the bucket under another aws account for some reason and this was preventing terraform from getting it using the profile I provided. The errors and log entries made it seem like it was something else. Once I reassumed ownership of the state file things worked again.
Terraform Version
Terraform Configuration Files
Debug Output
Crash Output
Expected Behavior
No attempt to access env:/ key
Actual Behavior
Attempted to access env:/ key:
Steps to Reproduce
terraform init
terraform apply
Additional Context
References
15358