pivotaljohn

#@data/values
---
ca_certs: []

pivotaljohn

Illustrates a potential "gotcha" with fragment functions (i.e. functions that only contain YAML fragments as opposed to functions that contain other Starlark logic).

$ ytt -f frag-funcs-before.yml

Unmarshaling YAML template 'frag-funcs-before.yml': yaml: line 9: did not find expected <document start>

(see https://gist.github.com/pivotaljohn/992c9bbc3c9f6743a1db8df7bfbe8a24 for a potential solution)

pivotaljohn

Illustrates one way to avoid creating invalid YAML documents while authoring fragment functions in your ytt templates.

(see https://gist.github.com/pivotaljohn/2be1aab1a58c5a8711bfa355de7d8cae)

$ ytt -f frag-funcs-after.yml

output:
 a: b

pivotaljohn

Illustrates how concatenating with the plus operator can lead to a Starlark error.

$ ytt -f concat-with-plus.yml -f values.yml

- unknown binary op: string + int
    in <toplevel>
 concat-with-plus.yml:3 | x: #@ data.values.a + data.values.b

pivotaljohn

#@ load("@ytt:data", "data")

resource_types:
- name: blah
- #@ data.values.emailresourcetype

pivotaljohn

apiVersion: training.eduk8s.io/v1alpha2
kind: Workshop
metadata:
  name: lab-1
spec:
  description: Sample
---
apiVersion: training.eduk8s.io/v1alpha2
kind: Workshop
metadata:

pivotaljohn

apiVersion: training.eduk8s.io/v1alpha2
kind: Workshop
metadata:
  name: lab-1
spec:
  description: Sample
---
apiVersion: training.eduk8s.io/v1alpha2
kind: Workshop
metadata:

pivotaljohn

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/name: prometheus-operator
    app.kubernetes.io/version: v0.39.0
  name: prometheus-operator
  namespace: default
spec:

pivotaljohn

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: ignore-me1
---
apiVersion: v1
kind: Service
metadata:
  name: ignore-me2

pivotaljohn

---
apiVersion: v1000
kind: baz
metadata:
  name: qux
spec:
  specialValue: 41