[
https://issues.apache.org/jira/browse/NIFI-16567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142869#comment-18142869
]
Marcos-Dimitris Fetcu commented on NIFI-16567:
----------------------------------------------
[~pvillard] Yes, that would work for my use case. Great idea.
> AzureKeyVaultSecretsParameterProvider's "Key Vault URI" field to accept
> parameters
> -----------------------------------------------------------------------------------
>
> Key: NIFI-16567
> URL: https://issues.apache.org/jira/browse/NIFI-16567
> Project: Apache NiFi
> Issue Type: Wish
> Components: Configuration
> Affects Versions: 2.12.0
> Environment: NiFi 2.12 hosted on a VM running CentOS Linux 7
> Reporter: Marcos-Dimitris Fetcu
> Priority: Minor
>
> In my flow I am currently using *AzureKeyVaultSecretsParameterProvider* to
> retrieve secrets from the key vault.
> On my setup I have *multiple* production and non-production *environments*
> where I have to deploy the Flow Definition JSON, {*}each one having a
> separate corresponding key vault{*}.
> I think it would be a great idea \{*}to make the
> AzureKeyVaultSecretsParameterProvider's "Key Vault URI" field to accept
> parameters{*}, this would \{*}increase reusability and flexibility{*}.
> Now for each environment I have to *manually* go and change the value of the
> "Key Vault URI".
> I was thinking to declare an environment variable containing *the right key
> vault URI* and fetch it as *parameter* using
> {*}EnvironmentVariableParameterProvider{*}, that parameter *could be used to
> populate the AzureKeyVaultSecretsParameterProvider's "Key Vault URI" field.*
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
