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.

Sign up for GitHub

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

Jump to bottom

[QA] Nettoyer les migrations après la prochaine MEP #2482

Closed
sfinx13 opened this issue Apr 19, 2024 · 2 comments
Closed

[QA] Nettoyer les migrations après la prochaine MEP #2482

sfinx13 opened this issue Apr 19, 2024 · 2 comments
Assignees
@sfinx13
Labels
v2.2.1
Projects
Backlog 🪵
Milestone
v2.2.1

Comments

@sfinx13
Copy link
Collaborator

sfinx13 commented Apr 19, 2024 •
edited
Loading

On approche les 100 migrations, pour accélérer la création de la base en locale, il faudra régénérer une nouvelle première migration à partir de la base de prod et supprimer les autres.

A voir quelle sont ceux qui doivent être gardé .

Pour éviter un impact en prod, il faudra dire via la table que la migration a déjà été joué (mettre à jour la table migration_versions via une migration)

Pousser l'étude car jouer 100 migrations à chaque fois ça fait un peu trop
@sfinx13 sfinx13 added this to 🔴 Priorité haute in Backlog 🪵 Apr 19, 2024
@sfinx13
Copy link
Collaborator Author

sfinx13 commented Apr 19, 2024

https://mattermost.incubateur.net/betagouv/pl/doyeugkxjbg35xzwqaurqcuoew

@sfinx13 sfinx13 moved this from 🔴 Priorité haute to 🟢 Dans le sprint - To do in Backlog 🪵 Apr 23, 2024
@sfinx13 sfinx13 changed the title [QA] Nettoyer les migrations [QA] Nettoyer les migrations après la prochaine MEP Apr 24, 2024
@sfinx13
Copy link
Collaborator Author

sfinx13 commented May 10, 2024 •
edited
Loading

Réflexion en stand-up pour faire des fixtures de communes
Pas besoin de toutes les communes pour bosser
Charger uniquement les villes de résidences des membres de l'équipe et gros territoires (Marseille, Nice) :-)

@sfinx13 sfinx13 self-assigned this May 10, 2024
@sfinx13 sfinx13 moved this from 🟢 Dans le sprint - To do to 💻 Sprint - Doing in Backlog 🪵 May 10, 2024
sfinx13 added a commit that referenced this issue May 10, 2024
@sfinx13
re-generate migrations #2482
11ff8c8
@sfinx13 sfinx13 mentioned this issue May 10, 2024
Merged
3 tasks
@sfinx13 sfinx13 moved this from 💻 Sprint - Doing to ⚠️ Sprint - Code revue in Backlog 🪵 May 10, 2024
sfinx13 added a commit that referenced this issue May 10, 2024
@sfinx13
remove down generate code #2482
7cb2a4e
@hmeneuvrier hmeneuvrier moved this from ⚠️ Sprint - Code revue to 🔍 Sprint - Tests in Backlog 🪵 May 13, 2024
sfinx13 added a commit that referenced this issue May 13, 2024
@sfinx13
Merge branch 'main' into develop #2482
45b546c
sfinx13 added a commit that referenced this issue May 13, 2024
@sfinx13
check if column exists #2482
d307034
@sfinx13 sfinx13 mentioned this issue May 13, 2024
Merged
2 tasks
sfinx13 added a commit that referenced this issue May 14, 2024
@sfinx13
fix constraint #2482
63544f6
@mathildepoulpux mathildepoulpux added this to the v2.2.1 milestone Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sfinx13 sfinx13

Labels
v2.2.1
Projects
Produit Histologe 🏡
Status: En prod
Backlog 🪵
🔍 Sprint - Tests
Milestone
v2.2.1
Development

No branches or pull requests
3 participants
@sfinx13 @hmeneuvrier @mathildepoulpux