We have added some reports as fixtures in our production site. However, after making changes to those reports in my local setup — including deleting a few of them — and pushing the updates to the production environment, the deleted reports are still present in production.
It seems the changes made to fixtures locally are not being fully reflected after deployment. I would like to ensure that any additions, deletions, or modifications to fixtures (especially reports) in the local environment are accurately synchronized with the production site.
Could anyone please guide me on how to properly update or clean up the fixtures in production to match the current state of the local setup?
I’m a bit unclear about some of the steps you’ve taken here, but I don’t believe it’s possible to define a “deleted” fixture. In other words, once a fixture has added a record to a database, I believe it has to be deleted manually. Simply removing the fixture definition won’t do it.
thanks for the support.
but i want to know is there any way other way to do it without doing it manually and using the production site.
the process what i am looking is if i delete any of the fixtures update in my local development environment. after pushing it into the production it need to be deleted in my production too
Yep, I understand what you’re saying. I don’t think there’s any way to do this with fixtures. You could probably do something with before_migrate or after_migrate hooks, but it would be a more manual process.