Skip to content

NIFI-16226 - Parameter Context update fails when adding provider-backed inheritance in a cluster - #11562

Open
pvillard31 wants to merge 3 commits into
apache:mainfrom
pvillard31:NIFI-16226
Open

NIFI-16226 - Parameter Context update fails when adding provider-backed inheritance in a cluster#11562
pvillard31 wants to merge 3 commits into
apache:mainfrom
pvillard31:NIFI-16226

Conversation

@pvillard31

Copy link
Copy Markdown
Contributor

Summary

NIFI-16226 - Parameter Context update fails when adding provider-backed inheritance in a cluster

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

Pull Request Tracking

  • Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
  • Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000
  • Pull request contains commits signed with a registered key indicating Verified status

Pull Request Formatting

  • Pull Request based on current revision of the main branch
  • Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

  • Build completed using ./mvnw clean install -P contrib-check
    • JDK 21
    • JDK 25

Licensing

  • New dependencies are compatible with the Apache License 2.0 according to the License Policy
  • New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

  • Documentation formatting appears as expected in rendered files

@exceptionfactory exceptionfactory left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for addressing this issue @pvillard31. I noted one question around inherited parameter handling.

@exceptionfactory exceptionfactory left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for the updates @pvillard31. On further review, there still appear to be some edge cases, particularly with handling of sensitive parameter values.

} else {
parameterEntity = dtoFactory.createParameterEntity(parameterContext, parameter, revisionManager, parameterContextDAO);
final Parameter entityParameter = locallyOwned ? localParameters.get(parameterDescriptor) : parameter;
parameterEntity = dtoFactory.createParameterEntity(parameterContext, entityParameter, revisionManager, parameterContextDAO);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This appears to be a latent issue, but createParameterEntity() calls createParameterDto(), which substitutes a hard-coded mask string when the Parameter is marked as sensitive. This seems like it will cause issues when persisting the values.

parameterEntity.setParameter(parameterDTO);
} else {
parameterEntity = dtoFactory.createParameterEntity(parameterContext, parameter, revisionManager, parameterContextDAO);
final Parameter entityParameter = locallyOwned ? localParameters.get(parameterDescriptor) : parameter;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It looks like this introduces a discrepancy for how the parameter checking occurs when adding inheritance. This keeps the original value and requested value as the parameter reference #{ParameterName}, but that avoids triggering any changes.

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 this pull request may close these issues.

2 participants