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

[mostly docs]: Vendor data scripts not explained well #5765

Open
TheRealFalcon opened this issue Oct 1, 2024 · 0 comments
Open

[mostly docs]: Vendor data scripts not explained well #5765

TheRealFalcon opened this issue Oct 1, 2024 · 0 comments
Labels
documentation This Pull Request changes documentation

Comments

@TheRealFalcon
Copy link
Member

Looking at https://docs.cloud-init.io/en/latest/reference/modules.html#scripts-vendor,

Any scripts in the scripts/vendor directory in the datasource will be run when a new instance is first booted. Scripts will be run in alphabetical order.

What does "in the datasource" mean? How would a user know if this refers to /var/lib/cloud/scripts/vendor or /var/lib/cloud/instance/scripts/vendor? It is in fact /var/lib/cloud/instance/scripts/vendor, so why are we even providing this detail as it's an implementation detail of vendor data? Vendors can't put their own scripts there unless they were to know the uuid of the instance before the instance launched.

This module allows control over the execution of vendor data.

This might be overly pedantic, but it allows control over the processing of vendor data. If a script sits in that directory, it'll get run regardless, but {vendor_data: {enabled: False}} means we're never write out the script in the first place, not that the directory won't get executed.

Also, I don't see why /var/lib/cloud/scripts/vendor exists. I don't see it being used anywhere and if I drop a script in there it does not get run on boot.

@TheRealFalcon TheRealFalcon added documentation This Pull Request changes documentation new An issue that still needs triage labels Oct 1, 2024
@aciba90 aciba90 removed the new An issue that still needs triage label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation This Pull Request changes documentation
Projects
None yet
Development

No branches or pull requests

2 participants