-
Notifications
You must be signed in to change notification settings - Fork 159
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
coreos-boot-edit: add triggering condition on coreos-copy-firstboot-network.stamp #745
Conversation
…etwork.stamp That way we completely avoid mounting `/boot` rw if we don't need to. Also clarify comment about the boot dependency. Additional roles for this service ideally would follow the same pattern. Minor follow-up to coreos#743.
Not tested yet. |
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!
Once we merge coreos-inject-rootmap.service into this, then I think the motivation for using the triggering model proposed here drops a lot because right now we always inject at least So closing this one. (And accordingly, we can indeed drop the stamp file as discussed in #743.) |
Just to be sure, would this mean we get rid of
|
I was arguing for dropping the triggering conditions entirely and just having the unit always run to be consistent, even if in some rare situations it might not have been necessary. We'd still make the call to |
Ahh, got it. 👍 |
That way we completely avoid mounting
/boot
rw if we don't need to.Also clarify comment about the boot dependency. Additional roles for
this service ideally would follow the same pattern.
Minor follow-up to #743.