-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add "boot" provisioning script mode #1094
Conversation
Thanks, but please sign the commit for DCO (run |
8f12c26
to
85ba0b3
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.
Thanks
Could you squash commits? |
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.
Thank you for the contribution! I've tested it, and it works well.
I would like to see the misleading hash-bang line issue addressed.
I wouldn't insist on fixing the YAML indentation, but if you edit the PR anyways, then please address that as well.
Signed-off-by: Justin Alvarez <alvajus@amazon.com>
Thanks for all the feedback. I just made all of the changes that were requested regarding the misleading example and the YAML formatting, and also rebased on latest master and squashed into one commit |
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.
Thank you, looks good!
I don't know why the Cirrus CI checks have not been running; I'm going to close this PR and then re-open it, to hopefully trigger them again. |
Doing another cycle of Close+Reopen, as Cirrus-CI seems to be working fine in other repos right now; but still not triggering here. |
Signed-off-by: Jan Dubois <jan.dubois@suse.com>
Allows users to customize their early boot workflow by specifying
bootCmds
. These commands are run bycloud-init-local.service
, which runs beforecloud-init.service
(which only starts after the network is up), and allow users to disable services (as in the example) or run other commands early on in the boot process. More info here.Resolves one of the proposals in #1093