Unified config handling for client libraries and programs
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Monty Taylor cc7a469fdb Update for opendev 1 month ago
doc Applying the HTTPS protocal in configuration.rst 5 months ago
os_client_config Shift Limestone Networks profile to openstacksdk 1 year ago
releasenotes Update master for stable/stein 3 months ago
tools Fix the conflict of urlparse between python2 and python3 7 months ago
.coveragerc Change ignore-errors to ignore_errors 3 years ago
.gitignore Updates for stestr 1 year ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Initial Cookiecutter Commit. 4 years ago
.stestr.conf Updates for stestr 1 year ago
.zuul.yaml OpenDev Migration Patch 1 month ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 4 years ago
HACKING.rst Update the documentation link for doc migration 1 year ago
LICENSE Initial Cookiecutter Commit. 4 years ago
README.rst Update for opendev 1 month ago
lower-constraints.txt Replace guts with openstack.config 1 year ago
requirements.txt Replace guts with openstack.config 1 year ago
setup.cfg Change openstack-dev to openstack-discuss 6 months ago
setup.py Manually sync with g-r 1 year ago
test-requirements.txt Update hacking version 3 months ago
tox.ini Update for opendev 1 month ago

README.rst

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