The namespace-configuration-operator helps keeping configurations related to Users, Groups and Namespaces aligned with one of more policies specified as a CRs
apiVersion: v1
kind: Namespace
metadata:
annotations:
parentOperatorCreatedOn: '{{ (lookup "v1" "Namespace" "" "namespace-configuration-operator").metadata.creationTimestamp }}'
sourceTemplate: "{{ toYaml . | b64enc }}"
require: '{{ required "Annotations on the Group are required!" .Annotations.test }}'
name: {{ .Name | lower }}
I then switched out the lower function to upper, shuffle, etc for testing
I switched out the toYaml function with toJson, toToml, etc
Then there are specific tests in the above example for required and lookup, both custom functions defined in operator-utils.
raffaelespazzoli
commented
4 years ago
Tested using the following template
templates:
I then switched out the lower function to upper, shuffle, etc for testing I switched out the toYaml function with toJson, toToml, etc Then there are specific tests in the above example for required and lookup, both custom functions defined in operator-utils.