Our Partner IAM system (which is used by APIs for Zalando's partner-facing UIs) has scope naming rules which don't fit to the naming convention in rule 225 (it uses / instead of .).
This causes violations when checking APIs which declare such scopes in our linter.
We should add an exception to the rule, maybe in this form:
This naming convention applies to Zalando IAM's scopes in service-to-service tokens. For IAM systems with other naming rules (e.g. Zalando Partner IAM), the naming convention is to be applied analogously.
We can then add a configuration to Zally for excluding scopes for specific IAM systems from the checking of this rule (or potentially add an alternative regexp).
Our Partner IAM system (which is used by APIs for Zalando's partner-facing UIs) has scope naming rules which don't fit to the naming convention in rule 225 (it uses
/instead of.).This causes violations when checking APIs which declare such scopes in our linter.
We should add an exception to the rule, maybe in this form:
We can then add a configuration to Zally for excluding scopes for specific IAM systems from the checking of this rule (or potentially add an alternative regexp).