Github user scottyaslan commented on the issue:
https://github.com/apache/nifi/pull/2081
Thanks @yuri1969 this has been merged to master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user yuri1969 commented on the issue:
https://github.com/apache/nifi/pull/2081
A misclick, sorry.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user yuri1969 commented on the issue:
https://github.com/apache/nifi/pull/2081
OK, @scottyaslan and @moranr. I'll try to push an update tomorrow.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user moranr commented on the issue:
https://github.com/apache/nifi/pull/2081
@scottyaslan â agreed, likely a larger and separate effort to know all
existing CSs. I'll create a new jira to capture the idea.
I think your suggestion as a first step is a good one. One
Github user scottyaslan commented on the issue:
https://github.com/apache/nifi/pull/2081
@moranr I am not sure we could do that (currently) without the UI knowing
how many CS's are named 'StandardSSLContextService-*' . I think that would
require a bit more effort to create some REST
Github user moranr commented on the issue:
https://github.com/apache/nifi/pull/2081
This will be a nice addition from a usability perspective.
It could be helpful to go ahead and generate a default name for the service
following some type of simple naming convention (e.g.,
Github user scottyaslan commented on the issue:
https://github.com/apache/nifi/pull/2081
Reviewing...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
