{"action":"created","issue":{"url":"https://api.github.com/repos/contentful/contentful-space-sync/issues/82","repository_url":"https://api.github.com/repos/contentful/contentful-space-sync","labels_url":"https://api.github.com/repos/contentful/contentful-space-sync/issues/82/labels{/name}","comments_url":"https://api.github.com/repos/contentful/contentful-space-sync/issues/82/comments","events_url":"https://api.github.com/repos/contentful/contentful-space-sync/issues/82/events","html_url":"https://github.com/contentful/contentful-space-sync/issues/82","id":150965114,"number":82,"title":"Question: Syncing Content Types from \"dev\" to \"prod\"","user":{"login":"rossthedevigner","id":5264084,"avatar_url":"https://avatars.githubusercontent.com/u/5264084?v=3","gravatar_id":"","url":"https://api.github.com/users/rossthedevigner","html_url":"https://github.com/rossthedevigner","followers_url":"https://api.github.com/users/rossthedevigner/followers","following_url":"https://api.github.com/users/rossthedevigner/following{/other_user}","gists_url":"https://api.github.com/users/rossthedevigner/gists{/gist_id}","starred_url":"https://api.github.com/users/rossthedevigner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rossthedevigner/subscriptions","organizations_url":"https://api.github.com/users/rossthedevigner/orgs","repos_url":"https://api.github.com/users/rossthedevigner/repos","events_url":"https://api.github.com/users/rossthedevigner/events{/privacy}","received_events_url":"https://api.github.com/users/rossthedevigner/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-25T19:56:29Z","updated_at":"2016-04-26T09:04:16Z","closed_at":"2016-04-26T09:04:16Z","body":"_Needs a question label_\r\nI have production space that I want to sync to a dev space to test/build new content types. Once I'm ready to sync my new Content Types from \"dev\" to \"production\", will running with the flag `--content-model-only` just copy the schema even though Entries are already published? \r\n\r\nIs there a scenario where Entries could be deleted by doing a `--content-model-only`?\r\n\r\nFor example; I add 3 new fields to a Content Type in dev that already has published entries in production. When I sync the content model from dev to production, I should see the 3 new (empty) fields in the already published entry in production?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/contentful/contentful-space-sync/issues/comments/214676563","html_url":"https://github.com/contentful/contentful-space-sync/issues/82#issuecomment-214676563","issue_url":"https://api.github.com/repos/contentful/contentful-space-sync/issues/82","id":214676563,"user":{"login":"trodrigues","id":38177,"avatar_url":"https://avatars.githubusercontent.com/u/38177?v=3","gravatar_id":"","url":"https://api.github.com/users/trodrigues","html_url":"https://github.com/trodrigues","followers_url":"https://api.github.com/users/trodrigues/followers","following_url":"https://api.github.com/users/trodrigues/following{/other_user}","gists_url":"https://api.github.com/users/trodrigues/gists{/gist_id}","starred_url":"https://api.github.com/users/trodrigues/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trodrigues/subscriptions","organizations_url":"https://api.github.com/users/trodrigues/orgs","repos_url":"https://api.github.com/users/trodrigues/repos","events_url":"https://api.github.com/users/trodrigues/events{/privacy}","received_events_url":"https://api.github.com/users/trodrigues/received_events","type":"User","site_admin":false},"created_at":"2016-04-26T09:04:16Z","updated_at":"2016-04-26T09:04:16Z","body":"Hi there,\r\n\r\nyes, that would possibly work and the behavior should be the one you describe.\r\n\r\nHowever, that works well if you add fields. If you delete fields, it won't work, as you can only delete fields if there are no entries associated with a content type (there is a workflow for field deletion which works, and it's explained on the README). If you change a field type, you'll also run into problems.\r\n\r\nThis tool was designed for a one way synchronization workflow, and not for a backwards and forwards workflow, and not only we do not recommend it for such a use case, we also do not intend to support these use cases as the edge cases and possibilities for errors are way too many to consider.\r\n\r\nWe are currently working on features on the API and User Interface that will allow people to make those sorts of changes possible and will eventually render this tool obsolete."}}