gresockj opened a new pull request, #10130: URL: https://github.com/apache/nifi/pull/10130
…bundles during PG replace-request # Summary To validate, start with a fresh NiFi instance, set the admin password, and start up NiFi. Create a process group, and enter it. Copy the process group ID from the URL. Download the following process group replacement entity: [NiFi_Flow.json](https://github.com/user-attachments/files/21395687/NiFi_Flow.json) ``` # In the directory where NiFi_Flow.json is located... PASSWORD=<your NiFi password> TOKEN=$(curl -k -s -X POST "https://localhost:8443/nifi-api/access/token"; \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "username=admin&password=$PASSWORD") PROCESS_GROUP_ID=<The copied process group ID> curl -k -X POST https://localhost:8443/nifi-api/process-groups/$PROCESS_GROUP_ID/replace-requests \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d @NiFi_Flow.json # If necessary, you can grab the latest revision from https://localhost:8443/nifi-api/flow/process-groups/$PROCESS_GROUP_ID?uiOnly=true to specify the next version in the NiFi_Flow.json. ``` The POST command should result in a parameter provider being successfully created, despite it being saved as version 2.5.0-SNAPSHOT in NiFi_Flow.json. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### 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 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 `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- 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]
