-
Notifications
You must be signed in to change notification settings - Fork 226
fix for OCPBUGS-55135: userDataSecret.name should be a Required value on AWS #1399
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
Merged
openshift-merge-bot
merged 7 commits into
openshift:main
from
germanparente:gparente-fix55135
Aug 12, 2025
Merged
Changes from 2 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b80bdd5
fix for OCPBUGS-55135: userDataSecret.name should be a Required value…
germanparente 403c9cb
fix (reviewed) for OCPBUGS-55135: userDataSecret.name should be a Req…
germanparente cc136d1
fix (reviewed) for OCPBUGS-55135: userDataSecret.name should be a Req…
germanparente dae7665
fix (reviewed) for OCPBUGS-55135: userDataSecret.name should be a Req…
germanparente ef5d3f2
Adding unit test for providerSpec.userDataSecret.name
germanparente c25f257
Update pkg/webhooks/machine_webhook.go
germanparente 1682aa6
Update pkg/webhooks/machine_webhook_test.go
germanparente File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
I suspect we still want this, and the new validation. Though looking at the new defaulting, can we ever get here?
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.
Thanks @JoelSpeed
My understanding was that there's a test that is checking that we can remove completely:
userDataSecret:
name: xxxxx
That's why I have switched to validate only that the name cannot be empty if the sctructure exists that is what the ocpbugs states as improvement.
If I re-add those lines and there's a test removing the full userDataSecret information, we will have the failure.