Specify inclusion type

[mihai-stancu]

Hi,

I sometimes need to define a YAML text node that contains text which will be treated as YAML (or JSON). For example helm

apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: some-config
spec:
  valuesContent: |-
     val1: 'this'
     val1: 'that'

I'd rather use a separate file, but that file should also be a *.yml file (for syntax highlighting).
Currently !include some-config-values.yml would treat it as a YAML and inline it as an object node.

Would it be possible to specify an extra parameter !include txt some-config-values.yml?

[leNEKO]

Hello,

I can see the use cases, i add something like this for the next version.

# content.yml
val1: 'this'
val2: 'that'

# main.yml
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: some-config
spec:
  valuesContent: !include { "path": "content.yml", "extension": "txt" }

[mihai-stancu]

Lovely to hear! The idea with the object spec sounds great to differentiate the use cases.

.path is clear & intuitive.

However .extension to me indicates an actual value discernible from the filename, not how to interpret/treat the contents.

Throwing in some suggestions:

• .type -- descriptive of the role
• .as -- pseudo-syntaxtic (it makes the object to "look" like a sentence)
• .kind -- descriptive of the role
• .role -- descriptive of the role
• .contains -- describes what the content is

Happy holidays!