kubermatic
Restrict project modifications to administrators
What is the problem, where is it and why is it an issue?
Not too long ago, I requested (and it got implemented - thank you!) that project deletion can be restricted to admins, just like project creation could beforehand already. Now I noticed that non-admins can also/still edit the project, i.e. the project name and project labels. Unfortunately, that's also undesired in our use case. Do you think this could be also be disabled, maybe through an additional toggle? 🙈
Suggest how to fix it, if possible Implement an additional toggle in the admin panel under interface > limits to restrict project modifications(?) to administrators. If the toggle is enabled, the "edit" icon should be disabled and greyed out - just like the "delete" icon and the "add project" buttons are if the respective toggles are enabled.
Additional comments Note that I really only mean the changes that are possible on the project overview/list page, i.e. currently that's the project name and project labels. "Inside" the project, no changes should be implemented.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubermatic-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
@csengerszabo: Reopened this issue.
In response to this:
/remove-lifecycle rotten /reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.