A super efficient Amazon SQS thread based message processor for Ruby. This project is in MAINTENANCE MODE. Reach me out on Slack link on the description if you want to become a new maintainer.
Other
2.06k
stars
280
forks
source link
Small feature request: `sqs create` to read config file #696
We recently attempted to simplify our queue configuration between ActiveJob, ActionMailer, dotenv env vars, docker-compose configs, and various CI configurations.
Our end goal was to have the queue name driven by shoryuken.yml, which itself would respect env-var. The plan was to eliminate duplication of queue name defaults across the many various configuration files.
However, in our docker-compose, which needs to create the queue, it seems we still need to duplicate the queue name in the command because sqs create doesn't respect the shoryuken configuration file?
So my feature request is for that command to accept the configuration file, such that queue name can remain configured in just that single location.
We recently attempted to simplify our queue configuration between ActiveJob, ActionMailer, dotenv env vars, docker-compose configs, and various CI configurations.
Our end goal was to have the queue name driven by shoryuken.yml, which itself would respect env-var. The plan was to eliminate duplication of queue name defaults across the many various configuration files.
However, in our docker-compose, which needs to create the queue, it seems we still need to duplicate the queue name in the command because
sqs create
doesn't respect the shoryuken configuration file?So my feature request is for that command to accept the configuration file, such that queue name can remain configured in just that single location.