-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Change default of where stack is created #971
Conversation
If currently logged in, `stack init` creates a managed stack. Otherwise, it creates a local stack. This avoids the need to specify `--local` when not using the service. As today, `--local` can be passed, which will create a local stack regardless of being logged in or not. A new flag, `--remote`, has been added, which can be passed to indicate a managed stack, used to force an error if not logged into the service.
338a027
to
50f415c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Sorry for the delay, thought I reviewed this yesterday!
@ellismg, No problem. I was about to merge this and looked over the changes again and I realized I made a mistake when factoring out the "is logged in" check to its own function. If we want to keep it factored this way, Mind taking a quick look at the new commit? |
It it possible to restructure the code such that we use |
Sure, I'll change it to that. |
07bded7
to
636898a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
If currently logged in,
stack init
creates a managed stack. Otherwise, it creates a local stack. This avoids the need to specify--local
when not using the service.As today,
--local
can be passed, which will create a local stack regardless of being logged in or not.A new flag,
--remote
, has been added, which can be passed to indicate a managed stack, used to force an error if not logged into the service.Fixes #816