Skip to content
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

Fix handling of undefined fields for mustonlyhave #223

Conversation

dhaiducek
Copy link
Member

@dhaiducek dhaiducek commented Apr 3, 2024

If a field exists in the existing object but wasn't defined for a mustonlyhave policy, we need to check the existing object's fields and set them accordingly, particularly to set them to null.

@dhaiducek
Copy link
Member Author

/hold to tag to an issue

@dhaiducek
Copy link
Member Author

/unhold

Signed-off-by: Dale Haiducek <19750917+dhaiducek@users.noreply.github.com>
If a field exists in the object but wasn't defined
for a mustonlyhave policy, we need to check the
existing object's fields and set them accordingly,
particularly to set them to null.

ref: https://issues.redhat.com/browse/ACM-10877

Co-authored-by: Matt Prahl <mprahl@users.noreply.github.com>
Signed-off-by: Dale Haiducek <19750917+dhaiducek@users.noreply.github.com>
Copy link

openshift-ci bot commented Apr 11, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhaiducek, mprahl

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dhaiducek dhaiducek deleted the e2e-list-handling branch April 11, 2024 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants