I think Nifi seems to normally take a while to finish starting. Seems like things are getting updated properly, as there would be errors in the process groups if things were not.

I think Nifi seems to normally take a while to finish starting. Seems like things are getting updated properly, as there would be errors in the process groups if things were not.

Let's see... if you run the pipeline (locally) from e70d5c2 and watch the logs for the nifi container, you should see it takes quite a while and maybe has error messages like "<something> cannot be...

Let's see... if you run the pipeline (locally) from e70d5c2 and watch the logs for the nifi container, you should see it takes quite a while and maybe has error messages like "<something> cannot be updated because it is not disabled"

Yes, I was quite pleased to see that the Nifi docker image had it included. Interesting, how can I recreate the issue you were having in order to support some basic error paths?

Yes, I was quite pleased to see that the Nifi docker image had it included.

Interesting, how can I recreate the issue you were having in order to support some basic error paths?

Yes, I read through the script there; was happy to learn about xmlstarlet. When I accidentally uploaded all the templates without the containing process groups, it took super long to upload: lots o...

Yes, I read through the script there; was happy to learn about xmlstarlet.
When I accidentally uploaded all the templates without the containing process groups, it took super long to upload: lots of retrying due to maybe conflicting processors. Not sure if that's something we can avoid here, especially since it doesn't look like this script does any retrying.

The review is mainly for any code smells in the preload.sh script. If you don't see any issues there, I can close this review.

The review is mainly for any code smells in the preload.sh script. If you don't see any issues there, I can close this review.

Pipeline seems to be working, and it did successfully upload templates.

Pipeline seems to be working, and it did successfully upload templates.

OLMIS-6481 Load process groups from templates, not registry
OLMIS-6481 Load process groups from templates, not registry
Let's not send another request just to verify the headers. We can re-use response from the previous call.

Let's not send another request just to verify the headers. We can re-use response from the previous call.

Let's not introduce another test just to verify the header. We can do the additional check in existing tests.

Let's not introduce another test just to verify the header. We can do the additional check in existing tests.

I debugged it and I can confirm that. I removed that line from those tests and I'm looking for new way to test it - either inside those methods or separately.

I debugged it and I can confirm that. I removed that line from those tests and I'm looking for new way to test it - either inside those methods or separately.

Update Changelog file, please.

Update Changelog file, please.

Since you have added profiler - let's add measurements for each important step - validate, build orderable, save,

Since you have added profiler - let's add measurements for each important step - validate, build orderable, save,

This block is repeated 3 times. Extract it to a private method.

This block is repeated 3 times. Extract it to a private method.

This likely has the potential to fail randomly. Please debug this test to verify.

This likely has the potential to fail randomly. Please debug this test to verify.

OLMIS-6485 Added Last-Modified Header to the POST and PUT /orderables endpoints
OLMIS-6485 Added Last-Modified Header to the POST and PUT /orderables endpoints
OLMIS-6476 Fixed getting paginated orderables and added sorting by product name
OLMIS-6476 Fixed getting paginated orderables and added sorting by product name
OLMIS-6442: Fixed updating inactive FTAP
OLMIS-6442: Fixed updating inactive FTAP