Kylo assigns "Controller Service" to the NiFi processor's property even though it had "No value set" during template registration.

Description

I have feed template which uses “InvokeHTTP” processor. One of its properties is “SSL Context Service” which is not required field and I need it to have “No value set”. When I import my NiFi template to Kylo (and value of this property is not assigned in NiFi and left untouched during Kylo Template Registration) and create a feed this property is getting assigned controller service: “StandardSSLContextService”. To deal with this bug I have to manually remove this value (to get “No value set”) after feed creation. Moreover when I update my feed in Kylo e.g. change “Schedule” options the property is getting assign context service once again. This behaviour is currently affecting QA environment for the customer and soon will be affecting Production as well. It also happens for other processors e.g. “ListS3” or “FetchS3Object”.

Environment

None

Status

Assignee

Unassigned

Reporter

Marcin Armata

Labels

None

Reviewer

None

Story point estimate

None

Components

Priority

Highest