Closed moleksyuk closed 6 years ago
Hi,
Thank you for submitting this issue. I appreciate it the detailed report.
I'll take a look shortly.
Thanks, Ronald
@roribio Hi,
According to the elasticmq supervisord settings: -Dconfig.file=/opt/config/elasticmq.conf
I can confirm this issue. The problem is, that the config file for sqs-insight is loaded from a different location than the /opt/config folder. This is stated in the logs Loading config file from "/opt/sqs-insight/lib/../config/config_local.json"
I created a pull request that fixes this issue (however it is just a quickfix solution and might be handled much smoother by copying the file to the correct location in the first place)
Thank you for your contribution @Phylu, I appreciate it 💥 💯 !
I'll try to find some time to improve how configs are loaded soon.
Hi @roribio,
Yesterday you closed #11 but unfortunately it doesn't work for me.
Steps to reproduce:
node-address { protocol = http host = "*" port = 9324 context-path = "" }
rest-sqs { enabled = true bind-port = 9324 bind-hostname = "0.0.0.0" // Possible values: relaxed, strict sqs-limits = strict }
queues { default { defaultVisibilityTimeout = 10 seconds delay = 5 seconds receiveMessageWait = 0 seconds }, test { defaultVisibilityTimeout = 10 seconds delay = 5 seconds receiveMessageWait = 0 seconds } }
docker run -p 9324:9324 -p 9325:9325 -v /Users/moleksyuk/tmp/alpine-sqs/opt:/opt/custom roribio16/alpine-sqs:latest
In logs I see it says only one queue is available:
And SQS-Insight also shows only default queue.
Is it bug or my config is wrong?