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 was archived by the owner on Dec 11, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: docs/tutorial.md
+18-19Lines changed: 18 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -316,15 +316,14 @@ spec:
316
316
fromImage:
317
317
repo: gcr.io/kuar-demo/kuard-amd64:blue
318
318
parameterConfiguration:
319
-
specToEnvs:
319
+
fromSpec:
320
320
# Skip variable2 from generating a parameter for the workload
321
321
- path: spec.variable2
322
-
render:
323
-
skip: true
322
+
skip: true
324
323
325
324
```
326
325
327
-
The `spec.workload.parameterConfiguration.specToEnvs[].render.skip` boolean indicates whether the environment variable for the element should be generated.
326
+
The `spec.workload.parameterConfiguration.fromSpec[].skip` boolean indicates whether the environment variable for the element should be generated.
Most often expected environment variables at the container do not match Scoby's automatic rendering. All generated environment variables can be renamed using `spec.workload.parameterConfiguration.specToEnvs[].render.key`.
379
+
Most often expected environment variables at the container do not match Scoby's automatic rendering. All generated environment variables can be renamed using `spec.workload.parameterConfiguration.fromSpec[].toEnv.name`.
The value for an environment variable can reference a Secret through the `spec.workload.parameterConfiguration.specToEnvs[].render.valueFromSecret` customization option, that needs the `name` and `key` subelements to be set. In this example we will also be setting the variable name.
541
+
The value for an environment variable can reference a Secret through the `spec.workload.parameterConfiguration.fromSpec[].toEnv.valueFromSecret` customization option, that needs the `name` and `key` subelements to be set. In this example we will also be setting the variable name.
The value for an environment variable can reference a ConfigMap through the `spec.workload.parameterConfiguration.specToEnvs[].render.valueFromConfigMap` customization option, that needs the `name` and `key` subelements to be set.
636
+
The value for an environment variable can reference a ConfigMap through the `spec.workload.parameterConfiguration.fromSpec[].toEnv.valueFromConfigMap` customization option, that needs the `name` and `key` subelements to be set.
638
637
639
638
```yaml
640
639
apiVersion: scoby.triggermesh.io/v1alpha1
@@ -653,10 +652,10 @@ spec:
653
652
fromImage:
654
653
repo: gcr.io/kuar-demo/kuard-amd64:blue
655
654
parameterConfiguration:
656
-
specToEnvs:
655
+
fromSpec:
657
656
# Reference a ConfigMap
658
657
- path: spec.refToConfigMap
659
-
render:
658
+
toEnv:
660
659
valueFromConfigMap:
661
660
name: spec.refToConfigMap.configName
662
661
key: spec.refToConfigMap.configKey
@@ -742,7 +741,7 @@ A destination duck type informs either an URI, a Kubernetes service, or a Kubern
742
741
uri: <uri>
743
742
```
744
743
745
-
Use the built-in function `spec.workload.parameterConfiguration.specToEnvs[].valueFromBuiltInFunc.resolveAddress` on the element that contains the Destination type. As an added feature this example also updates an status element with the resolved address.
744
+
Use the built-in function `spec.workload.parameterConfiguration.fromSpec[].toEnv.valueFromBuiltInFunc.resolveAddress` on the element that contains the Destination type. As an added feature this example also updates an status element with the resolved address.
0 commit comments