Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Machine should manage credentials for drivers #987

Closed
dave-tucker opened this issue Apr 9, 2015 · 3 comments
Closed

Machine should manage credentials for drivers #987

dave-tucker opened this issue Apr 9, 2015 · 3 comments

Comments

@dave-tucker
Copy link
Contributor

I find that managing env variables for the various drivers to be a little clumsy. Not only are there issues related to me accidentally putting these in my .zshrc which is hosted on GitHub, but it's tricky to manage multiple accounts with the same provider.

For example, consider DigitalOcean, where I have a "personal" account and a "company" account.
To perform operations on one, or the other, I'd need to make sure to source the correct file first or the API calls would fail.

I'd like to see something along the lines of:

docker-machine account create -d digitalocean dave
... prompts for the required credentials...
Account "dave" for DigitalOcean created successfully

docker-machine account create -d digitalocean work
... prompts for the required credentials...
Account "work" for DigitalOcean created successfully 

docker-machine create -d digitalocean --account dave

I would expect machine to securely store the minimum amount of information required. Perhaps in ~/.docker/accounts

@ehazlett
Copy link
Contributor

We are looking at adding support for this in #773. Not sure on timeline though.

@dave-tucker
Copy link
Contributor Author

Cool! Thanks @ehazlett

@ehazlett
Copy link
Contributor

yw! this is ref'd in that issue -- feel free to re-open if you have other ideas or questions. thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants