scheduler: AggregateMultitenancyIsolation to support unlimited tenant
This commit removes the previous limitation on the number of tenants that can be filtered using the `filter_tenant_id` aggregate property in the AggregateMultitenancyIsolation scheduler filter. The `filter_tenant_id` can now be used as a suffix, allowing for an unlimited number of tenant ID properties to be set on the aggregate. This update maintains backward compatibility. Implements: blueprint aggregatemultitenancyisolation-to-support-unlimited-tenant Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@industrialdiscipline.com> Change-Id: Ic87d142647774b62a6af2cc5eb7a3cd66f9afeb7
This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
This release removes the limit of the number of tenants that can
|
||||
be specified for an aggregate and honored by the
|
||||
`AggregateMultitenancyIsolation` filter. It now respects multiple
|
||||
keys prefixed by `filter_tenant_id` like the request filter
|
||||
implementation. You can use `filter_tenant_id` as a prefix to set
|
||||
an infinite number of properties for tenant IDs on the aggregate.
|
||||
This change has been implemented in a manner that preserves
|
||||
backward compatibility. Existing configurations using
|
||||
`filter_tenant_id` will continue to function as expected.
|
||||
Reference in New Issue
Block a user