Calling Developers!
We are reenergizing our code contribution process! Learn More

Keep migrations in repository?

Options
victor.vanherpt
victor.vanherpt Spryker Solution Partner Posts: 41 🪐 - Explorer

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.

Tagged:

Best Answer

  • rshopin
    rshopin Senior Solution Architect Sprykee Posts: 32 🧑🏻‍🚀 - Cadet
    Answer ✓
    Options

    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.

Answers