github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-03-09 07:13:36 -05:00
Code Issues 258 Packages Projects Releases 10 Wiki Activity

[feature request] permision handling #167

New Issue
Closed
opened 2025-10-31 15:03:47 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-10-31 15:03:47 -05:00
Owner
Copy Link

Originally created by @ValgulNecron on GitHub (Dec 28, 2024).

Hi at the moment if i give write per on a server, and also want this user to have access to stack, builder, etc.... on this server i need to manually give him.

i would really like if either write perm on a serve give access to stack and other stuff linked to this server or a "server admin" perm that would do the same without altering the already existing level.

Originally created by @ValgulNecron on GitHub (Dec 28, 2024). Hi at the moment if i give write per on a server, and also want this user to have access to stack, builder, etc.... on this server i need to manually give him. i would really like if either write perm on a serve give access to stack and other stuff linked to this server or a "server admin" perm that would do the same without altering the already existing level.
GiteaMirror added the enhancement label 2025-10-31 15:03:47 -05:00
GiteaMirror commented 2025-10-31 15:03:48 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Jan 2, 2025):

Yeah, I think the permissions regarding Server itself, vs Deployment / Stack that is on a Server, is a bit awkward currently.

@mbecker20 commented on GitHub (Jan 2, 2025): Yeah, I think the permissions regarding `Server` itself, vs `Deployment / Stack` that is _on_ a `Server`, is a bit awkward currently.
GiteaMirror commented 2025-10-31 15:03:48 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Aug 26, 2025):

It doesn't really fit the permission model to make this change. It keep everything straightforward to enumerate user access to resources. There are layer-able User Groups so it doesn't get too repetitive with many users too.

@mbecker20 commented on GitHub (Aug 26, 2025): It doesn't really fit the permission model to make this change. It keep everything straightforward to enumerate user access to resources. There are layer-able User Groups so it doesn't get too repetitive with many users too.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#167
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?