You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2023. It is now read-only.
I am setting up new migration scripts to be used with environment deployments and want to include Compose.
I followed this guide to export an initial migration script for Compose: Page and Compose: SEO. But when I try and run the migration script to import the migrations into a new environment I get the following error
Error: A field can't have "relationshipType" as a validation.
I am using the Continuous Intergration tutorial to import the migrations which does not use the contentful-cli but uses the npm package contentful-migrate instead.
How can I import the file generated via the alpha-features flag in the CLI with the contentful-migrate npm package?
The text was updated successfully, but these errors were encountered:
alex-windett
changed the title
A field can't have "relationshipType" as a validation.
Importing Compose migrations: 'A field can't have "relationshipType" as a validation.'
Apr 1, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am setting up new migration scripts to be used with environment deployments and want to include Compose.
I followed this guide to export an initial migration script for Compose: Page and Compose: SEO. But when I try and run the migration script to import the migrations into a new environment I get the following error
Error: A field can't have "relationshipType" as a validation.
I am using the Continuous Intergration tutorial to import the migrations which does not use the contentful-cli but uses the npm package contentful-migrate instead.
How can I import the file generated via the
alpha-features
flag in the CLI with the contentful-migrate npm package?The text was updated successfully, but these errors were encountered: