-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[refactor] make DoInit() a proper controller #3682
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
[refactor] make DoInit() a proper controller #3682
Conversation
// deploymentInitializer detects a deployment type and is able to extract image names from it | ||
type DeploymentInitializer interface { | ||
// Initializer detects a deployment type and is able to extract image names from it | ||
type Initializer interface { |
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.
Why? I think this is focused on Deployments.
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.
it reads a little clearer now, since we're using build.Initializer
and deploy.Initializer
in the same code block
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 with nit: why rename the DeployInitializer?
Codecov Report
|
f3632e8
to
e9e572a
Compare
last piece of the init refactor. this transfer control of the individual pieces of the init flow to their respective components, and refactors the
DoInit()
entrypoint to simply control these components without worrying about their implementations.this PR has no functional change.