fix to not omit the user domain when completion search result is empty #2532
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.
Description
We are utilizing Athenz with identical strings set for both user domain and home domain. Consequently, since the member completion search in AthenzUI returns results without the user domain, it becomes impossible to add RoleMembers or GroupMembers that begin with the user domain.
For instance, if both userdomain and homedomain are
personal
:personal.hiragi-gkuth.subdomain.test-service
hiragi-gkuth.subdomain.test-service
as the result.hiragi-gkuth.subdomain.test-servic
because it is not exists.Therefore, I have made a fix ensuring that the AddMember completion returns exactly the input text when the search result is empty.
Contribution Checklist:
Attach Screenshots (Optional)