Allow azurestoragequeues transport to be used with Azurite emulator in docker-compose #1611
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When integration testing the
azurestoragequeues
transport locally using Azurite within a docker-compose stack, the queue url becomeshttp://<service>:10001/devstoreaccount1
rather thanhttp://localhost:10001/devstoreaccount1
where<service>
is the name of the azurite service in docker-compose. As described in this issue on the Azure python SDK, this results in a failure to connect to the queue service. This PR applies the suggested workaround in this comment to enable the kombu transport to work with Azurite in local docker-compose stacks for integration testing.This PR should close #1168