Repository navigation
Allow all project permissions in Application profiles and Assistant proposals - #172
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
October 27, 2026 19:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Application access profiles previously offered only the 144 default workload permissions, so a Platform Owner could remove rights but could not add Kubernetes or other project services. The editor now offers the complete official project catalogue (916 permissions checked on 2026-10-27), grouped and searchable by service, identifier and description. The 144-right defaults stay unchanged; requester and Application-service-account selections remain separate.
The backend independently checks new publication profiles against the reviewed snapshot or an authenticated live catalogue. The Assistant can add a named service’s rights to existing granular profiles, preserving existing rights and the central owner, targeting both identities or an explicitly selected identity. All proposal paths reject invented permissions. Existing published versions, orders and State bindings are unchanged; acceptance still requires saving and a new publication. Recovery role inventory supports the same permission bounds.
Validation:
Project IAM permissions for Kubernetes are distinct from in-cluster RBAC. No customer Plan/Apply, State repair or production deployment is part of this change. English/German user and contributor guidance is included.
Hosted UI acceptance on the deployed source passed in a fresh guest browser with all non-GET/HEAD requests blocked: 916 selectable project permissions, 144 initial selections per identity, 11 SKE rights added only to the requester (155), Application-service-account selection preserved (144), IAM rights selectable but initially unchecked. Existing single-template-editor navigation and unsaved local draft preservation also passed. No customer Plan/Apply or remote State/lock write was performed.