Here at Watermark Community Church we’ve been developing our toolchain around Contentful for the last several months, and felt it was time to publicize one of our most important tools. We call it contentful-schema-diff.
The purpose of this tool is to inspect two spaces and determine the differences in their content-types, and then to output a migration file compatible with the contentful-migration CLI.
In our workflow, these migration scripts are stored in the db/migrate directory. We have our own fork of contentful-migration, which only runs migration files that have not already been run in the space. The record of these migrations is stored in a special content type in the space.
All of these tools are open-source at the moment, and we will continue supporting them as long as we are on the Contentful platform for our primary CMS. Pull requests welcome!
@gburgett : Thanks for this tool. I was try to execute it but was getting error. Am i doing something wrong.
For my space, I have “master” and “Development” environment, which is my feature / staging environment. And wanted to compare diff between master & development env.
I am running the below command :
contentful-schema-diff --from “space-id” --to Development --token “contentful management token”
Getting below error :
[warning] Connection error occurred. Waiting for 1944 ms before retrying…
[warning] Connection error occurred. Waiting for 2562 ms before retrying…
[warning] Connection error occurred. Waiting for 3506 ms before retrying…
[warning] Connection error occurred. Waiting for 4691 ms before retrying…
[warning] Connection error occurred. Waiting for 6235 ms before retrying…
{ Error: getaddrinfo ENOTFOUND api.contentful.comapi.contentful.com:443
at errnoException (dns.js:50:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)
code: ‘ENOTFOUND’,
errno: ‘ENOTFOUND’,
syscall: ‘getaddrinfo’,
hostname: ‘api.contentful.com’,
host: ‘api.contentful.com’,
port: ‘443’,
config:
Hey @mainak4u.007 , looks like you’re using it correctly! It seems that the tool could not connect to the contentful API. Can you connect using a curl request? Try executing this to make sure it’s not a connection issue (Make sure you replace the $CONTENTFUL_MANAGEMENT_TOKEN and $CONTENTFUL_SPACE_ID):
After getting the diff file is TS, I am trying to migrate it and getting below error. What could be wrong here.
Command :
node_modules/.bin/ts-node node_modules/.bin/contentful-migration -s xxxxxxxxxx -a xxxxxxxxxxxxxxxx 20190529202527_generated_diff_menu.ts
Error:
? Do you want to apply the migration Yes
❯ Update Content Type menu Making requests (2/2)
→ Batch failed
Update editor interface for Content Type menu Migration unsuccessful
Batch failed
Error: {"status":"Forbidden","message":"Forbidden","details":{"reasons":["accessTokenScope","You do not have permissions to update on ContentType, please contact your administrator for more information."]},"url":"https://api.contentful.com:443/spaces/xxxxxxx/environments/master//content_types/menu"}
@gburgett thanks for the suggestion. Yes, my issue was - Point 1. Some issue was happening with my content management token … when i try to generate from CLI contentful login command and then pasting the token, it was not working… later i tried generating one in contentful site, created .contentfulrc.json and pasted that token , it started working
One question, do this tool shows the difference of content as well.
@gburgett I am using contentful schema diff tool but getting the below error when i am trying to compare 2 environments
npx contentful-schema-diff --from 37lvxp3wt7oq/dev-2 --to 37lvxp3wt7oq/dev-3 --token na-ttkiP7bcKoCxODCFHSHS7XDguHPUEOsxrYy-hAKA --one-file
Error: Diff produced a “~” with a non-diff obj:
[“~”,{“defaultValue__added”:{“en-US”:“top”}}]
at C:\Users\viswa.telagamsetty\AppData\Roaming\npm\node_modules\contentful-schema-diff\dist\modify.js:151:43
at Array.forEach ()
at Object. (C:\Users\viswa.telagamsetty\AppData\Roaming\npm\node_modules\contentful-schema-diff\dist\modify.js:125:32)
at fulfilled (C:\Users\viswa.telagamsetty\AppData\Roaming\npm\node_modules\contentful-schema-diff\dist\modify.js:5:58)
because of this error file is not getting the closing bracket and there is one more issue if i am trying to close the curly brace and try to run the migration script on the file it was showing because of default_value your file cannot be migrated. If i have removed that than it is working.
We are trying to do the jenkins CI/CD by using this package.
Unfortunately the tool is not smart enough to handle 100% of all possible migrations. It works great for about 95% of cases, and then you have to manually edit the migrations. For this reason I advise that you do not run the tool in an unattended automatic process inside your CI/CD.
Our team uses this package to create migrations locally, and then we check them in to our source code and include the final migrations as part of a pull request.
Of course you are always welcome to fork and improve the tool! I would welcome any pull requests at
Making requests (2/2)
Migration unsuccessful