IAM Role Assignment #665
Draft
IAM Role Assignment #665
Conversation
This file contains 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
Signed-off-by: Benjamin Ritter <[email protected]>
l0wl3vel
force-pushed
the
feat/role-assignment
branch
from
b1fe2c3 to
cebf615
Compare
Fyusel
reviewed
Feb 7, 2025
stackit/internal/services/resourcemanager/projectroleassignment/resource_test.go
Outdated
Show resolved
Hide resolved
Sure. Just FYI: The Docs generated have a diff outside of the areas I touched. |
added 3 commits
February 10, 2025 09:44
…roup Signed-off-by: Benjamin Ritter <[email protected]>
Signed-off-by: Benjamin Ritter <[email protected]>
Signed-off-by: Benjamin Ritter <[email protected]>
l0wl3vel
force-pushed
the
feat/role-assignment
branch
from
9cd3acd to
b35a03d
Compare
Signed-off-by: Benjamin Ritter <[email protected]>
l0wl3vel
changed the title
Signed-off-by: Benjamin Ritter <[email protected]>
l0wl3vel
force-pushed
the
feat/role-assignment
branch
from
4f27e27 to
a275197
Compare
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.
Reattempts implementing Role Assignment as a separate resource instead of a field in an existing resource, which lead to problems with inherited group membership and general composability.
This attempt should mesh better with the internal behaviour of STACKIT API, which creates an anonymous "association object" when assigning roles: https://docs.stackit.cloud/stackit/en/identity-and-access-management-134415813.html
Currently only implements roles for STACKIT Projects, but most functionality could be broken out as a provider-internal utility to enable role assignments for other resources.
Fixes: #435