fix(ipa): Separate the word-count validation for Operation IDs #1114
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Jira ticket: CLOUDP-368244
This PR separates operation ID length validation into dedicated rules, distinct from the existing operation ID validness validation. This allows for more granular control and clearer error messages when operation IDs exceed the recommended 4-word limit.
New operationID length validation rules:
For
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}operation, we will need to:valid-operation-id,andoperation-id-lengthChecklist
Changes to Spectral
Further comments