Re: [DISCUSS] rename master branch, look through code for other related issues

After a quick review, in nifi, I wasn't able to find references to the properties Joe mentioned, but I did use crude recursive greps to look. A majority of the blacklist references were in wali in method names and log messages. Picking a more useful term in wali would probably make sense. I'll make

Re: [nifi] branch main created (now 239a2e8)

So, should we rebase our outstanding PR’s? Should all outstanding PR’s get a note? On July 6, 2020 at 17:57:25, Andy LoPresto (alopre...@apache.org) wrote: Apache Infra completed the change. Everything looks ok from my end but as I made the initial change, can someone else verify that their loc

Re: [DISCUSS] rename master branch, look through code for other related issues

Mike, I did a quick check to see if anyone had done a jira or pr for #2, so I'll take a stab at doing that today. Tony On Thu, Jul 2, 2020 at 10:27 PM Mike Thomsen wrote: > Didn't see any commits or PRs for any of these yet. Do we want to consider > these blockers for 1.12 or hold off until a p

Re: [nifi] branch main created (now 239a2e8)

Apache Infra completed the change. Everything looks ok from my end but as I made the initial change, can someone else verify that their local repo is good to go? Once that’s done, I’ll update the committer guide and GitHub PR template with the new language, and check the CI/CD for GitHub Actions

Re: Informing users fields are deprecated

That'll have to do for now. We have a PR from someone that was aiming to refactor a little bit of the Mongo security, and it reminded me that we need to start down the path of deprecating those old fields in favor of moving to the client service configuring all of the processors to better align wit

Re: Proposal: add nifi-elasticsearch-5-nar to a profile build in nifi-assembly

I'm supportive of es5 bits moving into a profile and not being included by default. Space savings for the older things is good where usage isn't known to be huge. Thanks On Wed, Jul 1, 2020 at 3:24 PM Mike Thomsen wrote: > Matt, > > I don't think it's an either-or, but we should work on making

Re: [nifi] branch main created (now 239a2e8)

Looking into this we might be fine. We use the github 'default branch' which I think you'll get changed by the INFRA ticket. We then might want to look at https://github.com/ethomson/retarget_prs Thanks On Mon, Jul 6, 2020 at 9:21 AM Joe Witt wrote: > Andy > > I *think* we need to change the

Re: [nifi] branch main created (now 239a2e8)

Andy I *think* we need to change the github actions config a little bit as well. It defaults to master I believe and we can specify an alternative branch of 'main'. Maybe we just keep an eye on it and see if there is a material difference. One example is the 'build passing' indicator comes from

Re: [nifi] branch main created (now 239a2e8)

It appears that we don’t have the ability to switch the default branch ourselves; I’ve filed https://issues.apache.org/jira/browse/INFRA-20487 requesting Apache Infra takes care of that. Until that time, committers _should_ merge the code to ma

Re: Informing users fields are deprecated

There are jira issues out there like : https://issues.apache.org/jira/browse/NIFI-6043 On July 6, 2020 at 09:28:35, Bryan Bende (bbe...@gmail.com) wrote: Do you mean a property on a processor/controller service? If so, there is no visual indicator that I'm aware of, it would require adding so

Re: Question about Using NiFi API of Secured Instance

Hello, Yes this is possible. I don't know C#, but in Java code you need to create an SSLContext where you specify the keystore and truststore, and then make an https connection that is configured with that SSLContext. Here is some sample code that shows creating an SSLContext in Java: https://gi

Re: Informing users fields are deprecated

Do you mean a property on a processor/controller service? If so, there is no visual indicator that I'm aware of, it would require adding something to the PropertyDescriptor API like ".deprecated()". Right now you can probably just make a statement in the description explaining that it is deprecat

Informing users fields are deprecated

Do we have any visual cues that inform users that a field has been marked @Deprecated? Thanks, Mike

Re: [discuss] 1.12.0 or 1.11.5...

Regarding the NiFi Registry 0.7.0 release - if we can have the OIDC support in it, that would be great. I know Nathan is working on it (based on the JIRA) not sure if this is something close to being ready. Le sam. 4 juil. 2020 à 21:15, Mike Thomsen a écrit : > FYI, if we add in https://github.c