Re: [DISCUSS] UI Contributions
I also agree with this stance for an initial period of transition time, but this obviously has a huge impact on contributions. Without any kind of end date, I worry this is going to be policy indefinitely. Because of this, I tend to agree with what Rob said in the previous email. Maybe once 2.0 is released, that's the end of this transition period where UI features must be implemented twice (unless desired or needed for backward compatibility, as Rob pointed out). On Wed, Apr 24, 2024 at 8:17 AM Robert Fellows wrote: > The new UI has progressed quite well and I agree with this stance. However, > with 2.0 getting close, one could argue that new UI features should > definitely land in the new UI but only really need to land in the original > UI if desired or to support backward compatibility. > > --Rob > > On Tue, Apr 23, 2024 at 7:55 PM Scott Aslan wrote: > > > Thanks for sending this out Matt! I agree that at this point any new > > features to the frontend should be implemented in both the new and the > > existing UI. Updating the contributions guidelines seems appropriate as > > well. > > > > -Scott > > > > On Tue, Apr 23, 2024 at 4:07 PM Matt Gilman wrote: > > > > > Team, > > > > > > Substantial progress has been made on modernizing the NiFi UI under [1] > > and > > > [2]. As detailed in the JIRAs, this effort has been largely motivated > by > > > moving away from deprecated and unsupported dependencies. As we begin > the > > > process to transition to the new UI, we are at a point where any UI > > > contributions should target both the new UI and the existing UI. We've > > > updated the PR template detailing this and the README for the new UI > [3] > > to > > > help introduce folks making UI contributions to the layout of the > > > repository. It discusses the steps needed to build NiFi with the new UI > > > included and how to access it. > > > > > > Happy to discuss any questions folks may have. > > > > > > Matt > > > > > > [1] https://issues.apache.org/jira/browse/NIFI-11481 > > > [2] https://issues.apache.org/jira/browse/NIFI-12400 > > > [3] https://github.com/apache/nifi/pull/8693 > > > > > > > > -- > --- > Rob Fellows >
Re: additional credential needed in S3 connection
Hi Glenda, Looking at the documentation, an approach you could take is to create an AWSCredentialsProviderControllerService[1] as your AWS Credentials Provider Service property value in the PutS3Object processor configuration properties. You can assign a value to the access key and secret key properties of the controller service. I have not done this myself, so hopefully others can chime in to verify if this is the correct approach or not. Hope that helps. Best, Shane [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-aws-nar/1.23.0/org.apache.nifi.processors.aws.credentials.provider.service.AWSCredentialsProviderControllerService/index.html On Tue, Feb 13, 2024 at 3:59 PM Glenda Ramos wrote: > Hi, > > > > We are currently testing Apache NiFi 1.23.0 specifically the "PutS3Object" > processor to automatically transfer data from remote site to an "internal" > S3 bucket. The standard AWSCLI commands work and able to connect the bucket > because we are able to pass in additional credentials like the > AWS_CA_BUNDLE environment variable. That being said, we need AWS_CA_BUNDLE > property added in order to connect successfully to our S3 bucket using > Apache NiFi's "PutS3Object". I have tried passing this as a Parameter and > made it available to the flow but it's not being used by the "PutS3Object" > processor to connect. Is there a way we can add an additional property for > the AWS credentials/config file? It looks like it's only looking for > "accessKey" and "secretKey". > > > > Any help would be greatly appreciated. > > > > Respectfully, > > Glenda Ramos > > Application Engineer >
Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2
+1 (non-binding). Performed all verification steps listed in the helper guide and ran the demo app. Thanks for RMing, Scott! On Wed, Jan 26, 2022 at 9:12 AM Matt Gilman wrote: > +1 (binding) Release this package as nifi-fds-0.3.0 > > Ran through release helper. Looks good. Thanks for RMing Scott! > > Matt > > On Tue, Jan 25, 2022 at 4:41 PM Scott Aslan wrote: > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > Flow Design System nifi-fds-0.3.0. > > > > The source zip, including signatures, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0 > > > > The Git tag is nifi-0.3.0-RC2 > > The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807 > > > > > https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807 > > > > Checksums of nifi-fds-0.3.0-source-release.zip: > > SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd > > SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff > > SHA512: > > > > > 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9 > > > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/scottyaslan.asc > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > > > 17 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12345959 > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.0 > > > > The vote will be open for 72 hours. > > Please download the release candidate and evaluate the necessary items > > including checking hashes, signatures, build from source, and test. Then > > please vote: > > > > [ ] +1 Release this package as nifi-fds-0.3.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > >
Re: How to run nifi in a development environment
Hi Roy, I have a bash script that may be of use to you. It rebuilds the UI and copies it over to the target lib directory. It'll pick up .jsp changes as well as JS and CSS. You can find it here: https://gist.github.com/sardell/65d7c225a5c70056e3e7a54ec4027fdb Best, Shane On Wed, Dec 22, 2021 at 10:42 AM Mark Payne wrote: > My apologies, apparently the syntax that Matt provided is also valid. Just > an alternate syntax that I wasn’t aware of. > > Thanks > -Mark > > Sent from my iPhone > > > On Dec 22, 2021, at 10:17 AM, Mark Payne wrote: > > > > Just a slight clarification on the syntax. I think the maven command > is: > > > > mvn clean install -P!minify-and-compress > > > > But you may need to escape the ! So you may need to run > > > > mvn clean install -P\!minify-and-compress > > > > Thanks > > -Mark > > > > Sent from my iPhone > > > >> On Dec 22, 2021, at 10:03 AM, Matt Gilman > wrote: > >> > >> Hi Roy, > >> > >> By default, the maven build will minify and aggregate all the front-end > >> resources. There is a profile that you can (de)activate to instead > bundle > >> the resources as they are in the source. This should look something > like: > >> > >> mvn clean install -P-minify-and-compress > >> > >> When running the resulting build you should be able to inspect things > with > >> DevTools and set breakpoints in the debugger. Subsequent iterations can > be > >> made faster by only building the necessary modules needed to bundle a > new > >> front-end. Specifically, that is nifi-web-ui (don't forget to deactivate > >> minify-and-compress) and nifi-server-nar. The resulting NAR from the > target > >> directory in nifi-server-nar will need to be copied to the lib > directory of > >> your previously built assembly. > >> > >> Unfortunately, there is no way to run just the front-end in a dev server > >> decoupled from the backed. The NiFi front-end sources are in JSPs which > >> generate markup server side. > >> > >> Hope this helps. > >> > >> Matt > >> > On Tue, Dec 21, 2021 at 10:24 PM Roy Huang > wrote: > >>> > >>> Hi everyone > >>> > >>> I want to modify some css style in nifi, but I don't know how to run > it in > >>> a dev environment, can you help me with that? I'm a front-end > developer and > >>> don't know about java maven. > >>> >
