Config change deltas now compare against and create a conflicted fields attribute on the service if the local value has changed from the remote value
Fixed tests and added new tests for the new conflicted fields work
Add change count to commit summary.
Merge pull request #574 from huwshimi/changelog-count

Add change count to commit summary

Fixes bug #1371018: on the commit summary the number of changes is now displayed.
Set mv true by default in app index and removed flag from index otherwise.
Merge pull request #575 from jaycee/kill-mv-flag-0

Set MV true by default so flag isn't needed.

* MV is set true by default--this doesn't actually remove the flag code, just
  ensures that in all cases the MV path is selected. This is to make cleaning
  the mv code cleaner and allow submitting cleanup possible as it's finished,
  rather than in one big block.
* As drive by, MV conditional elements in the index.html file have been removed.
Updates test to make it more detailed
Merge pull request #573 from hatched/config-default

Create a conflicted fields attribute in services models

In order to properly show conflicted fields in an ecs'd world we need to track which fields are actually in conflict with the environment and the ecs records at all times. This change breaks the databinding conflict engine because we no longer update the services config values if the user has changed them. Future branches will re-enable the conflict UI using this conflicted fields attribute.