You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to make better use of templating in kubernetesmod and provide context values for the templates. This makes it easier to manage Kubernetes resources with dynamic content based on pillar or other variables.
Describe the solution you'd like
I would like kubernetesmod to support the use of context in templating, similar to how file.managed does in Salt with defaults. This would allow users to provide context values for templates, simplifying the process of managing Kubernetes resources with dynamic content. This would primarily apply to updating the __read_and_render_yaml_file function to support the changes and adding the argument to all of the required functions.
Describe alternatives you've considered
No alternatives considered, similar functionality exists within other salt modules .
Additional context
Adding support for context in templating would enhance the usability of kubernetesmod and align it with the functionality provided by other modules like file.managed in Salt. This feature would be particularly useful for users who manage Kubernetes resources with dynamic content and rely on templating for configuration management.
The text was updated successfully, but these errors were encountered:
djivey
changed the title
[FEATURE REQUEST] Add functionality for using defaults for jinja templating in kubernetesmod.
[FEATURE REQUEST] Add functionality for using context values for jinja templating in kubernetesmod.
Jan 10, 2025
Is your feature request related to a problem? Please describe.
I would like to make better use of templating in kubernetesmod and provide context values for the templates. This makes it easier to manage Kubernetes resources with dynamic content based on pillar or other variables.
Describe the solution you'd like
I would like kubernetesmod to support the use of context in templating, similar to how file.managed does in Salt with defaults. This would allow users to provide context values for templates, simplifying the process of managing Kubernetes resources with dynamic content. This would primarily apply to updating the
__read_and_render_yaml_file
function to support the changes and adding the argument to all of the required functions.Describe alternatives you've considered
No alternatives considered, similar functionality exists within other salt modules .
Additional context
Adding support for context in templating would enhance the usability of kubernetesmod and align it with the functionality provided by other modules like file.managed in Salt. This feature would be particularly useful for users who manage Kubernetes resources with dynamic content and rely on templating for configuration management.
The text was updated successfully, but these errors were encountered: