2 Answers
Hello! First off, good on you for digging into this! 👍 Second, thank you for pointing out the potential misunderstanding and the second way of listing configuration properties.
If you wouldn’t mind–before you continue reading, below–could you please rewatch this lecture starting at 11:20 and tell me if you think what I’ve added helps avoid the confusion?
…
…
…
OK. Some additional thoughts:
The key thing is that gcloud config list
works (as you pointed out) against the active configuration, but it’s also valuable to note (as you did) that gcloud config configurations describe
always requires a configuration name, instead. Both are quite similar in what they do, but they format their output a little differently. In fact the documentation for "gcloud config configurations describe" notes the following:
To describe existing named configuration, run:
$ gcloud config configurations describe my_config</span>
This is similar to:
$ gcloud config configurations activate my_config
$ gcloud config list
Cheers!
Mattias
Try this
gcloud config list --configuration=$CONFIG_NAME
This also helps –
gcloud config list --configuration=$CONFIG_NAME
Correct. To describe the configuration information, you need to activate the configuration first as mentioned by mattias.