Skip to content

NIFI-15957 - Do not resolve parameter references when displaying parameter contexts#11267

Open
pvillard31 wants to merge 1 commit into
apache:mainfrom
pvillard31:NIFI-15957
Open

NIFI-15957 - Do not resolve parameter references when displaying parameter contexts#11267
pvillard31 wants to merge 1 commit into
apache:mainfrom
pvillard31:NIFI-15957

Conversation

@pvillard31
Copy link
Copy Markdown
Contributor

Summary

NIFI-15957 - Do not resolve parameter references when displaying parameter contexts

Following changes done in NIFI-15829 we can now have parameters referencing inherited parameters. However, when showing the parameter contexts in the UI the parameters that are referencing parameters are now showing the resolved value instead of the raw reference. While this is not an issue, it can be confusing and we should display the raw reference.

Example:

MyInheritedParameter => MyInheritedValue
MyParameter => #{MyInheritedParameter}

Showing the parameter context in the UI, it would show:

MyParameter => MyInheritedValue

(even though the flow definition does have the reference)

We want to always show:

MyParameter => #{MyInheritedParameter}

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant