Hello Vikki,
This is a common challenge when working across multiple Archy environments.
At the moment, Archy doesn't support multiple configuration profiles or alternate .archy_config locations in the same way that the Genesys Cloud CLI supports profiles. Because of that, you can't simply switch between environments by specifying a profile name.
That said, there is a practical workaround that works well: use separate options files for each environment and specify the appropriate file when running your Archy commands.
For example, you could create environment-specific YAML files such as:
clientId: xxx
clientSecret: yyy
location: mypurecloud.com
Then reference the correct file using the --optionsFile parameter:
# Environment 1
~/archy/archy publish \
--optionsFile ~/archy/env1/env1-options.yaml \
--file ~/archy/env1/myFlow.yaml
# Environment 2
~/archy/archy publish \
--optionsFile ~/archy/env2/env2-options.yaml \
--file ~/archy/env2/myFlow.yaml
Using this approach allows you to maintain separate credentials and configurations for each environment without relying on a shared .archy_config file. When Archy runs, it will also display where each configuration value was sourced from, making it easy to confirm that the correct options file is being used.
One additional thing to keep in mind: Archy creates various folders within its home directory (such as debug-related folders). If you're running multiple Archy instances or maintaining separate Archy workspaces, it's worth keeping an eye on those directories, as they can occasionally lead to conflicts.
There is currently a feature request to add profile support similar to the Genesys Cloud CLI, which would make managing multiple environments much more straightforward. Until then, using separate options files is probably the cleanest and most reliable approach.
Hope this helps!
------------------------------
Cameron
Online Community Manager/Moderator
------------------------------