Keep migrations in repository?

victor.vanherpt

We are about to move to prod. Currently we just use the Spryker default .gitignore setup where migrations are not commited to the repository.
I've seen 2 articles that relate to this topic in the docs:
https://docs.spryker.com/docs/scos/dev/back-end-development/zed/persistence-layer/database-overview.html
https://docs.spryker.com/docs/cloud/dev/spryker-cloud-commerce-os/troubleshooting/troubleshooting-general-issues/missing-migration-files-on-production-environments.html

I understand it is recommended then to keep migration files for productive systems.

Do I just remove migration files from gitignore and commit them?
Are the default pipelines in aws and install recipes ready for this? I see propel:migration:delete and propel:diff in production.yml.

rshopin

Hello Victor, yes, you need to remove migration files from .gitignore and adjust installation recipe (remove propel:migration:delete command) in the project files, AWS pipelines will use installation recipe from the project repository.

rshopin

Hello Victor, yes, you need to remove migration files from .gitignore and adjust installation recipe (remove propel:migration:delete command) in the project files, AWS pipelines will use installation recipe from the project repository.

fsmeier

Heyhey, please also have a look here:

https://commercequest.space/discussion/27995/should-we-add-the-migrations-to-the-git-repository

All the best,

Florian