Skip to content

/ stack

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

Jump to bottom

--stack-yaml command line flag #378

Closed
DanBurton opened this issue Jun 22, 2015 · 2 comments
Closed

--stack-yaml command line flag #378

DanBurton opened this issue Jun 22, 2015 · 2 comments
Assignees
@DanBurton
Labels
need confirmation
Milestone
P1: Must

Comments

@DanBurton
Copy link
Contributor

@DanBurton DanBurton commented Jun 22, 2015

Similar to how the STACK_YAML environment variable can override the location of stack.yaml, we'd like a command line flag that can do the same thing.
DanBurton added a commit that referenced this issue Jun 22, 2015
@DanBurton
Set the STACK_YAML env var to the --stack-yaml option. #378
Loading status checks…
264b4d1
@snoyberg snoyberg added this to the 0.2.0.0 milestone Jun 23, 2015
@snoyberg snoyberg mentioned this issue Jun 24, 2015
Closed
@adinapoli adinapoli mentioned this issue Jun 25, 2015
Closed
snoyberg added a commit that referenced this issue Jun 26, 2015
@snoyberg
Implement an upgrade command #237
Loading status checks…
4fb03ff 
Also implemented #378 along the way
@snoyberg
Copy link
Contributor

@snoyberg snoyberg commented Jun 26, 2015

This is now implemented. @DanBurton confirmed?
snoyberg added a commit that referenced this issue Jun 26, 2015
@snoyberg
Update ChangeLog for #378
Loading status checks…
7baa6d1
@DanBurton
Copy link
Contributor Author

@DanBurton DanBurton commented Jun 27, 2015

Confirmed.
@DanBurton DanBurton closed this Jun 27, 2015
@rrnewton rrnewton mentioned this issue Aug 7, 2015
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DanBurton DanBurton

Labels
need confirmation
Projects
None yet
Milestone
P1: Must
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@snoyberg @DanBurton