fgerlits opened a new pull request, #2069:
URL: https://github.com/apache/nifi-minifi-cpp/pull/2069

   https://issues.apache.org/jira/browse/MINIFICPP-2342
   
   Currently, MiNiFi modifies the installed config files (minifi.properties and 
config.yml) while it runs. This confuses the Windows installer, so changes to 
these config files get lost when MiNiFi is upgraded.
   
   After this change, the minifi.properties, minifi-log.properties and 
minifi-uid.properties files are no longer modified by MiNiFi at runtime, so 
they can be safely replaced by new versions during upgrade. All changes to the 
settings should be put into new files in the minifi.properties.d 
(minifi-log.properties.d, minifi-uid.properties.d) directory; these new files 
will not be touched by the upgrade.
   
   The config.yml file will no longer be installed as part of MiNiFi. If C2 is 
enabled, config.yml will be fetched from the C2 server; otherwise, MiNiFi will 
create a new file with an empty flow, and the user can edit this. Either way, 
config.yml will not be touched by an upgrade.
   
   ---
   
   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:
   - [x] Is there a JIRA ticket associated with this PR? Is it referenced in 
the commit message?
   
   - [x] 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.
   
   - [x] Has your PR been rebased against the latest commit within the target 
branch (typically main)?
   
   - [x] 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](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] 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.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to