-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Separate out a fi.InstallContext #14814
Conversation
Tasks: tasks, | ||
} | ||
i.Build(buildContext) | ||
|
||
// If there is a package task, we need an update packages task |
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 guess the idea is that we know there isn't a Package task? That makes sense if so!
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.
There's only a File and a Service.
@@ -165,16 +146,16 @@ func (i *Installation) buildEnvFile() *nodetasks.File { | |||
sysconfig += key + "=" + value + "\n" | |||
} | |||
|
|||
task := &nodetasks.File{ | |||
task := &nodetasks.InstallFile{File: nodetasks.File{ |
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.
A little awkward codewise, but I see the value!
(Would be great if these ended up as interfaces where the File task could implement both, but we have that conflict on Run... we could get rid of Run maybe, but ... not in this PR!)
/approve Thanks - would be nice if we didn't have to wrap File and Service, but it seems like we're moving forwards here! |
I was actually wrapping in the other direction until I figured I was touching too much code. |
759d2c9
to
9b22483
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb 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 |
This clarifies that the phase that installs the kops-configuration unit needs a lot less state. It sets us up to move more state into
NodeupSubContext
without having to create fake state in the install path.