-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MIWI cluster Dynamic Validation update for strict 1:1 matching for provided Platform Workload Identity to expected OCP Operators #3966
Conversation
744b3ad
to
da1decc
Compare
Please rebase pull request. |
da1decc
to
305400e
Compare
8fb81f7
to
ec9136e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM except for one tiny suggestion on a cx-facing error message.
/azp run e2e |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
E2E failed with a known flake that's already captured in our CI failure epic. I'll wait to run it again until Rajdeep responds to my most recent review. |
…cluster deletion flow
…d platform identity is found
…for unexpected platform workload identity
ec9136e
to
79f70e5
Compare
/azp run ci |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving with some small comments. thank you!
pkg/util/platformworkloadidentity/platformworkloadidentityrolesbyversion.go
Show resolved
Hide resolved
Co-authored-by: Caden Marchese <[email protected]>
cx-facing error message was changed according to feedback.
…ovided Platform Workload Identity to expected OCP Operators (#3966) * ARO-10859 static validation to reject empty or nil PlatformWorkloadIdentityProfile * ARO-10859 avoid using platformWorkloadIdentityRolesByVersion for the cluster deletion flow * ARO-10859 throw an error for create/update flow whenever an unexpected platform identity is found * ARO-10859 update dynamic validation to reject the create/update flow for unexpected platform workload identity * ARO-10859 sort required identities for consistent error messaging * ARO-10859 update empty pwi map validation error message * ARO-10859 update test case name Co-authored-by: Caden Marchese <[email protected]> --------- Co-authored-by: Caden Marchese <[email protected]>
…ovided Platform Workload Identity to expected OCP Operators (#3966) * ARO-10859 static validation to reject empty or nil PlatformWorkloadIdentityProfile * ARO-10859 avoid using platformWorkloadIdentityRolesByVersion for the cluster deletion flow * ARO-10859 throw an error for create/update flow whenever an unexpected platform identity is found * ARO-10859 update dynamic validation to reject the create/update flow for unexpected platform workload identity * ARO-10859 sort required identities for consistent error messaging * ARO-10859 update empty pwi map validation error message * ARO-10859 update test case name Co-authored-by: Caden Marchese <[email protected]> --------- Co-authored-by: Caden Marchese <[email protected]>
…ovided Platform Workload Identity to expected OCP Operators (#3966) * ARO-10859 static validation to reject empty or nil PlatformWorkloadIdentityProfile * ARO-10859 avoid using platformWorkloadIdentityRolesByVersion for the cluster deletion flow * ARO-10859 throw an error for create/update flow whenever an unexpected platform identity is found * ARO-10859 update dynamic validation to reject the create/update flow for unexpected platform workload identity * ARO-10859 sort required identities for consistent error messaging * ARO-10859 update empty pwi map validation error message * ARO-10859 update test case name Co-authored-by: Caden Marchese <[email protected]> --------- Co-authored-by: Caden Marchese <[email protected]>
Which issue this PR addresses:
Fixes ARO-10859
What this PR does / why we need it:
Test plan for issue:
[x] Unit tests were added/updated for the above implementation
[x] Create/Update MIWI cluster in local
[x] CI
[x] e2e
Is there any documentation that needs to be updated for this PR?
Not yet.
How do you know this will function as expected in production?
Feature is not in production yet.