-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow restraining snapshot selection #229
Comments
I think the solution here will end up being very close to what we do for #228, so the two issues should be considered together (possibly even merged into a single issue actually). |
Feel free to merge/close this issue if it's covered my #228. |
This issue is potentially asking for a |
Adding a |
Bikeshedding: do we have a problem with the command |
There could be a single command that does the right thing. If
There's also a question of what to do when creating a multi-package project. Right now |
I've pushed a simple commit to the 229-stack-init branch that implements the basics of an init command. One thing I'm concerned about is trying to make I think instead of becoming too magical, it would make more sense to generate a basic stack.yaml and explain to the user (via docs on the website and comments in the generated file) how to proceed. |
Sure, it might make sense to give it a different name. I am wondering if |
Hmm I like that. On Tue, Jun 9, 2015, 7:29 PM Greg Weber notifications@github.com wrote:
|
Another thing I have been thinking about is that There are different points in the design space, good thing we are still in beta :) |
I've opened #253 to try and discuss this and other related topics together |
Solved by the |
I'd like to have an option to select the snapshot when running
stack build
instead of relying on stack to figure it out for me and if it is wrong cancelling, editing the yaml file and rerunning it.The text was updated successfully, but these errors were encountered: