Skip to content
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

update: Add cloud-boothook tip for user data #443

Merged
merged 2 commits into from
Dec 18, 2024

Conversation

ramimac
Copy link
Contributor

@ramimac ramimac commented Dec 15, 2024

Throwing this up, but let me know if I'm missing something - we're outside my wheelhouse :).

My understanding is #cloud-boothook is a straightforwardly better approach than the current documented cloud-config, and also is what dagrz uses in the linked source

@Frichetten
Copy link
Contributor

What about #cloud-boothook makes it a better approach? :o Here, we set the parameter to always so it runs each time the instance is restarted. I think that's the same as #cloud-boothook?

I'm not opposed to the addition, just want to make sure I understand.

@ramimac
Copy link
Contributor Author

ramimac commented Dec 16, 2024

I left the current details because I think it's useful to present both. Functionally, they're similar (as far as I know). I find it much easier to mentally model, remember, and use the one-line prefix ("Add #cloud-boothook, then your commands, at the top of user data") than the current guidance.

Maybe just a matter of preference? Either way I think including #cloud-boothook somehow will be useful, no strong feelings on how/where!

@Frichetten
Copy link
Contributor

Gotcha, no worries, that sounds reasonable to me! I'll merge this PR and add an item to include an example for #cloud-boothook. Thank you for contributing!

@Frichetten Frichetten merged commit 94d99fa into Hacking-the-Cloud:main Dec 18, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants