I have an issue with Features which contains a view. If I update the feature and then clear the Drupal cache, the view will revert to the configuration in the updated feature.
My understanding was that a feature would not be reverted unless it is specifically made to (e.g. manually revert the feature). Is this a wrong assumption?
Here is more information of what I have tried. On server A, I modify a view which is contained in a feature. I then update the feature so that it contains the modification to the view. I then commit the updated feature to git.
Now, I log into the other server, and pull in the changes from git (e.g. bring in the updated feature). If I go to the feature's admin page I can now see that it is overridden (so far so good).
I then clear the drupal cache (e.g. via performance page or drush cc all). If I now check the feature status, it is set to default and the view has also been modified.
Why would the feature and the view change on cache clear if I haven't specifically reverted the feature?
UPDATE: It seems the issue only occurs if the status of the feature on Server B was 'default' prior to deploying the updated feature. See following scenarios:
SCENARIO 1: Feature on Server B is in 'default' state. Updated feature from Server A is deployed to Server B. The features admin page shows on Server B now shows the feature to be "Overridden" (expected given we have deployed updated feature).
If I now clear cache, the feature's status has now changed to 'default' and examination of the relevant view shows that the changes in the updated feature have been applied.
Feature on Server B is already in 'Overridden' state, due to a local change I made to the view. The updated feature from Server A is deployed to Server B. The features admin page shows feature on Server B to be "Overridden" (expected given we made local changes to relevant view).
If I now clear cache, the feature is still shown as "Overridden" and the relevant view has not been altered.
As you can see in SCENARIO 1 the updated feature is automatically reverted on cache clear, but in SCENARIO 2 it is not.