The official Temporal CLI already stores profile-related information in one of two ways:
Both of these methods include the cluster address, namespace, and TLS information, and both have CLI commands to dump the properties of the currently active env/profile.
$ temporal --env example env get -o json
[
{
"property": "address",
"value": "temporal.home.arpa:7233"
},
{
"property": "namespace",
"value": "default"
}
]
$ temporal --profile example config get -o json
{
"address": "temporal.home.arpa:7233",
"namespace": "default"
}Rather than having to duplicate that configuration for tempo, would it be possible for tempo to optionally reference profiles from the official CLI?
The official Temporal CLI already stores profile-related information in one of two ways:
$HOME/.config/temporalio/temporal.yaml(eventually replaced by "profiles", but still takes precedence currently)$HOME/.config/temporalio/temporal.toml(some flags experimental)Both of these methods include the cluster address, namespace, and TLS information, and both have CLI commands to dump the properties of the currently active env/profile.
$ temporal --env example env get -o json [ { "property": "address", "value": "temporal.home.arpa:7233" }, { "property": "namespace", "value": "default" } ]$ temporal --profile example config get -o json { "address": "temporal.home.arpa:7233", "namespace": "default" }Rather than having to duplicate that configuration for
tempo, would it be possible fortempoto optionally reference profiles from the official CLI?