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

Sidekiq access permission needs an endpoint #424

Open
DrumsnChocolate opened this issue Sep 19, 2024 · 4 comments
Open

Sidekiq access permission needs an endpoint #424

DrumsnChocolate opened this issue Sep 19, 2024 · 4 comments

Comments

@DrumsnChocolate
Copy link
Contributor

It is currently a hassle to modify sidekiq access: we need to go into the ruby console or db console (not sure which), obtain the correct user, switch some flag, and save the user. It would be nice to have some way to set this via the UI.

@DrumsnChocolate
Copy link
Contributor Author

DrumsnChocolate commented Sep 19, 2024

not sure whether an API endpoint already exists to allow for the UI side of things, so I thought I'd raise the issue in amber-api.

@wilco375
Copy link
Contributor

wilco375 commented Oct 8, 2024

I thought ICT committee members automatically get access to sidekiq

@wilco375
Copy link
Contributor

wilco375 commented Oct 8, 2024

Looking at the code I think you're right. We could change it to be a permission, then it will just show up in the user permissions table in the frontend. We can then also just give the committee the permission.

@lodewiges
Copy link
Contributor

Is this a duplicate of #391?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants