Features workflow issue with deleting a field Suppose I have a content type Person with fields: Name, Age, Email

This content type is controlled by a Feature called test so I can source control it and push it to the live site.

My workflow goes like this:


I add a new field on Person called Phone
locally I do: drush fu test -y
I edit the test.info to increase the version number
I commit the changes to my repository
I push the feature to the live site (copy the feature files)
on the live site I do: drush fr test -y
on the live site I do: drush cc all


Then the new field appears on the live site's Person.

If on the first step I remove a field of Person the field will not be deleted from the live site. How do I solve this? I don't want to have to manually delete it from the UI on the live site.
Is this workflow correct?
The correct way to remove Features-created content is via hook_update_N (which should be implemented in the file your_module.install).



The main idea with Features is to manage configuration with code. Using hook_update_N is consistent with that, since the field deletion is in code (which can be managed with version control) — whereas the equivalent command drush field-delete field is not being called from managed code; it's a separate command-line step you need to perform (and to remember to perform).