Skip to content
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

Unable to Create Parameter Context (NiFi 1.16.0+) #305

Closed
ChrisSamo632 opened this issue May 9, 2022 · 0 comments · Fixed by #306
Closed

Unable to Create Parameter Context (NiFi 1.16.0+) #305

ChrisSamo632 opened this issue May 9, 2022 · 0 comments · Fixed by #306
Assignees
Labels

Comments

@ChrisSamo632
Copy link
Contributor

  • Nipyapi version: 0.18.0
  • NiFi version: 1.16.1
  • NiFi-Registry version: 1.16.1
  • Python version: 3.10
  • Operating System: Alpine (Docker Image)

Description

NiPyApi cannot create new Parameter Contexts in NiFi 1.16.0+ due to missing inherited_parameter_contexts field (not defaulted in NiFi, although it probably should be - NIFI-9470.

Suspect updating the create_parameter_context method to accept an optional inherited_parameter_contexts parameters (defaulting to an empty list) then sending that to NiFi as part of the ParameterContextDTO would be a solution - at least until NIFI-9470 is fixed, but actually NiPyApi should probably be updated to handle inherited parameter contexts now that they've been introduced.

What I Did

Attempted to create a Parameter Context in a new instance of NiFi 1.16.1 by calling nipyapi.parameters.create_parameter_context("local")

Urgency

Cannot create Parameter Contexts with NiPyApi (or NiFi Toolkit as a workaround), which means automated deployments to NiFi 1.16.0+ (possibly 1.15.0+) where a Flow includes a Parameter Context is no longer possible.

That said, if the Parameter Context already exists in a Flow Definition within NiFi Registry, it can be imported then subsequently updated within NiFi (assuming that fits with one's deployment workflow).

@Chaffelson Chaffelson self-assigned this May 13, 2022
@Chaffelson Chaffelson added the bug label May 13, 2022
Chaffelson added a commit that referenced this issue May 13, 2022
Added pylint exclusions for known but unimportant complaints
Added workaround for NiFi 9470 by providing default inherited_parameter_contexts per advice from Chris Sampson in NiPyAPI Issue #305
Fixes #305
Updated NiFi and Registry versions in Docker compose configs to use latest 1.16.1 builds

Signed-off-by: Daniel Chaffelson <chaffelson@gmail.com>
Chaffelson added a commit that referenced this issue May 13, 2022
* modify utils.check_version to accept a default version to check against, and remove nested error when version check fails as it is overzealous
Update test file paths in test_utils in case someone runs tests as root which actually can write to fake devices and therefore break the tests
* Updated clients for 1.16
Added pylint exclusions for known but unimportant complaints
Added workaround for NiFi 9470 by providing default inherited_parameter_contexts per advice from Chris Sampson in NiPyAPI Issue #305
Fixes #305
Updated NiFi and Registry versions in Docker compose configs to use latest 1.16.1 builds

Signed-off-by: Daniel Chaffelson <chaffelson@gmail.com>

* Bump version: 0.18.0 → 0.19.0
rsaggino pushed a commit to rsaggino/nipyapi that referenced this issue Nov 2, 2022
* modify utils.check_version to accept a default version to check against, and remove nested error when version check fails as it is overzealous
Update test file paths in test_utils in case someone runs tests as root which actually can write to fake devices and therefore break the tests
* Updated clients for 1.16
Added pylint exclusions for known but unimportant complaints
Added workaround for NiFi 9470 by providing default inherited_parameter_contexts per advice from Chris Sampson in NiPyAPI Issue Chaffelson#305
Fixes Chaffelson#305
Updated NiFi and Registry versions in Docker compose configs to use latest 1.16.1 builds

Signed-off-by: Daniel Chaffelson <chaffelson@gmail.com>

* Bump version: 0.18.0 → 0.19.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants