Skip to content

consistent use of TYPE_PRINCIPAL_NAME type when validating principal names#3302

Merged
psasidhar merged 1 commit intomasterfrom
princ
Apr 13, 2026
Merged

consistent use of TYPE_PRINCIPAL_NAME type when validating principal names#3302
psasidhar merged 1 commit intomasterfrom
princ

Conversation

@havetisyan
Copy link
Copy Markdown
Collaborator

@havetisyan havetisyan commented Apr 13, 2026

Description

Contribution Checklist:

  • The pull request does not introduce any breaking changes
  • I have read the contribution guidelines.
  • Create an issue and link to the pull request.

Attach Screenshots (Optional)

…names

Signed-off-by: Henry Avetisyan <hga@yahooinc.com>
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates multiple validation calls within ZMSImpl and ZTSImpl to use TYPE_PRINCIPAL_NAME instead of inconsistent types like TYPE_SERVICE_NAME, TYPE_ENTITY_NAME, TYPE_RESOURCE_NAME, and TYPE_MEMBER_NAME. This change ensures that principal names are validated against the correct schema across various service endpoints. I have no feedback to provide.

@psasidhar psasidhar merged commit 97e9e85 into master Apr 13, 2026
8 checks passed
@psasidhar psasidhar deleted the princ branch April 13, 2026 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants