You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: Allow SQS port number to be passed as environmental configuration (#660)
* Allow SQS port number to be passed as environmental configuration
* Updating SQS.service.js unit tests, to test local mode host and port
* Adding documentation about using LAMBDA_WRAPPER_OFFLINE_SQS_PORT
* Fixing linting
* Fixing unit test failures upon passing env. variables as LAMBDA_WRAPPER_OFFLINE_SQS_PORT=1234 and LAMBDA_WRAPPER_OFFLINE_SQS_HOST=custom1-host
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,6 +82,7 @@ The URL is likely to be your localhost URL and the next available port from the
82
82
Use this mode by setting `LAMBDA_WRAPPER_OFFLINE_SQS_MODE=local`. Messages will still be sent to an SQS queue, but using a locally simulated version instead of AWS. This allows you to test your service using a tool like Localstack.
83
83
84
84
By default, messages will be sent to a SQS service running on `localhost:4576`. If you need to change the hostname, you can set `process.env.LAMBDA_WRAPPER_OFFLINE_SQS_HOST`.
85
+
Also, if you need to change the port, you can set `process.env.LAMBDA_WRAPPER_OFFLINE_SQS_PORT`.
0 commit comments