summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorMonty Taylor <mordred@inaugust.com>2017-09-19 14:40:53 -0500
committerMonty Taylor <mordred@inaugust.com>2017-09-19 14:40:53 -0500
commit45fd7b4a949e6cd8482b3025b96251c5832ddf23 (patch)
treed4f225a4d6a4642ca243116152eea4422a19a9bb /releasenotes
parenteafc8bed564d41f2a0c6a050e7a301241309fa59 (diff)
downloados-client-config-45fd7b4a949e6cd8482b3025b96251c5832ddf23.tar.gz
Treat clouds.yaml with one cloud like envvars
If there is only one cloud and that cloud is envvars, things work as expected. If there is only one cloud in clouds.yaml and no envvars cloud, we throw an error, even though it should be obvious which cloud was intended. Change-Id: Ia49d0fb2cc7dca36476d0e5ae3fe2b2aa1209e59
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/default-cloud-7ee0bcb9e5dd24b9.yaml7
1 files changed, 7 insertions, 0 deletions
diff --git a/releasenotes/notes/default-cloud-7ee0bcb9e5dd24b9.yaml b/releasenotes/notes/default-cloud-7ee0bcb9e5dd24b9.yaml
new file mode 100644
index 0000000..49aba3c
--- /dev/null
+++ b/releasenotes/notes/default-cloud-7ee0bcb9e5dd24b9.yaml
@@ -0,0 +1,7 @@
+---
+issues:
+ - If there was only one cloud defined in clouds.yaml
+ os-client-config was requiring the cloud parameter
+ be passed. This is inconsistent with how the envvars
+ cloud works which WILL work without setting the cloud
+ parameter if it's the only cloud.