feat: Allow SQS port number to be passed as environmental configuration#660
Conversation
There was a problem hiding this comment.
Makes sense, thanks for doing this!
I wondered about allowing the port number to be included in LAMBDA_WRAPPER_OFFLINE_SQS_HOST, e.g. localhost:4566, so that we avoid another SQS config variable. However I think this would be harder to implement in a backwards compatible way, so I'm happy with your approach.
Three more small things needed here:
- Please add a test for this in
tests/unit/Service/SQS.service.test.js. There's a suite of queue URL tests in there. - Also add a note to the readme documenting use of
LAMBDA_WRAPPER_OFFLINE_SQS_PORT. This can go in the Local SQS mode section. - Finally, you'll need to prefix your PR title with
feat:so thatsemantic-releasepublishes this when merged.
|
Thanks @seb-cr for comprehensive review and comments. |
Great, thank you! Just checking your tests, they need to be slightly more robust – I can make them fail if I set Make sure at the start of each test you There are also |
…ER_OFFLINE_SQS_PORT=1234 and LAMBDA_WRAPPER_OFFLINE_SQS_HOST=custom1-host
|
Great @seb-cr, I have implemented that as well. |
seb-cr
left a comment
There was a problem hiding this comment.
All looks good. Nice work!
Thank you. |
|
🎉 This PR is included in version 1.10.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Please refer to #659 SQS Port as Env. Configuration for more details.