Closed syacko closed 3 years ago
Yeah the consumer config don’t hold the stream name only the api call does. So the idea is you can use a consumer config on different streams uncanged
so you have to give the stream name as a argument “nats c create STREAM —config x.json”
When running NATS CLI (v.0.0.21) and using the --output option, the stream name is not recorded.
When you run this output file as input using the --config option, the Steam name is prompted. This will cause an automated process for the installation of a consumer to hang.
Here is what happens when the above list.of.values file is used to create the consumer.
Running on Mac OS 11.2.1