Import does not publish the content about contentful-cli HOT 11 CLOSED

There's the following piece of code in the library. It filters all the entities and decides if they should be published or not:

const entityIdsToPublish = sourceEntities
    .filter(({ original }) => original.sys.publishedVersion)
    .map(({ original }) => original.sys.id)

Only after finding this, it get clear that if an entity has to be published, it should contain sys.publishedVersion field

from contentful-cli.

I am sorry, does anyone have a solution for this?

Example:

{
    "entries": [
        {
            "sys": {
                "publishedVersion": 1,
                "space": {
                    "sys": {
                        "type": "Link",
                        "linkType": "Space",
                        "id": "4zg16q5vss6b"
                    }
                },
                "environment": {
                    "sys": {
                        "id": "staging",
                        "type": "Link",
                        "linkType": "Environment"
                    }
                },
                "contentType": {
                    "sys": {
                        "type": "Link",
                        "linkType": "ContentType",
                        "id": "model"
                    }
                }
            },
            "fields": {
                "tesyId": {
                    "it-IT": "0049130"
                },
                "synced": {
                    "it-IT": false
                }
            }
        }
    ]
}

from contentful-cli.

Hi @scaccogatto

Is there already content in the space you're importing into?

You can read more about the publishing strategy of the import tool when there is existing content here: https://github.com/contentful/contentful-import#bulb-importing-to-a-space-with-existing-content

The sys properties are ignored, so sending published data in the sys payload will not force a publish.

from contentful-cli.

I solved by using the cli manually, so I don't need this feature anymore.
If it helps, yes, there is already content in the space.

from contentful-cli.

glad you were able to solve it.

The existing content in the space, and its status (published, draft, etc) was likely having an effect on whether the import tool published the content.

from contentful-cli.

I am sorry, this was 10 day ago. I forgot almost everything. I did NOT solve this problem with the cli.
I cannot make it publish after importing.
The content imports correctly but it tets itself to draft.
There is more content in the space but not the one that I am importing. I am stuck.

from contentful-cli.

@scaccogatto could you open a new issue and we can continue debugging there?

from contentful-cli.

Hi, @scaccogatto did you get any feedback on this? I'm facing the same issue. Imported assets are set as drafts.

Thanks in advance.

from contentful-cli.

Hi, @scaccogatto did you get any feedback on this? I'm facing the same issue. Imported assets are set as drafts.

Thanks in advance.

I had to rewrite my logic with the contentful js sdk.
Never had the chance to write the whole thing as I wanted because of this bug.

from contentful-cli.

figured it out

from contentful-cli.

@KaterynaBoiko is right, and to clarify: for each entry to contain the sys.publishedVersion, the --include-drafts option (when exporting the content in the first place) should be set to true. Then when the content is imported, it will hold the correct draft/published status.

from contentful-cli.