-
-
Couldn't load subscription status.
- Fork 59
Move org deletion to background job with access to backend ops classes #2098
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
Conversation
Not yet working because of ModuleNotFound import error in container running main_bg.py
Loading from secrets not working, not sure what issue is yet
Likely not the right approach but I wanted to see if it the background job template's inability to load secrets was due to the crawler namespace not having access to them
Job now seems to run and exit successfully but doesn't actually delete the org yet.
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.
Looks good! Some follows up may include refactoring to more generic run_bg_job in crawlmanager and consolidating the main_bg.py / main_op.py, but that'll be for a follow-up tasks.
Follow-up to #2098 Updates I missed to nightly org deletion tests following the shift to deleting orgs in a background job. I think this should be the last thing to get nightly tests passing consistently again.
Related to #1898
This PR introduces background jobs that have full access to the backend ops classes and moves the delete org job to a background job.
We will likely want to move additional functionality into background jobs in subsequent PRs, but I'm hoping to merge this before too long so that we can use it for handling changes to storage as part of #2093
If we want to close the attached issue with this PR, I can split out the additional follow-up tasks into separate issues.