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

MINIFICPP-2447 Include the Python processor version in the manifest #1861

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

fgerlits
Copy link
Contributor

https://issues.apache.org/jira/browse/MINIFICPP-2447


Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

  • Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically main)?

  • Is your initial contribution a single, squashed commit?

For code changes:

  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file?
  • If applicable, have you updated the NOTICE file?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

Note:

Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

@fgerlits fgerlits force-pushed the MINIFICPP-2447_Include_Python_processor_version_in_the_manifest branch 4 times, most recently from 11859e5 to c8465fd Compare September 6, 2024 09:42
NiFi python processors which define a ProcessorDetails.version field should
show this version number in the manifest. For all other processors, we will
continue to use the MiNiFi version.
@fgerlits fgerlits force-pushed the MINIFICPP-2447_Include_Python_processor_version_in_the_manifest branch from c8465fd to 211fd33 Compare September 11, 2024 12:08
@fgerlits fgerlits marked this pull request as ready for review September 11, 2024 14:57
Comment on lines +119 to +121
void setVersion(const std::string& version) {
version_ = version;
}
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we could filter empty values to not override the agent version

Copy link
Contributor Author

@fgerlits fgerlits Sep 13, 2024

Choose a reason for hiding this comment

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

Hm, I'm not sure. Is anyone going to set ProcessorDetails.version = ""? If they do, would they expect to see the MiNiFi version in the C2 server GUI?

EDIT: I've changed my mind, because 1: we remove all key-value pairs with empty values when we create the manifest, and 2: our C2 server implementation crashes if it doesn't find a version key in a bundle in the manifest. 521a6c4

@fgerlits fgerlits marked this pull request as draft September 17, 2024 16:29
@fgerlits fgerlits marked this pull request as ready for review September 17, 2024 17:39
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