Skip to content
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

Implement new field for store statuses in domain model #2080

Closed
OlegPhenomenon opened this issue Jul 8, 2021 · 0 comments · Fixed by #2083
Closed

Implement new field for store statuses in domain model #2080

OlegPhenomenon opened this issue Jul 8, 2021 · 0 comments · Fixed by #2083
Assignees

Comments

@OlegPhenomenon
Copy link
Contributor

Related ##1902
Related internetee/registrant_center#93

In #1902 said the following:

PR was reverted due to high amount of DB load on data migrations.
Set on hold until Sidekiq will be online in prod so we could implement the PR in question in two parts:

    Preparing the DB via async jobs
    Updating code itself.

Therefore, all the fields that were created in the #1902 case disappeared and the ticket with the preservation of domains after unlocking becomes relevant.
Since we have had changes in the structures of the project, the plan is as follows:

  1. This PR will have to go to the master FIRST! because it prepares the structure for data migration.
  2. The second step will be to create a rake task (this will be a separate PR), which will migrate data to a new database structure
  3. But the third step and the third PR will decide the question of how to maintain the necessary statuses
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants