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.
Go to file
Stephen Finucane 59a3dc90a9
Add support for tox 4
3 months ago
doc Switch to newer openstackdocstheme and reno versions 3 years ago
os_client_config Fix zuul jobs 10 months ago
releasenotes Switch to newer openstackdocstheme and reno versions 3 years ago
tools Fix the conflict of urlparse between python2 and python3 4 years ago
.coveragerc Change ignore-errors to ignore_errors 8 years ago
.gitignore Updates for stestr 6 years ago
.gitreview OpenDev Migration Patch 4 years ago
.mailmap Initial Cookiecutter Commit. 9 years ago
.stestr.conf Updates for stestr 6 years ago
.zuul.yaml Fix zuul jobs 10 months ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 8 years ago
HACKING.rst Update the documentation link for doc migration 6 years ago
LICENSE Initial Cookiecutter Commit. 9 years ago
README.rst Update for opendev 4 years ago
lower-constraints.txt Cap jsonschema 3.2.0 as the minimal version 3 years ago
requirements.txt Replace guts with openstack.config 5 years ago
setup.cfg Cleanup py27 support 3 years ago
setup.py Cleanup py27 support 3 years ago
test-requirements.txt Cap jsonschema 3.2.0 as the minimal version 3 years ago
tox.ini Add support for tox 4 3 months 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