-
Notifications
You must be signed in to change notification settings - Fork 1.8k
e2e: better method of adding SDK repo replace directive to operator's go.mod #1574
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
187d34d
to
80f29b1
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 after addressing question.
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
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
Description of the change: directly add
replace
directive for the local SDK repo togo.mod
bytes instead of doing a bunch of extra work to usego mod edit
.Motivation for the change: other dependencies may have unresolved tags/commits, ex.
kubernetes-1.14.1
, in a newly-scaffoldedgo.mod
which cause errors during the parse step ofgo mod edit
. Instead of doing extra replace work withsed
or Go, we can skip usinggo mod
entirely and just add areplace
directive for the SDK repo by modifyinggo.mod
bytes directly.