Unified config handling for client libraries and programs
Go to file
Monty Taylor cc7a469fdb Update for opendev
Change-Id: Ib29ca90f7268e4a31dab6e80d92ef4e0fa99f64e
2019-04-21 13:09:50 +00:00
doc Applying the HTTPS protocal in configuration.rst 2019-01-09 14:12:33 +00:00
os_client_config Shift Limestone Networks profile to openstacksdk 2018-06-12 10:36:30 -04:00
releasenotes Update master for stable/stein 2019-03-18 14:41:55 +00:00
tools Fix the conflict of urlparse between python2 and python3 2018-10-31 17:08:45 +08:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:41:36 +00:00
.gitignore Updates for stestr 2017-09-14 16:57:42 -05:00
.gitreview OpenDev Migration Patch 2019-04-19 19:30:03 +00:00
.mailmap Initial Cookiecutter Commit. 2014-09-20 16:16:13 -07:00
.stestr.conf Updates for stestr 2017-09-14 16:57:42 -05:00
.zuul.yaml OpenDev Migration Patch 2019-04-19 19:30:03 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:46 +00:00
HACKING.rst Update the documentation link for doc migration 2017-08-07 15:10:42 +08:00
LICENSE Initial Cookiecutter Commit. 2014-09-20 16:16:13 -07:00
lower-constraints.txt Replace guts with openstack.config 2018-04-27 08:42:17 -05:00
README.rst Update for opendev 2019-04-21 13:09:50 +00:00
requirements.txt Replace guts with openstack.config 2018-04-27 08:42:17 -05:00
setup.cfg Change openstack-dev to openstack-discuss 2018-12-04 23:58:50 +08:00
setup.py Manually sync with g-r 2017-07-24 21:46:26 +02:00
test-requirements.txt Update hacking version 2019-03-06 22:18:14 +08:00
tox.ini Update for opendev 2019-04-21 13:09:50 +00:00

os-client-config

image

Warning

os-client-config has been superceded by openstacksdk. While os-client-config will continue to exist, it is highly recommended that users transition to using openstacksdk directly.

os-client-config is a library for collecting client configuration for using an OpenStack cloud in a consistent and comprehensive manner. It will find cloud config for as few as 1 cloud and as many as you want to put in a config file. It will read environment variables and config files, and it also contains some vendor specific default values so that you don't have to know extra info to use OpenStack

  • If you have a config file, you will get the clouds listed in it
  • If you have environment variables, you will get a cloud named envvars
  • If you have neither, you will get a cloud named defaults with base defaults

Source