[Resolve #546] select command stacks based on exact stack-group name

[cornerman]

When specifying a command_path for cli operations, commands will be executed on all stack-groups which share a prefix with command_path. So, if you have two configs env1 and env2, but then provide env as your command_path, both env1 and env2 will be executed.

In my opinion, env is not a valid stack-group and should therefore not start anything. We should either specify env1 or env2 expicitly or alternatively group them under one common directory my-envs when you want to launch stack together.

PR Checklist

• Wrote a good commit message & description [see guide below].
• Commit message starts with [Resolve #issue-number].
• Added/Updated unit tests.
• Added/Updated integration tests (if applicable).
• All unit tests (make test) are passing.
• Used the same coding conventions as the rest of the project.
• The new code passes flake8 (make lint) checks.
• The PR relates to only one subject with a clear title.
  and description in grammatically correct, complete sentences.

Approver/Reviewer Checklist

• Before merge squash related commits.

Other Information

Guide to writing a good commit

[ngfgrant]

@cornerman thanks for the PR. LGTM but I'd like someone with windows to test this if they could basically I am intrigued as to whether the use of sep will cause issues in Windows. I don't think it will but worth double checking. Maybe @lukeplausin or @mike-rsi if you get sometime to checkout this branch?

[cornerman]

We might want to add a check for yaml files. If you have a config file config/folder/resource.yaml, you should be able to select this stack with either sceptre status folder/resource.yaml or sceptre status folder/resource. With this PR, currently only the first one would work.

Edit: But it could again be ambiguous, if you have a folder folder/resource. So maybe we just better leave the PR as is.

[craighurley]

Would love to see this make it into the next release. This issue has tripped up colleagues on my team, luckily in non-prod environments 😄.

[ngfgrant]

Guys its my bad for letting this stay open as long as it has. Definitely need to get this merged and I am happy with this PR as it is. As per my original comment there may be some windows issues with sep but I am pretty sure there won't be.

@cornerman if you have time could you rebase this off master and resolve the conflict in test_config_reader.py? If not let me know and I'll help out.

[rseuchter]

@cornerman if you have time could you rebase this off master and resolve the conflict in test_config_reader.py? If not let me know and I'll help out.

I took the liberty of rebasing this. Please check rseuchter@f5a5181
(I have no idea if or how I can add this to the existing PR #731)

An hour or two ago, I ran into this bug with a colleague. While we found a workaround it caused some serious concern. After realizing this has been lying around for so long I thought I rather help get this resolved.

[cornerman]

@rseuchter Thank you! That is great. I just reset my branch to your commit and pushed!

@ngfgrant This PR is now rebased

[rseuchter]

This PR has been stale. Still, I feel the underlying issue is critical.
The build says it was unauthorized. I don't think it's related to the PR itself.

Any ideas @ngfgrant?

[ngfgrant]

I’m going to get to this and others this weekend. Unauthorised makes sense (to me).