bbende opened a new pull request, #9138: URL: https://github.com/apache/nifi/pull/9138
<!-- Licensed to the Apache Software Foundation (ASF) under one or more --> <!-- contributor license agreements. See the NOTICE file distributed with --> <!-- this work for additional information regarding copyright ownership. --> <!-- The ASF licenses this file to You under the Apache License, Version 2.0 --> <!-- (the "License"); you may not use this file except in compliance with --> <!-- the License. You may obtain a copy of the License at --> <!-- http://www.apache.org/licenses/LICENSE-2.0 --> <!-- Unless required by applicable law or agreed to in writing, software --> <!-- distributed under the License is distributed on an "AS IS" BASIS, --> <!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. --> <!-- See the License for the specific language governing permissions and --> <!-- limitations under the License. --> # Summary This pull request adds the ability to upload assets to parameter contexts and then reference them from parameters in the context. This feature is described in [NIFI-12898](https://issues.apache.org/jira/browse/NIFI-12898) and the [feature proposal](https://cwiki.apache.org/confluence/display/NIFI/Asset+Management). A new framework extension - `AssetManager` - is responsible for storing/retrieving assets on the file system. The following REST end-points are added: Create/upload an asset: `POST /parameter-contexts/{id}/assets` List assets: `GET /parameter-contexts/{id}/assets` Get asset content: `GET /parameter-contexts/{id}/assets/{assetId}` The last two end-points are primarily intended to be used when a node joins the cluster for it to compare it's current assets with the coordinator and synchronize it's assets to match. To reference an asset it is done through a normal parameter context update, where a parameter will send no value and instead provide an asset reference: ``` referencedAssets: [ { "id": "assetId1" }, { "id": "assetId2" }, ] ``` The back-end will automatically make the value of the parameter become the concatenated paths of the referenced assets. The following CLI commands were added: ``` nifi create-asset -pcid <param-context-id> -af <full-path-to-a-file> nifi list-assets -pcid <param-context-id> nifi add-asset-reference -pcid <param-context-id> -pn <param-name> -aid <asset-id> nifi remove-asset-reference -pcid <param-context-id> -pn <param-name> -aid <asset-id> ``` When a parameter context is updated, any asset that was previously referenced by a parameter and no longer referenced after the update will be deleted. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] 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 - [X] Build completed using `mvn clean install -P contrib-check` - [X] 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]
