Update docker-compose.yml #5558
Open
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add mattermost to CELERY_WORKER_QUEUE
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does
add mattermost to CELERY_WORKER_QUEUE
Comment
#5553
We think that with the 1.16.0 release it would be a good idea to add mattermost to the CELERY_WORKER_QUEUE so that no one else has the same issues as we did when we upgraded from 1.9 to 1.16.2 to get the Mattermost integration via ChatOps.
When we upgraded our OnCall and set up the Mattermost integration, we couldn't get any messages in MM because Celery was simply ignoring the Mattermost queue.