Repository navigation
support authentication from OS_* environment variables - #81
Conversation
|
Hej @thomaslaurenson, thanks a lot taking an interest in the project and taking the time to contribute as well. The OS_* env var support is a very useful addition, and I really appreciate the effort you put into the implementation, testing, and docs. Which other OpenStack services are you using regularly? and are there particular commands/actions you’d like to see implemented in o7k? Real-world feedback in this phase is extremely useful for figuring out where to take the project next. Thanks again and feel free to ⭐ the repo and spread the word so more OpenStack folks get to know the project. |
|
Thanks for the ultra fast merge 💯 We use a bunch of OpenStack services - the regular ones being nova, neutron, glance, cinder, swift. I work at a university that is part of the Nectar Research Cloud (https://ardc.edu.au/services/ardc-nectar-research-cloud/) - a group of universities in Australia/New Zealand participate in it. The main things I have been using o7k for, is just browsing our inventory, mainly instances. Was looking for something easier than running |
Firstly, very cool project - I have been using a local build against our OpenStack environment. However, one issue for us is that most team member using the standard
OS_*environment variables, either sourced from anopenrcfile or injected per process by a secret manager - I have a password store extension I use (https://github.com/thomaslaurenson/pass-env).Changes
OS_AUTH_URLis set, the Contexts screen lists an extra context namedenvvars(name taken from openstacksdk)envvarsauthenticates with gophercloud from theOS_*variables; everything downstream sees an ordinary contextclouds.yamlwhenOS_AUTH_URLis set; without either, the error and exit code are unchangedLimitations
clouds.yaml, user and project are assumed to be in the same domain; useOS_PROJECT_IDotherwiseOS_CACERT,OS_CERTandOS_KEYare not applied to this context yetThis was a first effort to add envvar support. I did some testing locally with envvars set, and
clouds.ymlfiles in default locations. Open to any feedback and changes, and have "allowed edits by maintainers".