[strailov]

Introduction

Limits the number of distinct target groups a tenant may create.
Quota check on each write case for target group - create/update (+bulk case) targets if groups is present and assigning group to target(s).
Default quota set to 100 with options to be increased/decreased.

Behaviour

• null group never consumes quota — unassignment always allowed
• Limit <= 0 means unlimited
• Assigning an existing group is always allowed, even for a tenant already over the limit,
  so introducing a limit never breaks existing tenants
• Batches are asserted once against their distinct new groups, so n + k is checked rather
  than n + 1 repeatedly
• Rejection throws AssignmentQuotaExceededException
• Existence is checked before the quota rejection is surfaced in update, so a bad id still
  reports EntityNotFoundException

[avgustinmm]

LGTM, but see comment - maybe better to call method without parentId

[avgustinmm]

why use method with parrentId (when no such) instead of:
public static void assertAssignmentQuota(
final long requested, final long limit,
@NotNull final Class type, @NotNull final Class parentType) {
i.e. parent null?

[strailov]

Because we won't get into :
if (parentId != null && countFct != null) in the assertAssignmentQuota where we want to evaluate currentCount + requested > limit . Didn't want to modify the method just for one parameter, which just needs to be non null (and why not the parent to be the Tenant in the exception message).