[WIP] bring up docker env in unit test #307
Open
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.
Current status:
I have a local amqp server running in a docker container, using the public
rabbitmq
image. I'm trying to makego test -race github.com/graphite-ng/carbon-relay-ng/input -test.v -run TestAmqpConsumeRabbit
connect to it, but I can't get it to succeed because the topic exchange doesn't exist and I can't find a way to create it withrabbitmqctl
. I think if the unit test would connect to rabbitmq, then it could declare the topic exchange, and then the amqp input should succeed to connect on the next reconnect. So I think the next step should be to make the unit test connect and declare that exchange, and then verify that this way the input can connect successfully.Side Note:
by default the
rabbitmq
image user the userguest
with passwordguest
for the virtualhost/
. Alternatively users / vhosts can be created with these env vars: