Namespace substitution vars

docs/docs/resources/pipeline-components/helm-app.yaml

@@ -3,16 +3,16 @@
   name: helm-app # required
   # Pipeline prefix that will prefix every component name. If you wish to not
   # have any prefix you can specify an empty string.
-  prefix: ${pipeline_name}-
+  prefix: ${pipeline.name}-
   from: # Must not be null
     topics: # read from topic
-      ${pipeline_name}-input-topic:
+      ${pipeline.name}-input-topic:
         type: input # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra
-      ${pipeline_name}-input-pattern-topic:
+      ${pipeline.name}-input-pattern-topic:
         type: pattern # Implied to be an input pattern if `role` is undefined
-      ${pipeline_name}-extra-pattern-topic:
+      ${pipeline.name}-extra-pattern-topic:
         type: pattern # Implied to be an extra pattern if `role` is defined
         role: some-role
     components: # read from specific component
@@ -28,11 +28,11 @@
   # Topic(s) into which the component will write output
   to:
     topics:
-      ${pipeline_name}-output-topic:
+      ${pipeline.name}-output-topic:
         type: output # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra; Will throw an error if `type` is defined
-      ${pipeline_name}-error-topic:
+      ${pipeline.name}-error-topic:
         type: error
         # Currently KPOps supports Avro and JSON schemas.
         key_schema: key-schema # must implement SchemaProvider to use

docs/docs/resources/pipeline-components/kafka-app.yaml

@@ -4,16 +4,16 @@
   name: kafka-app # required
   # Pipeline prefix that will prefix every component name. If you wish to not
   # have any prefix you can specify an empty string.
-  prefix: ${pipeline_name}-
+  prefix: ${pipeline.name}-
   from: # Must not be null
     topics: # read from topic
-      ${pipeline_name}-input-topic:
+      ${pipeline.name}-input-topic:
         type: input # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra
-      ${pipeline_name}-input-pattern-topic:
+      ${pipeline.name}-input-pattern-topic:
         type: pattern # Implied to be an input pattern if `role` is undefined
-      ${pipeline_name}-extra-pattern-topic:
+      ${pipeline.name}-extra-pattern-topic:
         type: pattern # Implied to be an extra pattern if `role` is defined
         role: some-role
     components: # read from specific component
@@ -29,11 +29,11 @@
   # Topic(s) into which the component will write output
   to:
     topics:
-      ${pipeline_name}-output-topic:
+      ${pipeline.name}-output-topic:
         type: output # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra; Will throw an error if `type` is defined
-      ${pipeline_name}-error-topic:
+      ${pipeline.name}-error-topic:
         type: error
         # Currently KPOps supports Avro and JSON schemas.
         key_schema: key-schema # must implement SchemaProvider to use
@@ -49,8 +49,8 @@
   # add the key-value pairs they need.
   app: # required
     streams: # required
-      brokers: ${kafka_brokers} # required
-      schemaRegistryUrl: ${schema_registry.url}
+      brokers: ${config.kafka_brokers} # required
+      schemaRegistryUrl: ${config.schema_registry.url}
     nameOverride: override-with-this-name # kafka-app-specific
     imageTag: "1.0.0" # Example values that are shared between streams-app and producer-app
   # Helm repository configuration (optional)

docs/docs/resources/pipeline-components/kafka-connector.yaml

@@ -2,16 +2,16 @@
   name: kafka-connector # required
   # Pipeline prefix that will prefix every component name. If you wish to not
   # have any prefix you can specify an empty string.
-  prefix: ${pipeline_name}-
+  prefix: ${pipeline.name}-
   from: # Must not be null
     topics: # read from topic
-      ${pipeline_name}-input-topic:
+      ${pipeline.name}-input-topic:
         type: input # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra
-      ${pipeline_name}-input-pattern-topic:
+      ${pipeline.name}-input-pattern-topic:
         type: pattern # Implied to be an input pattern if `role` is undefined
-      ${pipeline_name}-extra-pattern-topic:
+      ${pipeline.name}-extra-pattern-topic:
         type: pattern # Implied to be an extra pattern if `role` is defined
         role: some-role
     components: # read from specific component
@@ -27,11 +27,11 @@
   # Topic(s) into which the component will write output
   to:
     topics:
-      ${pipeline_name}-output-topic:
+      ${pipeline.name}-output-topic:
         type: output # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra; Will throw an error if `type` is defined
-      ${pipeline_name}-error-topic:
+      ${pipeline.name}-error-topic:
         type: error
         # Currently KPOps supports Avro and JSON schemas.
         key_schema: key-schema # must implement SchemaProvider to use

docs/docs/resources/pipeline-components/kafka-sink-connector.yaml

@@ -3,16 +3,16 @@
   name: kafka-sink-connector # required
   # Pipeline prefix that will prefix every component name. If you wish to not
   # have any prefix you can specify an empty string.
-  prefix: ${pipeline_name}-
+  prefix: ${pipeline.name}-
   from: # Must not be null
     topics: # read from topic
-      ${pipeline_name}-input-topic:
+      ${pipeline.name}-input-topic:
         type: input # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra
-      ${pipeline_name}-input-pattern-topic:
+      ${pipeline.name}-input-pattern-topic:
         type: pattern # Implied to be an input pattern if `role` is undefined
-      ${pipeline_name}-extra-pattern-topic:
+      ${pipeline.name}-extra-pattern-topic:
         type: pattern # Implied to be an extra pattern if `role` is defined
         role: some-role
     components: # read from specific component
@@ -28,11 +28,11 @@
   # Topic(s) into which the component will write output
   to:
     topics:
-      ${pipeline_name}-output-topic:
+      ${pipeline.name}-output-topic:
         type: output # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra; Will throw an error if `type` is defined
-      ${pipeline_name}-error-topic:
+      ${pipeline.name}-error-topic:
         type: error
         # Currently KPOps supports Avro and JSON schemas.
         key_schema: key-schema # must implement SchemaProvider to use

docs/docs/resources/pipeline-components/kafka-source-connector.yaml

@@ -3,17 +3,17 @@
   name: kafka-source-connector # required
   # Pipeline prefix that will prefix every component name. If you wish to not
   # have any prefix you can specify an empty string.
-  prefix: ${pipeline_name}-
+  prefix: ${pipeline.name}-
   # The source connector has no `from` section
   # from:
   # Topic(s) into which the component will write output
   to:
     topics:
-      ${pipeline_name}-output-topic:
+      ${pipeline.name}-output-topic:
         type: output # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra; Will throw an error if `type` is defined
-      ${pipeline_name}-error-topic:
+      ${pipeline.name}-error-topic:
         type: error
         # Currently KPOps supports Avro and JSON schemas.
         key_schema: key-schema # must implement SchemaProvider to use

docs/docs/resources/pipeline-components/kubernetes-app.yaml

@@ -3,16 +3,16 @@
   name: kubernetes-app # required
   # Pipeline prefix that will prefix every component name. If you wish to not
   # have any prefix you can specify an empty string.
-  prefix: ${pipeline_name}-
+  prefix: ${pipeline.name}-
   from: # Must not be null
     topics: # read from topic
-      ${pipeline_name}-input-topic:
+      ${pipeline.name}-input-topic:
         type: input # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra
-      ${pipeline_name}-input-pattern-topic:
+      ${pipeline.name}-input-pattern-topic:
         type: pattern # Implied to be an input pattern if `role` is undefined
-      ${pipeline_name}-extra-pattern-topic:
+      ${pipeline.name}-extra-pattern-topic:
         type: pattern # Implied to be an extra pattern if `role` is defined
         role: some-role
     components: # read from specific component
@@ -28,11 +28,11 @@
   # Topic(s) into which the component will write output
   to:
     topics:
-      ${pipeline_name}-output-topic:
+      ${pipeline.name}-output-topic:
         type: output # Implied when role is NOT specified
-      ${pipeline_name}-extra-topic:
+      ${pipeline.name}-extra-topic:
         role: topic-role # Implies `type` to be extra; Will throw an error if `type` is defined
-      ${pipeline_name}-error-topic:
+      ${pipeline.name}-error-topic:
         type: error
         # Currently KPOps supports Avro and JSON schemas.
         key_schema: key-schema # must implement SchemaProvider to use