gresockj commented on a change in pull request #5113:
URL: https://github.com/apache/nifi/pull/5113#discussion_r657847936
##########
File path: nifi-stateless/nifi-stateless-assembly/README.md
##########
@@ -427,33 +431,54 @@ Additionally, there may be sensitive parameters that
users prefer not to include
Environment Variables, for example.
These parameters may be passed when running NiFi via the `bin/nifi.sh` script
by passing a `-p` argument.
-When used, the `-p` argument must be followed by an argument in the format
`<context name>:<parameter name>:<parameter value>`
+When used, the `-p` argument must be followed by an argument in the format
`[<context name>:]<parameter name>=<parameter value>`
For example:
```
-bin/nifi.sh stateless -c -p "Kafka Parameter Context:Kafka Topic:Sensor Data"
/var/lib/nifi/stateless/config/stateless.properties
/var/lib/nifi/stateless/flows/jms-to-kafka.properties
+bin/nifi.sh stateless -c -p "Kafka Parameter Context:Kafka Topic=Sensor Data"
/var/lib/nifi/stateless/config/stateless.properties
/var/lib/nifi/stateless/flows/jms-to-kafka.properties
```
Note that because of the spaces in the Parameter/Context name and the
Parameter value, the argument is quoted.
Multiple Parameters may be passed using this syntax:
```
-bin/nifi.sh stateless -c -p "Kafka Parameter Context:Kafka
Brokers:kafka-01:9092,kafka-02:9092,kafka-03:9092" -p "Kafka Parameter
Context:Kafka Topic:Sensor Data" /var/lib/nifi/stateless/config
/stateless.properties
+bin/nifi.sh stateless -c -p "Kafka Parameter Context:Kafka
Brokers=kafka-01:9092,kafka-02:9092,kafka-03:9092" -p "Kafka Parameter
Context:Kafka Topic=Sensor Data" /var/lib/nifi/stateless/config
/stateless.properties
```
-Note also that the Parameter Context Name and the Parameter Name may not
include a colon character.
-The Parameter Value can include colon characters, as in the example here.
+If the name of the Parameter Context contains a colon, it must be escaped
using a backslash.
+The name of the Parameter Context and the name of the Parameter may not
include an equals sign (=).
+The Parameter Value can include colon characters, as well as equals, as in the
example here.
Often times, though, the Parameter Context name is not particularly important,
and we just want to provide a Parameter name.
This can be done by simply leaving off the name of the Parameter Context. For
example:
```
-bin/nifi.sh stateless -c -p "Kafka
Brokers:kafka-01:9092,kafka-02:9092,kafka-03:9092" -p "Kafka Topic:Sensor Data"
/var/lib/nifi/stateless/config /stateless.properties
+bin/nifi.sh stateless -c -p "Kafka
Brokers=kafka-01:9092,kafka-02:9092,kafka-03:9092" -p "Kafka Topic=Sensor Data"
/var/lib/nifi/stateless/config /stateless.properties
```
In this case, any Parameter Context that has a name of "Kafka Brokers" will
have the parameter resolved to `kafka-01:9092,kafka-02:9092,kafka-03:9092`,
regardless of the name
of the Parameter Context.
If a given Parameter is referenced and is not defined using the `-p` syntax,
an environment variable may also be used to provide the value. However,
environment variables typically are
allowed to contain only letters, numbers, and underscores in their names. As a
result, it is important that the Parameters' names also adhere to that same
rule, or the environment variable
-will not be addressable.
\ No newline at end of file
+will not be addressable.
+
+At times, none of the builtin capabilities for resolving Parameters are ideal,
though. In these situations, we can use a custom Parameter Provider in order to
source Parameter values from elsewhere.
Review comment:
I'd add a dash to "built-in".
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
