feat(iam): Add PlatformAccess resource for unified user access lifecycle#660
Open
JoseSzycho wants to merge 2 commits into
Open
feat(iam): Add PlatformAccess resource for unified user access lifecycle#660JoseSzycho wants to merge 2 commits into
JoseSzycho wants to merge 2 commits into
Conversation
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
1 participant
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.
Summary
Today, governing whether a user can access the platform requires three separate resources —
UserDeactivation,PlatformAccessApproval, andPlatformAccessRejection— each immutable and each answering only part of the question. Moving a user between states requires delete-then-create sequences with windows of inconsistency, and there is no single place to look to understand why a user cannot access the platform.This PR introduces
PlatformAccess, a single mutable cluster-scoped resource that owns the full access lifecycle for a user. It is the first step in the migration described in #613 and intentionally introduces only the API type; controller logic, webhook updates, and removal of the existing resources are tracked in follow-on issues.Note
The existing
UserDeactivation,PlatformAccessApproval, andPlatformAccessRejectionresources are untouched in this PR. Migration of controllers, the authn webhook, and theValidatingAdmissionPolicyindatum-cloud/datumis tracked in #658, #659, and a separate issue for the admission policy update.