Skip to content

Conversation

amfern
Copy link

@amfern amfern commented Nov 6, 2018

No description provided.

@josegonzalez
Copy link
Contributor

Why this change?

@amfern
Copy link
Author

amfern commented Nov 18, 2018

I wanted to have different mixes of sinks for the same command, for example writing job changes to http and to mongo at the same time

@josegonzalez
Copy link
Contributor

@jippi I'll leave merging/releasing to you :)

@amfern
Copy link
Author

amfern commented Nov 19, 2018

I do realize its a breaking change, but it think its a needed one

@jippi
Copy link
Contributor

jippi commented Nov 19, 2018

@amfern can you make it so it defaults to the current value, but you can override it by LOCK_NAME env variable?

@amfern
Copy link
Author

amfern commented Nov 19, 2018

yes

@ilyaiqoqo ilyaiqoqo force-pushed the use-sink-type-as-lock-key-too branch from 860cc6f to 1b26c2c Compare November 19, 2018 09:42
@amfern
Copy link
Author

amfern commented Nov 19, 2018

@jippi update the PR

@jippi
Copy link
Contributor

jippi commented May 7, 2019

Hi, this now has a merge conflict :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants