feat(talos): Allow users to include talhelper patches #1320
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.
Talhelper allows us to include external patch files outside of the main
talconfig.yaml
. We can use this feature to allow the user to create patches that can be maintained separately from the template generated talconfig. This can be used similarly to this PR for talos specific overrides.When enabling
distribution.talos.user_patches
the includes for the following files are added to the generated talconfig.yaml. These patches are applied to the talconfig file's sections of the same name.nodes.inventory.[].name
)I haven't figured out how to get
makejinja
(or similar like ansible/go-task) to optionally generate these as empty files if they don't already exist. The goal is to not stomp these files each time we update our local repo with the latest changes from the template repo. These are particularly useful for nodes that have specific differences from the global defaults due to different worker hardware, existance as a virtual machine, or similar.