Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALL action not showing properly in the UI when creating a Repository Content Selector privilege via the REST API #497

Open
brenuart opened this issue Oct 20, 2024 · 0 comments
Assignees
Labels
triage Issues that need to be investigated, replicated

Comments

@brenuart
Copy link

brenuart commented Oct 20, 2024

When creating a Repository Content Selector privilege via the REST API, it's possible to set the action as "ALL" instead of specifying each action individually. For example, you can POST the following definition to the /service/rest/v1/privileges/repository-content-selector endpoint:

{
    "contentSelector": "my-selector",
    "name": "test",
    "repository": "my-repo",
    "type": "repository-content-selector",
    "actions": [
        "ALL"
    ],
    "format": "*"
}

However, when you view the privilege details in the UI, none of the actions appear as selected, which can be confusing. Despite the misleading display, the privilege seems to function as expected, allowing the intended actions to be performed.


Tested with Nexus 3.72 and 3.73

@mrprescott mrprescott added triage Issues that need to be investigated, replicated and removed pending labels Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issues that need to be investigated, replicated
Projects
None yet
Development

No branches or pull requests

2 participants