In #1384 a context feature was proposed. Until this get's implemented one could workaround by combining fzf with exporting the OS_CLOUD environment variable, but this would require a list of available clouds. As the cli already knows the configuration format it would be cool to have something like osc config clouds or something similar which outputs the available clouds in line separated list by default or -o json as json array.
Alternative solution
A possible alternative solution would be to parse the clouds.yaml with something like yq and extract each individual cloud. But in general I think it makes sense to get config subcommands in the cli itself.
I've seen #1888 which proposes configuration modification, if modification is added listing makes sense, too.
In #1384 a context feature was proposed. Until this get's implemented one could workaround by combining
fzfwith exporting the OS_CLOUD environment variable, but this would require a list of available clouds. As the cli already knows the configuration format it would be cool to have something likeosc config cloudsor something similar which outputs the available clouds in line separated list by default or-o jsonas json array.Alternative solution
A possible alternative solution would be to parse the
clouds.yamlwith something like yq and extract each individual cloud. But in general I think it makes sense to get config subcommands in the cli itself.I've seen #1888 which proposes configuration modification, if modification is added listing makes sense, too.