[
https://issues.apache.org/jira/browse/NIFIREG-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703881#comment-16703881
]
ASF GitHub Bot commented on NIFIREG-211:
----------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi-registry/pull/148
Just pushed a new commit that allows the client to specify a SHA-256 when
uploading the bundle. If they specify one and it doesn't match what the server
calculates, then it is rejected. If they don't specify one then we accept the
bundle, but we mark a flag called "sha256Supplied" as false, so consumers later
will know if the bundle was uploaded with or without a client provided checksum.
Since the upload is already a multi-part request, I thought it made the
most sense for the SHA-256 to be another field in the multi-part form data. As
an example of a curl command to upload with the checksum:
`curl -v -F file=@./nifi-example-processors-nar-1.0.0.nar
-Fsha256=93d2c6537142497ca3f908452d3c3c2bcae928fdc07e1b48fd3ba95ec22bc639
"http://localhost:18080/nifi-registry-api/buckets/72f897d9-5645-4168-852f-4885cc7c9cfe/extensions/bundles/nifi-nar";
`
> Add extension bundles as a type of versioned item
> -------------------------------------------------
>
> Key: NIFIREG-211
> URL: https://issues.apache.org/jira/browse/NIFIREG-211
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Major
> Fix For: 0.4.0
>
>
> This ticket is to capture the work for adding extension bundles to NiFi
> Registry.
> This work may require several follow on tickets, but at a high-level will
> include some of the following:
> - Add a new type of item called an extension bundle, where each bundle
> can contain one ore extensions or APIs
>
> - Support bundles for traditional NiFi (aka NARs) and also bundles for
> MiNiFi CPP
>
> - Ability to upload the binary artifact for a bundle and extract the
> metadata about the bundle, and metadata about the extensions contained
> in the bundle (more on this later)
>
> - Provide a pluggable storage provider for saving the content of each
> extension bundle so that we can have different implementations like
> local fileysystem, S3, and other object stores
>
> - Provide a REST API for listing and retrieving available bundles,
> integrate this into the registry Java client and NiFi CLI
> - Security considerations such as checksums and cryptographic signatures for
> bundles
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
