Import space with locale based publish export does not work

[Swissbite]

In a nutshell: The cli contentful space import ... does not reflect the enterprise feature of Locale-based publishing and hinders a successful import.

Expected behavior

The space import should be able to handle locale-based publishing.

Existing behavior

It publishes via the standard way which does not consider locale-based publishing

Detail explenation

If you export a space which has the feature Locale-based publishing enabled and not all locales are published, then the import will fail. Period.

The exported JSON has all the information to consider if a content is general published or if it is locale published. This is readable via the field sys.fieldStatus and is exported as follows:

 "fieldStatus": {
          "*": {
            "cs": "published",
            "da": "published",
            "de-CH": "published",
            "en": "published",
            "es-ES": "published",
            "fr-FR": "published",
            "hu": "published",
            "it-IT": "published",
            "ko": "published",
            "nl": "published",
            "no": "published",
            "pl": "published",
            "sv": "published",
            "th": "published",
            "vi": "published",
            "zh-TW": "published",
            "zh-CN": "published"
          }
        },

Whenever this field exists on any entry or asset, you must assume that the publishing must be locale-aware.

Further documentation

• API Documentation of locale-based publishing
• Help Center - Documentation of locale-based publishing

[whitelisab]

Hi David Daester (@Swissbite), thanks for taking the time to report this! We're aware of this feature request to add support for locale-based publishing to our import/export tooling. I have added it to the backlog for the appropriate team to review. While we can’t share an exact timeline, please know that it’s now on our radar. Thanks again for helping us improve!