Thank you for your contribution! 🙏

Please understand that we will do our best to review your PR and give you feedback as soon as possible, but please bear with us if it takes a little longer as expected.

While you are waiting, make sure to:

• Add an entry in our changelog in alphabetical order and link related issue
• Update the documentation, if needed
• Add unit & e2e tests for your changes
• GitHub checks are passing
• Is the DCO check failing? Here is how you can fix DCO issues

Once the initial tests are successful, a KEDA member will ensure that the e2e tests are run. Once the e2e tests have been successfully completed, the PR may be merged at a later date. Please be patient.

Learn more about our contribution guide.

/run-e2e ibm
Update: You can check the progress here

I'm curious about why this is needed. Does it mix the requests?

Not that I know of, but the original code reuses a single http.Request instance across multiple queue queries by only replacing the req.Body in each loop iteration. Creating a new request for each iteration ensures proper isolation and prevents potential issues with request state management.