Skip to content

bug: A user without schema rights can still update a dropdown options #6410

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.

Sign up for GitHub

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

Jump to bottom
Open
BeArchiTek opened this issue May 6, 2025 · 0 comments
Open

bug: A user without schema rights can still update a dropdown options #6410

BeArchiTek opened this issue May 6, 2025 · 0 comments
Assignees
@LucasG0
Labels
group/backend Issue related to the backend (API Server, Git Agent) state/backlog This issue is part of the backlog type/bug Something isn't working as expected
Milestone
Backlog

Comments

@BeArchiTek
Copy link
Contributor

Component

API Server / GraphQL

Infrahub version

1.2.8

Current Behavior

A user with no rights regarding the schema, should not be able to add/delete dropdown options.

Expected Behavior

A user with no rights regarding the schema, should not be able to add/delete dropdown options.

Steps to Reproduce

n/a

Additional Information

No response
@BeArchiTek BeArchiTek added the type/bug Something isn't working as expected label May 6, 2025
@exalate-issue-sync exalate-issue-sync bot added the state/need-triage This issue needs to be triaged label May 6, 2025
@dgarros dgarros added the group/backend Issue related to the backend (API Server, Git Agent) label May 6, 2025
@dgarros dgarros removed the state/need-triage This issue needs to be triaged label May 6, 2025
@dgarros dgarros added this to the Backlog milestone May 6, 2025
@exalate-issue-sync exalate-issue-sync bot removed this from the Backlog milestone May 6, 2025
@exalate-issue-sync exalate-issue-sync bot added the state/need-triage This issue needs to be triaged label May 6, 2025
@exalate-issue-sync exalate-issue-sync bot added this to the Backlog milestone May 8, 2025
@exalate-issue-sync exalate-issue-sync bot removed the state/need-triage This issue needs to be triaged label May 8, 2025
@exalate-issue-sync exalate-issue-sync bot added the state/backlog This issue is part of the backlog label May 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LucasG0 LucasG0

Labels
group/backend Issue related to the backend (API Server, Git Agent) state/backlog This issue is part of the backlog type/bug Something isn't working as expected
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@dgarros @BeArchiTek @LucasG0