Major Description
1. In Ranger's policy creation UI, when a resource (e.g. Hive database or table name) is entered in the Policy Details, the autocomplete feature will proactively present a dropdown of possible matches to known resource names pulled from the service, which the user can then select to populate the fields in the policy.
2. If there is only one match to an existing resource name, then only that single name will be presented in the dropdown.
3. If there are no matches, then the text already entered into the field will be presented in the autocomplete dropdown. This behavior is exactly the same as (2) whether the resource exists or not.
4. While there are some use cases where a policy may need to be created prior to creating the actual resource itself, there is no validation or feedback in the UI to indicate if a resource name already exists. In the case of a simple typo error, this lack of feedback can result in the creation of invalid policies that are then difficult to isolate and fix.
This request is to include some additional feedback ("not found" message or similar) in the UI, to indicate when a resource does not exist. This would also assist in identifying communication issues between Ranger and the backend services.
Attachments
Attachments
Issue Links
- links to
