Open hijakk opened 8 years ago
As an alternative, would supporting a runtime state in the deployment spec be an option? E.g. trying to see if that's just a missing feature from the script or something else.
Definitely, that sounds fine too. Command line could be nice as an extra sanity check for folks when deploying a template too, but we can work with it whatever way makes sense for implementation for you. On Apr 21, 2016 5:46 PM, "Andrew Grande" notifications@github.com wrote:
As an alternative, would supporting a runtime state in the deployment spec be an option? E.g. trying to see if that's just a missing feature from the script or something else.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/aperepel/nifi-api-deploy/issues/15#issuecomment-213184399
Halted services starting themselves after receiving an update is not desirable behavior in our environment. Would it be possible to include a command line flag to keep the process groups from starting before we explicitly tell them to through the UI or REST API?