-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update NiFi configuration in nifikop for NiFi 2.0.0 #360
Comments
+1 |
+1 Are y'all still planning on updating the nifi configuration files for the NiFi 2.0.0 milestones? |
@juldrixx : Do you think it's worth maintaining two branches in nifikop, for example how Apache NiFi team does, for 2.0.0? |
And if people want to use a 1.X version, they'll have to use an older version of the compatible operator.PPaByPark Because otherwise there's a risk that the operator's functionalities will diverge too much, resulting in 2 completely different versions. What's more, version 1.X will no longer be updated, so we'd have to maintain a version of the operator for a version of NiFi that's no longer evolving, when people should just migrate to a newer version of NiFi. |
I am currently upgrading my nifi helm chart 1.26 to nifi 2.0.0-M3 at work. I was thinking whether I should just switch to the nifikop operator instead. Do you have a timeline when nifikop will support nifi 2.00? |
In So in the next release ( |
Any updates post 2.0 release? |
Is your feature request related to a problem?
No
Describe the solution you'd like to see
Update all of the various existing NiFi property templates maintained in nifikop for NiFi 2.0.0. This would include things like
nifi.properties
,logback.xml
,bootstrap.properties
,bootstrap-notifications.xml
, etc.Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: