Is the database migration task idempotent

[adamelmohamad]

Currently, I am running the migration task as part of an AWS fargate service container, which runs for every deployment.

Since I could not find this information in the docs, I would like to know whether this is idempotent?

That is, whether running the migration task every deployment is safe?

Will it skip migrations that have already been applied, and only apply any new ones?

[dyeam0]

Hi @adamelmohamad, we will pull in some other team members to help answer your question.

[dyeam0]

Hi @adamelmohamad, just for clarification, can you describe what you mean and what all is involved in your workflow when you say "migration task"? Are you rewriting all your tuples in the database? If you are, the API now supports functionality to ignore errors when encountering duplicate writes or missing deletes, which would make this activity much easier. SDK support is available for Go and .NET, and support in the other languages is currently in progress. See roadmap item: openfga/roadmap#79

[dyeam0]

@adamelmohamad, I got clarification from a colleague that you are most likely referring to the openfga migrate command. I will get confirmation for you whether this is idempotent.

[adamelmohamad]

Hey @dyeam0 , yes, I am referring to the openfga migrate command. Please let me know.

[cchen-motion]

I have the same question as this will be part of our CI deployment process; trying to understand best practices.