Sean

It is certainly possible and you could do this manually via the UI and your
browser and use the browsers dev tools to learn more about the requests.
We have the REST API docs but those aren't always very helpful to
understand the recipe of taking a series of actions.

With NiFi 1.5 host header we made it harder to configure in some cases
which we've relaxed and will arrive in 1.6.0 but i'm not aware of it not
allowing proper functions and of course it was a change made to address a
security concern which since you're running in secure mode I'm guessing
you'll find important.

With regard to the registry I will say that it was designed to be a far
better answer to what templates could never do.  So what you'll work to
learn more about now with templates and a workflow to get you closer the
registry already does very well.  With 1.6.0 you'll also have access to a
nice CLI to use between NiFi and Registry instances for versioned
flows/flow management as well.

Thanks

On Wed, Feb 21, 2018 at 8:42 AM, Jorge Machado <[email protected]> wrote:

> Hi Sean,
>
> Which error are u getting. It the API has the option for it It should
> work.
> may be this helps: https://github.com/hermannpencole/nifi-config
>
> Jorge Machado
>
>
>
>
>
> On 21 Feb 2018, at 13:40, Sean Marciniak <[email protected]> wrote:
>
> Hey Team,
>
> We are currently trying to deploy flow templates to NiFi while its running
> in secure mode over https.
> Do we know if this is possible?
> Is there any documentation about doing this?
>
> I am able to deploy the flow templates when it is running in non secure
> mode, but when we enforce secure mode, we are unable to do it.
>
> We are currently stuck with using NiFiv1.4 due host header issues
> introduced in NiFi 1.5 and nifi registry is a unneeded risk we don't want
> to take.
>
>
> --
> <https://www.beamery.com/>
>
> Sean Marciniak
>
> [email protected]
>
>
> www.beamery.com
>
> Are you ready for GDPR? *GDPR: The Complete Guide for Recruiting Teams
> <https://beamery.com/academy/gdpr-for-recruiting-teams>*
>
>
>

Reply via email to