Skip to content
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

Automatically login to Pier One #441

Closed
musiKk opened this issue Jan 27, 2017 · 3 comments
Closed

Automatically login to Pier One #441

musiKk opened this issue Jan 27, 2017 · 3 comments

Comments

@musiKk
Copy link

musiKk commented Jan 27, 2017

When creating a stack, Pier One is checked. This is sensible. If I'm not logged in, senza barfs and suggests to log in. Senza should try to log the user in first and only if that fails abort with an error.

I think the behavior of the --force flag should stay the same, i.e., when it is used, don't even try to check for the existence of the image and thus don't try to log the user in.

last-ent pushed a commit that referenced this issue Feb 2, 2017
last-ent added a commit that referenced this issue Feb 2, 2017
#441 Try to log into Pier One if the existing token has expired.
@akauppi
Copy link

akauppi commented Feb 9, 2017

Personally, I like to keep log ins away from any scripts, and would like for the current separation to remain.

The reason is that I would like to be personally aware of when such logins happen, and if any or all the tools start logging in on my behalf, this control essentially vanishes.

@musiKk
Copy link
Author

musiKk commented Feb 10, 2017

It seems there is already a proposed change.

Personally I don't really see a problem though. I mean, the tools are interwoven to a degree and the only thing I'm doing after I get the error is to do what it suggests (login to Pier One) and retry stack creation. When would attempting to log in not be a sensible solution? I think this is a matter of purity (separate all the things) vs. usability (do what I want!) and I'm in favor of usability.

@musiKk
Copy link
Author

musiKk commented Mar 23, 2017

I think this is deployed. I'll just clean up after myself.

@musiKk musiKk closed this as completed Mar 23, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants