Skip to content

NIFI-16076: Context path support for NiFi Registry Flow Registry Clie…#11393

Open
PNAC03 wants to merge 1 commit into
apache:mainfrom
PNAC03:context-path-2.10.0
Open

NIFI-16076: Context path support for NiFi Registry Flow Registry Clie…#11393
PNAC03 wants to merge 1 commit into
apache:mainfrom
PNAC03:context-path-2.10.0

Conversation

@PNAC03

@PNAC03 PNAC03 commented Jul 6, 2026

Copy link
Copy Markdown

Summary

NIFI-16076
NIFI-16075

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

…nt and Support for Context Paths on NiFi Registry (NIFI-16075)

@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 proposing this improvement @PNAC03. However, the NiFi Registry project is deprecated for removal as of February 2026, and thus is not in the position to accept substantive feature changes.

I will leave this pull request open for a little while to consider any additional feedback from other maintainers. Given the planned removal, however, it would be best to pursue alternative solutions.

@PNAC03

PNAC03 commented Jul 6, 2026

Copy link
Copy Markdown
Author

I did notice the deprecation. But I felt that for a tool that's come this far, it deserved this bit even if it's going to the archives :)

@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 @PNAC03, I appreciate the willingness to contribute changes. The challenge is availability of cycles for review and future maintenance. I noted two quick items of unrelated changes in the pull request that need to be reverted, but I haven't evaluated the other changes for now.

Comment on lines +59 to +62
@Tags({"kubernetes", "state", "provider", "configmap", "cluster"})
@CapabilityDescription("Provides a State Provider that stores state in a Kubernetes ConfigMap. "
+ "This allows state to be shared across a Kubernetes cluster. "
+ "The State Provider uses the Kubernetes Client to read and write ConfigMaps.")

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 change is unrelated and should be reverted

<dependency>
<groupId>org.apache.nifi</groupId>
<artifactId>nifi-utils</artifactId>
<version>2.4.0</version>

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 change is unrelated and should be reverted.

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