Open james-boydell opened 1 month ago
@james-boydell, we do have plans to support this, and there is already a separation between backend type/name internally, so it should help. As a workaround, can you use multiple projects for that? Do I understand correctly that it's inconvenient because of the team management duplication?
@r4victor This is a non-blocker for us. If there is intent to support this, amazing!
Problem
I'd like the ability to add multiple backends of the same type (eg, AWS), as we may have different settings/use cases.
For example, we may want to run dev environments in one AWS account/region/VPC and run our tasks/larger training jobs in another AWS account/region/vpc.
Solution
-add custom naming to cloud backends (as they would need to be referenced by runs) -allow multiple backend configs of the same type -allow runs to reference custom backend names for runs
Workaround
No response
Would you like to help us implement this feature by sending a PR?
No