Conversation
@@ -87,6 +87,7 @@ Arbitrary systemd units may be provided in the `coreos.units` attribute. | |||
|
|||
- **name**: String representing unit's name. Required. | |||
- **runtime**: Boolean indicating whether or not to persist the unit across reboots. This is analagous to the `--runtime` argument to `systemd enable`. Default value is false. | |||
- **enable**: Boolean indicating whether or not to enable the given unit. Default value is false. |
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.
Can you explain what enabling a unit gets you? (Starts after reboot, right?)
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.
That's one effect enabling a unit can have, but that's not the only thing. It essentially takes the [Install]
section of your unit and handles each of the directives you define.
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.
Perhaps refer to [Install]
in the description? enable
vs start
and what [Install]
can do tends to not be obvious to people new to systemd so some hint would be useful.
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.
Added a note
@marineam This feature is just for you ❤️ |
Fix #69 - A user may provide an `enable` attribute of a unit in their cloud config document. If true, coreos-cloudinit will instruct systemd to enable the associated unit. If false, the unit will not be enabled. Fix #71 - The default enable behavior has been changed from on to off.
lgtm |
Fix #71
Fix #69