Export creates improper json
Expected Behavior
I'm exporting an environment from a space and should be getting proper json file, but I'm not.
Actual Behavior
Here's the beginning of the (a lot longer) json I get, but the errors are obvious from the beginning. These continue throughout the whole file.
"contentTypes":,
[
{"sys":
{"space":
{"sys":
{"type":
"Link" "linkType":,
"Space" "id":,
"****"
}
Cli output is:
The export took less than a minute (4s) Stored space data to json file at: ***** The following 0 errors and 6 warnings occurred: 15:58:08 - Rate limit error occurred. Waiting for 1519 ms before retrying... 15:58:08 - Rate limit error occurred. Waiting for 1566 ms before retrying... 15:58:08 - Rate limit error occurred. Waiting for 1528 ms before retrying... 15:58:08 - Rate limit error occurred. Waiting for 1575 ms before retrying... 15:58:08 - Rate limit error occurred. Waiting for 1690 ms before retrying... 15:58:08 - Rate limit error occurred. Waiting for 1599 ms before retrying... The export was successful. Done
Steps to Reproduce
I'm running the following command: contentful space export --space-id ********* --environment-id master --management-token ******* --content-file master_export20240925.json
Environment
I've tested with node 18.13.0 and 20.9.0. I'm running it in windows 11 command line. contentful-cli version is 3.3.11
same issue here!
Same issue here with version 3.3.11 running on both MacOS Sonoma and Debian bookworm
Hello! Same issue here on Mac Sonoma. I tried with several previous versions of the CLI but same result.
Duplicate of https://github.com/contentful/contentful-cli/issues/2761
A recent contentful-cli release of v3.3.12 fixed this issue for us
(We were experiencing this problem when running the export inside a Debian Docker Container)
A recent contentful-cli release of v3.3.12 fixed this issue for us
(We were experiencing this problem when running the
exportinside a Debian Docker Container)
Thanks, yes, working for me as well with 3.3.12.
I'll go ahead and close this issue now that the problem has been resolved (as of 3.3.12). Thanks all for reporting and confirming here when the fix was released.