Skip django migration that was used for couch-to-sql migration on fresh installs #35243
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.
On fresh install we were getting error that django.utils.connection.ConnectionDoesNotExist: The connection 'commcarehq_repeaters' doesn't exist. It makes sense, the things that migration was doing were related to repeat records couch to sql migration. And we don't need to run it on fresh installs
Product Description
Technical Summary
Feature Flag
Safety Assurance
Safety story
Should not affect any env except the ones which are newly installing commcare.
Automated test coverage
QA Plan
Rollback instructions
Labels & Review