Skip to content

NIFI-15870 Improve error message for enabled controller service refer…#11294

Closed
venkateshwaracholan wants to merge 1 commit into
apache:mainfrom
venkateshwaracholan:NIFI-15870
Closed

NIFI-15870 Improve error message for enabled controller service refer…#11294
venkateshwaracholan wants to merge 1 commit into
apache:mainfrom
venkateshwaracholan:NIFI-15870

Conversation

@venkateshwaracholan
Copy link
Copy Markdown
Contributor

@venkateshwaracholan venkateshwaracholan commented May 28, 2026

Improved controller service reference error messages for parameter updates and removals
Replaced StandardControllerServiceNode object rendering with structured controller service details
Added concise state guidance indicating the controller service must be DISABLED

Summary

NIFI-15870

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

Copy link
Copy Markdown
Contributor

@exceptionfactory exceptionfactory left a comment

Choose a reason for hiding this comment

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

Thanks for attempting to address this Jira issue @venkateshwaracholan.

This Jira issue should have been closed following the original pull request.

In general, submitting a new pull request for a Jira issue with a previous pull request should include coordinating with the current assignee, or asking a question for direction, rather than proceeding to submit a new PR.

Based on this status, I am closing this PR.

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.

2 participants