| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Region name support got changed a little while ago, and a call that
should now be a keyword argument style stayed as a positional ... which
means that we lost region name support for clouds with more than one
region. (it treated all of them like the first region)
Change-Id: I666758a775b8fc8e03b7e9ddd3aa494c13505612
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Treat the CloudConfig object as if it has the config attributes directly.
And add some simple tests.
This makes it easier to replace an argparse.Namespace() object with a
CloudConfig object. It also might make initialization of some of the
default attributes unnecessary. An example of this usage is in
https://review.openstack.org/#/c/129795/1/openstackclient/shell.py
Change-Id: I00ced540cf94742e8cb738f8f0767445ffeb4bfe
|
| |
|
|
|
|
|
|
|
| |
The Namespace objects returned by argparse contain all defined options
even if they are unspecified and default to None or ''. Also it
is not iterable. Change all that to add only the options presented
to argparse to the cloud_config.
Change-Id: Ia22fad60c81ab0b2878b404c0c8608d903ca964b
|
| |
|
|
|
|
|
|
| |
Now takes the ability to pass in a dict of key/value pairs, probably
from a command line processing thing like argparse, and to overlay them
on the config that came from the files or env vars.
Change-Id: I830699476e2340389979b34704c0dfbfe97a1e08
|
| |
|
|
|
|
|
| |
It's possible that there will not be a value in username, so we can't
use it as a blind default.
Change-Id: Iae93b9ec0e691c7b2174a0138c5455e36ad77ad7
|
| |
|
|
|
|
|
| |
devstack clouds are more strict that public ones, so it's more important
to get project_name vs. project_id correct. Solve it with brute force.
Change-Id: I957b19c23266d379834361ab6a5b3b2dc5d15d3d
|
| |
|
|
|
|
|
| |
Things need to do local caching, which means they need to control
some settings about that. Add simple cache settings support.
Change-Id: I7b56cc25ebe7a803816d95b79d0329f8e42025ba
|
| |
|
|
| |
Change-Id: If0ab1db3df8ba3a2880473f2287ae3f85c84d9d5
|
| |
|
|
| |
Change-Id: Id133bc3c39b97a4489e75c3d38df601f999e8f3a
|
| |\
| |
| | |
Add clouds-public.yaml
|
| |/
|
|
|
|
|
|
|
| |
Put vendor config outside of the code in clouds-public.yaml. Fall back to
vendors.py if clouds-public.yaml not found.
The search follows the same rules as clouds.yaml, the file is the same
format except the top-level key is 'public-clouds'. Typically only auth_url
and region_name are populated.
|
| | |
|
| |\
| |
| | |
Handle missing vendor key
|
| | |
| |
| |
| | |
Continue on if the configured vendor config is not present
|
| |\ \
| | |
| | | |
Make env vars lowest priority
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When working with multiple tools the project CLIs only know about options
and environment variables. When selecting a cloud config that includes
a section from vendors.py environment vars overwrite that data if they
are defined. The priority order should be:
* command line args
* cloud config selection
* environment variables
|
| |\ \
| |/
|/| |
Handle null region
|
| |/
|
|
| |
Not all clouds define/require region_name to be set
|
| | |
|
| |
|
|
|
| |
We don't need to enumerate the service types - we can simply match
at consumption time on patterns.
|
| | |
|
| | |
|
| |
|
