[Backport] Coerce blank fields to null in ApiKey requests #66315
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.
API Key request objects (
InvalidateApiKeyRequestandGetApiKeyRequest) support multiple key-selection parameters such asrealm-name, user-name, key-id and key-name.
The specified behaviour is that if any of these are blank then they
act as a wildcard and do not restrict the search criteria.
This change moves the "is blank" logic into the constructor for these
requests so that there is a single consistent way to determine blank
(
Strings.hasText(arg) == false) and all usage of these fields canrely on the getter returning either
nullor a real value, andnever a non-null blank.
Backport of: #66240