0.9.1
state environments.
When I run terraform env list I expect to see the default environment listed.
I have no other state environments created.
State environment creation is also not working using terraform env new test
$ terraform env list
named states not supported
terraform env new test
named states not supported
Please list the steps required to reproduce the issue, for example:
terraform env listWhich backend do you use for the state storage?
I'm seeing this behaviour using the S3 backend.
I can confirm the same behaviour with the Artifactory backend.
Confirming with the S3 backend. No previous remote state was used, nor local state imported.
The S3 backend also.
If you dig through the code you will see that Consul appears to be the only remte backend supporting environments.
I think this is the same issue I have raised here: #12768
@tom-schultz, I expected this might be the case as soon as I saw the error, although I didn't have time to investigate, thanks.
It's a shame that this wasn't mentioned in the docs or the announcement, if it turns out this is simply a currently unsupported feature.
Hi Everyone,
Sorry this isn't as clear as it could be in the docs yet. I think the supported backends may have only been mentioned in the release announcement.
I'm going to close as as this is the expected behavior, and there is already an issue open for supporting named states in S3.
Are the docs going to be updated? That would seem to be pretty critical.
Are the docs going to be updated? That would seem to be pretty critical.
Agree, just ran into this issue. Would be nice to have known from the docs that it wasn't going to work.
@jbardin any chance to enable it for gce?
I'm going to lock this issue because it has been closed for _30 days_ โณ. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.