Skip to content
This repository has been archived by the owner on Aug 1, 2023. It is now read-only.

Support clouds.yaml files #487

Open
emonty opened this issue Sep 14, 2015 · 9 comments
Open

Support clouds.yaml files #487

emonty opened this issue Sep 14, 2015 · 9 comments

Comments

@emonty
Copy link

emonty commented Sep 14, 2015

Keystone with auth plugins gets ... complex. As a result, openstack spawned the os-client-config library this last cycle, which, in addition to handling normal openrc env vars, allows the configuration of multiple clouds - and features of known providers in a yaml file:

http://docs.openstack.org/developer/os-client-config/

It would be super cool if gophercloud supported reading the same file. I'd be happy to work on adding the support - but I figured I should check first to see if it's a feature you'd take. I would imagine given the way env vars work - perhaps 'openstack.AuthOptionsFromYaml()' ?

@jrperritt
Copy link
Contributor

I think that sounds great, and that it's definitely a feature worth having.

@emonty
Copy link
Author

emonty commented Oct 16, 2015

Sweet! I'll get to work on it soon!

@mcanevet
Copy link

@emonty any news?

@raphink
Copy link

raphink commented Jun 29, 2016

This would be very useful. @emonty would you duplicate the vendor info, or import it from the python lib somehow?

@emonty
Copy link
Author

emonty commented Jun 29, 2016

@mcanevet hoping to work on it RSN. (sorry for the delay) @raphink We're also adding clouds.yaml support for javascript, so what I'm thinking is to split the vendor info into its own repo that we can either import or vendor or submodule or something waves hands

@raphink
Copy link

raphink commented Jun 29, 2016

Thanks for the answer. We would like to use this feature in terraform using this lib, and we'd be willing to contribute in the dev.

@jrperritt
Copy link
Contributor

Note that it is too late for this feature to make it into this repo. See #592

@emonty
Copy link
Author

emonty commented Jun 30, 2016

@jrperritt thanks! I'll get a PR done for the new repo whenever it's ready for such a thing.

@mcanevet
Copy link

mcanevet commented Aug 1, 2016

@emonty any news on this?

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

Successfully merging a pull request may close this issue.

4 participants