Hi Michael,
The behavior you describe is what I want, but is not the behavior I have observed.
I want to create tags related to hosting, thus:
Hosting Continent: europe, america
Hosting Environment: prod, demo, test
Hosting Pool: pool01, pool02, …
I set up tenants with the appropriate values from these tag sets:
Tenant01: prod, america, pool01
Tenant02: prod, europe, pool01
Tenant03: demo, america, pool01
Tenant04: demo, europe, pool01
Tenant05: prod, america, pool02
Tenant06: prod, europe, pool02
Then, I went to use the tags sets to filter tenants on deployment targets:
us_prod_web01: prod, america, pool01
us_prod_web02: prod, america, pool02
eu_prod_web01: prod, europe, pool01
us_demo_web01: demo, america , pool01
us_prod_db01: prod, america
eu_prod: db01: prod, europe
To take one example:
- I expected us_prod_web01 to have one tenant according to the tag sets (this would be AND logic across sets): Tenant01
- Instead, us_prod_web01 has: Tenant01, Tenant02, Tenant03, Tenant04, Tenant05, Tenant06. In other words, the tags are applied as an OR.
This makes tags sets as filters completely useless to me.