Russell, You're right that we don't really cover it. The truth is that it wasn't supposed to be optional - we just made a mistake a forgot it. One of our feature proposals would have us build a registry concept for extensions and templates and once we have that then the base build should be a good bit smaller and you'll only pull things in by indicating you want them.
For now, you can simply give the URL of the aws processor nar bundle to the ops team so they know to include that nar in the deployed directory of nifi/lib. Thanks Joe On Tue, Sep 1, 2015 at 3:13 PM, Russell Whitaker <[email protected]> wrote: > Apologies if this is off-topic for this list (user@ instead?) but I > need these Nifi > processor types for a dataflow: > > GetSFTP > PutS3Object > > AFAICT, GetSFTP is available out-of-the-box, but pre-0.3.0, > PutS3Object needs to be installed separately as nifi-aws-bundle, > correct? > http://mvnrepository.com/artifact/org.apache.nifi/nifi-aws-bundle/0.2.1 > > If not, please advise; if so, what's the guidance I should give to our > Operations > team for the work ticket I need to open up at my company to specify > the work? Something > of this form, perhaps? > > 1.) Go to the Admin Guide section of http://nifi.apache.org/docs.html > and download the base artifact(s) as directed; > 2.) Modify top-level Nifi pom.xml to include nifi-aws-bundle as a dependency; > 3.) Do maven build/install. > > The existing docs don't address the case of "build base system along > with optional > processor bundles"... or am I overlooking documentation which covers this > case? > > Thanks in advance, > Russell > > -- > Russell Whitaker > http://twitter.com/OrthoNormalRuss > http://www.linkedin.com/pub/russell-whitaker/0/b86/329
