The service currently does not support sensitive dynamic properties. It's not a bug, but you can submit a ticket for the improvement. Look for the
Dynamic Properties: Supports Sensitive Dynamic Properties: Yes in the processor usage. Lehel ________________________________ From: Roman Wesołowski <wesolowski.ro...@gmail.com> Sent: Thursday, March 7, 2024 17:48 To: users@nifi.apache.org <users@nifi.apache.org> Subject: Re: RestLookupService question Hi, I have an additional question regarding RestLookupService. I will use this thread. When we add a header in InvokeHTTP processor we can set "Sensitive Value" Yes/No, however during adding dynamic values (tokens) in RestLookupService there is no way to make it sensitive it is grayed out. Shouldn't it be a bug as well? Or is there any idea behind it? Thanks, Roman On Thu, 7 Mar 2024 at 19:03, Lehel Boér <lehe...@hotmail.com<mailto:lehe...@hotmail.com>> wrote: The response code is only used in debug logs, there is room to improve error handling, Thanks for reporting! ________________________________ From: Gregory Foreman <gfore...@spinnerconsulting.com<mailto:gfore...@spinnerconsulting.com>> Sent: Thursday, March 7, 2024 12:53 To: users@nifi.apache.org<mailto:users@nifi.apache.org> <users@nifi.apache.org<mailto:users@nifi.apache.org>> Subject: Re: RestLookupService question I assume this is a bug. I just created NIFI-12875 (https://issues.apache.org/jira/browse/NIFI-12875) to track. On Mar 1, 2024, at 8:04 AM, Gregory Foreman <gfore...@spinnerconsulting.com<mailto:gfore...@spinnerconsulting.com>> wrote: Hello: The RestLookupService service seems to treat all http response status codes the same. Is this intentional? I would assume the LookupRecord processor would like to know if the service is returning errors so it could route accordingly. Thanks, Greg
