Ensure run_oban_trigger and scheduler are aware of the tenant in context-driven multi tenancy
#122
+7
−2
Conversation
This file contains 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
Otherwise, it wll set it to a NULL value and the job will fail in a context-driven multitenancy system.
Otherwise, it will fail in a context-driven multitenancy system.
zachdaniel
approved these changes
Feb 13, 2025
|
🚀 Thank you for your contribution! 🚀 This may actually be related to a bug I've been hunting down 😆 |
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.
No tests added. I didn't find any for context-driven multi tenancy and not sure what would be the best approach here. Probably defining pair of resources where one provides the tenant and another one uses context multi tenancy ¯_(ツ)_/¯
Contributor checklist