feat: api key auth + config reorg #7
Conversation
brendan-myers
commented
Jul 10, 2025
brendan-myers
commented
- Added support for API key auth to Temporal Cloud
- Modified the config structure so Temporal Cloud config is nested
config.yaml.sample
Outdated
| tls: | ||
| cert_file: "/path/to/<namespace>.<account>/tls.crt" | ||
| key_file: "/path/to/<namespace>.<account>/tls.key" | ||
| - proxy_id: "<id>" |
There was a problem hiding this comment.
How about something like client_id or workload_id here?
There was a problem hiding this comment.
Or we could use temporal namespace as the target_id since this block is nested under targets then have a nested list for configuring clients/workloads per target.
There was a problem hiding this comment.
If we used the namespace as the id then only one target could be configured for that namespace; users wouldn't be able to configure more than one target that connected to the same namespace (if they wanted a different configuration for auth/encryption/etc).
workload_id would work. Preferable to client_id as that may sound like each client (worker) needs a separate target configured. workload_id is good too because it can be used as a correlation id, for instance, if some external system grants a workload access to a namespace it can use the id for CRUD operations on the proxy config if needed.
What do you think?
There was a problem hiding this comment.
Would you change the key of this section from targets to workloads then?
