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.
Dmitry Tantsur efd56a806e Add a release note for Python 2 support removal 2 weeks ago
doc Fix broken link to openstacksdk 6 months ago
os_client_config Fix pep8 issue in o_c_c/__init__ 2 weeks ago
releasenotes Add a release note for Python 2 support removal 2 weeks ago
tools Fix the conflict of urlparse between python2 and python3 1 year ago
.coveragerc Change ignore-errors to ignore_errors 4 years ago
.gitignore Updates for stestr 2 years ago
.gitreview OpenDev Migration Patch 9 months ago
.mailmap Initial Cookiecutter Commit. 5 years ago
.stestr.conf Updates for stestr 2 years ago
.zuul.yaml Stop testing python2.7 3 months ago
CONTRIBUTING.rst Workflow documentation is now in infra-manual 5 years ago
HACKING.rst Update the documentation link for doc migration 2 years ago
LICENSE Initial Cookiecutter Commit. 5 years ago
README.rst Update for opendev 9 months ago
lower-constraints.txt Replace guts with openstack.config 1 year ago
requirements.txt Replace guts with openstack.config 1 year ago
setup.cfg Stop testing python2.7 3 months ago
setup.py Manually sync with g-r 2 years ago
test-requirements.txt Update hacking version 10 months ago
tox.ini Merge "Stop testing python2.7" 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