Hi David,
Thanks for your answer.
I had considered Hashicorp Vault for exactly the reason you state, but at this
point it's too much overhead and not all of our NiFi clusters are at 1.14+ yet.
You make a good point about the likelihood of changes "under the hood" causing
problems. I'll focus
+1
- Verified checksums, signature, and commit hash
- LICENSE and NOTICE look good
- Verified npm run clean:install passes
- Verified the demo app works as expected
Thanks!
- Margot
> On Jan 25, 2022, at 2:39 PM, Joe Witt wrote:
>
> +1 binding.
>
> Verified hashes, signature, L&N, commit.
+1 (non-binding)
Verified signature
Verified hashes
Checked LICENSE and NOTICE
Built with node 16.13.2
Ran demo app, verified a handful of the resolved issues. Everything looks
great!
Thanks for RM'ing Scott!
---
Rob Fellows
+1 binding.
Verified hashes, signature, L&N, commit. Ran the build and demo app.
Checks out fine.
Please note we should not publish sha1 hashes anymore. Just delete
that from the artifacts.
Thanks for RM efforts!
Joe
On Tue, Jan 25, 2022 at 2:41 PM Scott Aslan wrote:
>
> Hello,
>
> I am ple
Hello Apache NiFi community,
Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.
# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS
# Import keys file:
gpg --import KEYS
# Pull down nifi-fds-0.3.0 so
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
Cancel this RC due to LICENSE, NOTICE, and README need some changes.
On Tue, Jan 25, 2022 at 12:06 PM Joe Witt wrote:
> We also need to update the NOTICE file
>
> Apache NiFi Flow Design System
> Copyright 2014-2018 The Apache Software Foundation
>
> This product includes software developed at
>
We also need to update the NOTICE file
Apache NiFi Flow Design System
Copyright 2014-2018 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
On Tue, Jan 25, 2022 at 10:02 AM Joe Witt wrote:
>
> -1 (binding)
>
> Thi
-1 (binding)
This vote thread appears to be the helper thread. We need to be using
the vote template found in step 5
https://nifi.apache.org/fds-release-guide.html
Need to ensure the JIRA with a set of changes is linked, the commit
IDs are there. Let's fix the links that Rob found. And let's m
Hi Isha,
Thanks for contacting the developers list and describing what you are
attempting to accomplish.
Although there are several Java interfaces and implementation classes that
could be leveraged to implement a custom approach to property encryption,
that may not be the most reliable method.
Marshall,
You've been assigned contributor in Apache NiFi JIRA.
Thanks
Matt
On Fri, Jan 21, 2022 at 2:21 PM Marshall Newberry
wrote:
> Requesting Jira contributor access for user dmnewber.
>
+1 (non-binding)
With the corrected download links I was able to download, verify signatures
and hashes, build, and exercise FDS components.
* Built with node 16.13.2 / npm 8.1.2
Thanks for RM'ing Scott!
On Mon, Jan 24, 2022 at 7:23 PM Scott Aslan wrote:
> Hello Apache NiFi community,
>
>
> P
Thanks Rob! Copy/Paste error. I’ll be sure to update the RC template at
https://nifi.apache.org/fds-release-guide.html.
On Tue, Jan 25, 2022 at 8:08 AM Robert Fellows
wrote:
> The links for the downloads are incorrect. It should read:
>
> # Pull down nifi-fds-0.3.0 source release artifacts for r
The links for the downloads are incorrect. It should read:
# Pull down nifi-fds-0.3.0 source release artifacts for review:
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0/nifi-fds-0.3.0-source-release.zip
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds
Hi all,
I hope this question is appropriate for the developers list, if not, I’ll move
it to users.
I have an Ansible role for NiFi that includes generating the NiFi properties
files from templates and variables set per cluster/host as well as updating
keystore etc.
This works very well, excep
15 matches
Mail list logo