4 results found
-
Variable Set support for Tenants
Variable sets should have Tenant support. Such variables to have a Tenant scope.
This would allow common vars to be reused via variable sets. This should be a common requirement for multi-tenanted microservice setups. Without that you either have to have variable copied or have them all defined at the Tenant level. Both bad options.
A work around is to have variables as #{if TenantName =="A"}TenantAValue{#/if}#{if TenantName =="B"}TenantBValue{#/if}
this is pretty ugly and it doesnt work for snesative variables as far as I know.I know this tricky to implement but really important IMHO
4 votes -
Permissions on Tenant Tag level
Currently it’s possible to limit rights of a Team to specific tenants but not to a tenant tag. With ~20 tenants and more it's really hard to maintain this. Also the list would become so long. It would really help to specify just the tenant tag.
In our case we have only one risky tenant which should be assigned to a small Team. But we have to add all 19 less risky tenants to the bigger Team.
2 votes -
There should be a "table" view of tenants.
There should be a "table" view of tenants. Table columns should be customizable and and there should be the ability to filter. This way I can easily modify variables.
Lets say I have a variable indicating which web server my app is assigned to. And I get a new web server. I could look at this table, sort or filter on the web_server variable and assign tenants/apps to the new webserver.
1 vote -
Users with a scoped Tenant Manager role should have created tenants added to their role scope
Currently if I have a user or team that is assigned the Tenant Manager role that is scoped to specific tenants they are unable to view any of the tenants they create. Instead they could create the tenant but would then need someone to add the new tenant to the role scope
1 vote
- Don't see your idea?