Open vkatsikaros opened 5 years ago
Hi @vkatsikaros - I like your icon 😀 !
terraform workspace list
lists the existing workspace in your current working directory. The default
workspace always exists - even if there are no terraform configuration files present in the working directory. You might consider it a "potential" workspace.
Having said that, I can see how this is confusing - personally I would expect terraform workspace list
to print a notification that no terraform configuration was found in the current directory. I'm going to flag this as an enhancement and see what the rest of the core team thinks.
Thanks for opening this issue!
@mildwonkey I like yours too :)
Thanks for the detailed explanation. Let me know how this goes. I'd be interested in working on the issue if it's something that isn't a priority, it's not very complicated and if there are some starting pointers.
The
terraform workspace
current documentation says:In directories where there is no terraform code,
terraform workspace list
still reports the default workspace. I apologize if I have missed an terraform workspace concept that explains the behavior.Expected Behavior
Actual Behavior
Steps to Reproduce
The steps are simple and unrelated to terraform configuration files, so the "Expected Behavior" section above covers reproduction.