contentful-import 10.1.2 → 10.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -235,7 +235,7 @@ contentfulImport({
235
235
 
236
236
  ### Embargoed Assets
237
237
 
238
- If a space is configured to use the [embargoed assets feature](https://www.contentful.com/help/media/embargoed-assets/), certain options will need to be set to use the export/import tooling. When exporting content ([using `contentful-export`](https://github.com/contentful/contentful-export)), the `downloadAssets` option must be set to `true`. This will download the asset files to your local machine. Then, when importing content, the `uploadAssets` option must be set to `true` and the `assetsDirectory` must be set to the directory that contains all of the exported asset folders.
238
+ If a space is configured to use the [embargoed assets feature](https://www.contentful.com/help/media/embargoed-assets/), export with `downloadAssets: true` and import with `uploadAssets: true` and `assetsDirectory` pointing to the directory generated by the export. Embargoed asset URLs cannot be processed directly during import; the importer now fails before making API calls and prints the required options when the local upload options are missing.
239
239
 
240
240
  ```javascript
241
241
  const contentfulImport = require('contentful-import')
@@ -245,7 +245,7 @@ const options = {
245
245
  spaceId: '<space_id>',
246
246
  managementToken: '<content_management_api_key>',
247
247
  uploadAssets: true,
248
- assetsDirectory: '/path/to/exported/assets.json'
248
+ assetsDirectory: '/path/to/exported-assets'
249
249
  }
250
250
 
251
251
  contentfulImport(options)