fix: [BB-6077] allow setting celery backend in yml - #467
Merged
Conversation
navinkarkera
changed the title
kaustavb12
approved these changes
May 22, 2022
kaustavb12
left a comment
kaustavb12
left a comment
Member
There was a problem hiding this comment.
👍
Looks good to me
- I tested this: Tested it in the PR sandbox
- I read through the code
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry pick of: openedx#30244
Description
Currently, the
CELERY_RESULT_BACKENDis hard coded to usedjango-cache.This PR allows to setup
CELERY_RESULT_BACKENDviaENV_TOKENS.To use django ORM as celery backend, one can set
CELERY_RESULT_BACKENDtodjango-dbas described in docs.