Settings and activity
8 results found
-
13 votes
An error occurred while saving the comment -
3 votes
dingus
supported this idea
·
-
13 votesdingus
supported this idea
·
dingus
shared this idea
·
-
7 votesdingus
shared this idea
·
-
10 votesdingus
supported this idea
·
-
57 votesdingus
supported this idea
·
-
7 votes
An error occurred while saving the comment dingus
commented
This is much needed in my team as well. Another work around is to have a different "database" variable in the library set that has 2 values scoped for each environment and then in the tenant/template variable("tenant_database") you reference #{database}.
However this is so messy and only really works for single text box types, it becomes much more difficult for account or certificate types.
Project Templates have the ability to be scoped per environment so can we please have this for tenants vars. Also if I'm being picky can we do away with the format for setting project template vars in the tenants with a drop down for each environment, it's not very DRY. Just implement the same scoping behavior for regular project vars.
Sorry if I seem cynical, love the product!
dingus
supported this idea
·
-
1 votedingus
shared this idea
·
I would also love to see this implemented. I just put in the work to setup a build pipeline to get it into Azure Container Registry only to find out octo doesn't support OCI. I love Octo and don't fancy using another option but I don't have much choice.