-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Per queue config + ENV config #10
base: version-1.0
Are you sure you want to change the base?
Conversation
:shutdown_timeout, :client, :logger, | ||
:async_queue_error_handler, :message_group_id | ||
GLOBAL_ENV_CONFIGS = %i[ | ||
threads backpressure |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit - single line or multiline all
|
||
# Don't use this method directly: Configuration is a singleton class, use | ||
# +Aws::ActiveJob::SQS.config+ to access the singleton config. | ||
# | ||
# This class provides a Configuration object for AWS ActiveJob | ||
# by pulling configuration options from Runtime, the ENV, a YAML file, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think ENV should take precedence over YAML, so that you can set ENV for the config file location. See how this was done in the sessionstore gem recently.
@@ -87,12 +111,24 @@ class Configuration | |||
|
|||
def initialize(options = {}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This style/approach reads a lot cleaner IMO
Issue #, if available:
#4 #3
Description of changes:
Adds configuration per queue and allows configuration through the environment for both global and queue specific values.
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.