-
Notifications
You must be signed in to change notification settings - Fork 131
[GEP-28] Fix panic if provider does not support Driver.InitializeMachine #1032
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
Conversation
|
Thank you @maboehm for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below. |
timebertt
left a comment
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! lgtm
aaronfern
left a comment
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 for the fix!
/lgtm
… (#1047) Co-authored-by: Marcel Boehm <[email protected]>
…ener#1032) (gardener#1047) Co-authored-by: Marcel Boehm <[email protected]>
…ener#1032) (gardener#1047) Co-authored-by: Marcel Boehm <[email protected]>
What this PR does / why we need it:
/kind bug
Fixes a small bug introduced in #1012, where a panic can occur if the provider does not implement the
InitializeMachinefunction. This code path can only be reached when running without a target-client (gardenadmscenario)Which issue(s) this PR fixes:
Special notes for your reviewer:
Release note: