[nifi-registry] Made compatible with apache/nifi >= 1.19.0 #285
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jrebmann Can you please bump the chart version so we can merge this PR into main? |
|
@VladStarr Thank you for reviewing my pull request :) I have upgraded the version to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This bugfix is completely analogous to the pull request cetic/helm-nifi#314.
This pull request allows apache/nifi-registry versions >=0.19.0 to be released with this helm chart.
As described in issue cetic/helm-nifi#313, this only required the keystore type to be explicitly set to JKS when calling keytool to be compatible with Java 11.
This change is backward compatible with Java 8.