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
{{ message }}
This repository has been archived by the owner on Sep 5, 2023. It is now read-only.
This is a decent use case where I'd like to look something up with a query within the same file or an external file, and plug it's value into somewhere within a yaml file (terrible statement). This may be something better suited for pure templating, but I think this could reduce some of the needs for templating in general. This needs to be thought out more, but I wanted to capture the idea.
Example:
File 1 - To look up a value I'd like to use in my overlays
---
# "path" key optional and would lookup a reference in the original yaml document?references:
- name: ref1 path: ./file1.yamlquery: some.stuff.here
- name: ref2path: ./file2.yamlquery: other.stuff.here[b]yamlFiles:
- path: /file/to/modify.yamloverlays:
- name: Use ref1query: metadata.labels[app.kubernetes.io/name]value: "%r{ref1}"action: replace
- name: Use ref2query: kindvalue: "%r{ref2}"action: replace
Expected Behavior:
overlay 1 replaces the value of metadata.labels['app.kubernetes.io/name'] with the value of cool
overlay 2 replaces the value of kind with the value banana
I'd like to use this to lookup and reference maps and arrays as well.
A use for this would be I deploy a bunch of stuff with Terraform and then spit it out in an orderly way with a template.
Then I want to populate a yaml based variables file with some of the info that I spit out from the terraform steps by looking up those references from the output to create a new yaml file that is properly configured for my new environment before further automation runs.
The text was updated successfully, but these errors were encountered:
This is a decent use case where I'd like to look something up with a query within the same file or an external file, and plug it's value into somewhere within a yaml file (terrible statement). This may be something better suited for pure templating, but I think this could reduce some of the needs for templating in general. This needs to be thought out more, but I wanted to capture the idea.
Example:
File 1 - To look up a value I'd like to use in my overlays
Instructions file feature usage
Expected Behavior:
metadata.labels['app.kubernetes.io/name']
with the value ofcool
kind
with the valuebanana
I'd like to use this to lookup and reference maps and arrays as well.
A use for this would be I deploy a bunch of stuff with Terraform and then spit it out in an orderly way with a template.
Then I want to populate a yaml based variables file with some of the info that I spit out from the terraform steps by looking up those references from the output to create a new yaml file that is properly configured for my new environment before further automation runs.
The text was updated successfully, but these errors were encountered: