Problem Statement
At the moment Entitlement Kind-types are partially set directly in With.Kind and then within With.Entitlements as part of @{} together with Id. This should be improved and simplified.
We should rethink the With.Kind level as the StepType doesn't really differ from what it does for Kind = 'Group' or AdministrativeUnit. Hence, even mixed situations may make sense or simplify give more flexibility for the Step definitions.
Proposed Solution
Only using Kind within With.Entitlements = @{} hashtables for EnsureEntitlement or within With.Keep = @{} hashtables?
Alternatives Considered
To be investigated.
Think about provider-specific parts (e.g. 'Administrative Units' do only exist in Entra but not in AD)?
Impact
- Does this affect existing workflows?
- Any backward compatibility concerns?
Additional Context
We should make sure access rights scopes are only activated based on Kind condition.
Problem Statement
At the moment Entitlement Kind-types are partially set directly in
With.Kindand then withinWith.Entitlementsas part of@{}together with Id. This should be improved and simplified.We should rethink the
With.Kindlevel as the StepType doesn't really differ from what it does forKind = 'Group'orAdministrativeUnit. Hence, even mixed situations may make sense or simplify give more flexibility for the Step definitions.Proposed Solution
Only using Kind within
With.Entitlements = @{}hashtables forEnsureEntitlementor withinWith.Keep = @{}hashtables?Alternatives Considered
To be investigated.
Think about provider-specific parts (e.g. 'Administrative Units' do only exist in Entra but not in AD)?
Impact
Additional Context
We should make sure access rights scopes are only activated based on Kind condition.