Permission Set for "Edit/Save" Buttons in Manual Git Mode
Permission Set for "Edit/Save" Buttons in Manual Git Mode
1 vote
We rely heavily on Git manual mode, but the Edit/Save toggle in the header bar only appears for full platform Administrators. We've tried every permission combination we could find related to Git, without success. The Edit/Save buttons simply never render for non-admin users. Is it possible to introduce a permission (or permission set) that grants Git edit/commit capability without requiring full platform Administrator rights?
Use case: As an administrator, I'd like others on my team, who are intentionally not platform admins, to be able to edit and commit changes to Git. All of our changes promote from Test to Prod via GitHub PRs, so we'd like non-admins to be able to commit in manual mode to stage their PRs.
One thing we noticed: if a non-administrator is granted the settings.git.commit/* permission, they can reach the commit page that the "Save" button navigates to (/admin/settings/git/commit) and submit changes there, but they cannot initiate Edit mode, because the Edit/Save buttons never appear for them. Could this capability be tied to (or piggybacked on) the settings.git.commit/* permission so it also surfaces the Edit/Save controls?
97f171af-5cb3-4549-84e1-19ce2e73df79.png
99e50e8b-1187-48fe-96cc-fb853c8ccf52.png
All Comments (2)
@timjacobs We can certainly get this implemented. I think we are leaning back into settings/update for that button but I think that it's an overly permissive permission and we should have something specific for this workflow.
Adam Driscoll
PowerShell Expert and Developer at Devolutions
Awesome, thanks! Definitely would be appreciated, and would make our non-admin user's lives a bit easier. :) We've had a bit of a "hack" work around, exposing a script that POSTs at the /api/v1/gitstatus/edit endpoint that users can run ad-hoc which kicks off edit mode, and they've bookmarked the "/admin/settings/git/commit" page for when they're done. I'll trust your judgement on which permission set is best appropriate for this. Our non-admins typically fall into roles that have the standard "Operator" type permissions, if that's any help.