Skip to content

Update for NiFi-2.6.0 #391

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update for NiFi-2.6.0 #391

wants to merge 1 commit into from

Conversation

Chaffelson
Copy link
Owner

  1. Updated client for NiFI-2.6.0.
  2. Fixed augmentation system to correctly pass env vars.
  3. Updated contributing guide to explain common issues and how nifi and registry differ on security.
  4. Fixed mustache templates for new NiFi security schemes.
  5. Fixed make file passing through env vars to client generator.
  6. Regenerated full client for 2.6.0

@Chaffelson
Updated client for NiFI-2.6.0. Fixed augmentation system to correctly…
0c1c12a 
… pass env vars. Updated contributing guide to explain common issues and how nifi and registry differ on security. Fixed mustache templates for new NiFi security schemes.Fixed make file passing through env vars to client generator
@Chaffelson Chaffelson changed the title … Update for NiFi-2.6.0 Oct 5, 2025
ottobackwards
ottobackwards approved these changes Oct 7, 2025
View reviewed changes
Copy link
Collaborator

@ottobackwards ottobackwards left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really cannot review this because GitHub is garbage.
The files I looked are are good though,
Let's get it in people's hands!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ottobackwards ottobackwards ottobackwards approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Chaffelson @ottobackwards