Expose ELEMENTAL_CLOUD_INIT_PATHS option #2163
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds the
--cloud-init-paths
argument for allelemental
cli subcommands. This was previously added only forbuild-disk
, but I find it useful in all other cases.The
ELEMENTAL_CLOUD_INIT_PATHS
env variable is also added to achieve the same effect.The reason to introduce this feature is to address corner cases when using
after-install
andafter-reset
, especially the latter since in the default Elemental images,/system/oem
and/usr/local/cloud-config
are read only, and/oem
is going to be formatted before being evaluated.Having a dynamic path to be evaluated at run time allows for more freedom.
This is also an enabler for rancher/elemental-operator#806