You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sensitive Parameters are often best managed externally from NiFi, where they can be better protected (and/or shared with outher applications as appropriate).
Describe the solution you'd like to see
NiFi allows for the use of Parameter Providers in order to externalise sensitive parameters, e.g. as Kubernetes Secrets, AWS Systems Manager Parameters, AWS Secrets, etc.
Adding the ability to configure Parameter Providers as part of a NiFi Cluster deployment by NiFiKop could help with secure and configurable deployments, particularly in multi-environment setups.
Describe alternatives you've considered
Manually configuring the Parameter Providers within the deployment
Using NiFi Toolkit/NiPyApi to script the connectivity as part of a post-deployment Job
Additional context
No response
The text was updated successfully, but these errors were encountered:
At some point, when the feature was released, I thought of implementing it but I never had the time to do it. But it sure a feature that is interesting to implement.
The Kubernetes Secrets is in someway already usable with the NifiParameter resource and its secretRef field.
Is your feature request related to a problem?
Sensitive Parameters are often best managed externally from NiFi, where they can be better protected (and/or shared with outher applications as appropriate).
Describe the solution you'd like to see
NiFi allows for the use of Parameter Providers in order to externalise sensitive parameters, e.g. as Kubernetes Secrets, AWS Systems Manager Parameters, AWS Secrets, etc.
Adding the ability to configure Parameter Providers as part of a NiFi Cluster deployment by NiFiKop could help with secure and configurable deployments, particularly in multi-environment setups.
Describe alternatives you've considered
Additional context
No response
The text was updated successfully, but these errors were encountered: