[
https://issues.apache.org/jira/browse/NIFI-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886906#comment-17886906
]
Matt Gilman commented on NIFI-13533:
------------------------------------
[[email protected]] Looks like FileParameterProvider was just renamed [1].
[1] https://issues.apache.org/jira/browse/NIFI-13454
> All ParameterProviders in 2.0.0-M4 fail to fetch parameters with a period in
> the parameter name
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-13533
> URL: https://issues.apache.org/jira/browse/NIFI-13533
> Project: Apache NiFi
> Issue Type: Sub-task
> Affects Versions: 2.0.0-M4
> Reporter: Felix Schultze
> Assignee: Rob Fellows
> Priority: Blocker
> Fix For: 2.0.0-M5
>
> Attachments: Fetch-Parameter-error.jpg, NIFI-13533-M3.mov,
> NIFI-13533-M4-no-period-parameter-group.mov, NIFI-13533-M4.mov
>
>
> All Parameter Providers fail to fetch any parameters which have a period (aka
> dot) in the parameter name.
> Parameter names containing periods work in NiFi 1.x and also worked in NiFi
> 2.0.0 M3, but do NOT work in 2.0.0 M4.
> This is a serious blocker for anyone using Parameter Providers who have
> periods in their parameter names.
> KubernetesSecretParameterProvider 2.0.0-M4 does not allow dots in Keys
> If we create a new parameter (named e.g. "foo.bar") on disk and try to fetch
> it by KubernetesSecretParameterProvider 2.0.0-M4, we always get the error
> message: Parameter sensitivity must be specified for parameter ....
> Dismissing the error does not work an the error occurs again.
>
> If we set the parameter name to fooBar, foo_bar, etc, the fetch is working.
> In M3, dots were working with FileParameterProvider
>
> *Update:*
> *Even if I activate the sensitivity for a parameter, the transmitted JSON
> object "parameterSensitivities" in request always has null values...*
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
