Make specifying a template file not necessary

[vaijab]

As a user I don't want to remember which template file I used to create a particular stack. Instead I'd like it not be necessary.

How could this work?

stacks create -e dev -t templates/foobar.yaml dev-foobar

The above could be reduced to:

stacks create dev-foobar

So stacks defaults to looking at `templates/<template-name.yaml> for templates and the first word before the first dash can be used as an environment name.

[timgent]

Agree this would be nice

[danharvey]

Should it look in templates/ or just the current directory?

Then we can just put a space between environment and stack name so they are two separate arguments?

[vaijab]

Should it look in templates/ or just the current directory?

I think in templates/, because currently workflow is cd stacks; stacks -t templates/.... Also stacks looks for config.yaml in current directory which is normally outside templates/ directory.

Then we can just put a space between environment and stack name so they are two separate arguments?

Not sure about having multiple positional arguments, that could be quite confusing or easy to make a mistake.

[vaijab]

The safest option is to specify a template file and omit specifying stack name, which is now been implemented as part of #39