search

ordercloud-api / ordercloud-seed

CLI and library to Import and export serialized representations of full marketplaces
MIT License
9 stars 9 forks source link

Seeding "Simple - B2C" configuration fails #4

Closed crhistianramirez closed 2 years ago

crhistianramirez commented 3 years ago

Seems to fail because it's expecting a supplier to exist which is odd since this is a B2C configuration. I ran this twice to rule out the chance that it was a transient network error.

The following is the output of running the command.

SUCCESS - Found "https://raw.githubusercontent.com/ordercloud-api/ordercloud-seed/main/seeds/Simple-B2C.yml". ✔️ SUCCESS - Valid yaml in "https://raw.githubusercontent.com/ordercloud-api/ordercloud-seed/main/seeds/Simple-B2C.yml" ✔️ SUCCESS - Data source ready for seeding! ✔️ SUCCESS - Created new Organization with Name "Simple-B2C" and ID "pwsJ5UDjumVlUgcp". � PROGRESS - Uploaded 0 Incrementors. � PROGRESS - Uploaded 0 XpIndices. � PROGRESS - Uploaded 3 SecurityProfiles. � PROGRESS - Uploaded 1 AdminUsers. � PROGRESS - Uploaded 0 AdminUserGroups. � PROGRESS - Uploaded 0 AdminAddresses. � PROGRESS - Uploaded 0 MessageSenders. � PROGRESS - Uploaded 1 IntegrationEvents.

Unexpected error from OrderCloud. This is likely a seeding tool bug. Please create a github issue with your seed file included! https://github.com/ordercloud-api/ordercloud-seed/issues.

Request method: POST Request url: https://sandboxapi.ordercloud.io/v1/catalogs Request data: {"ID":"solitary-storefront","OwnerID":"simple-B2C-starter","Name":"Solitary Storefront ","Description":"Default catalog for Solitary Storefront ","Active":true,"CategoryCount":15,"xp":null}

Response status: 404 Response data: { ErrorCode: 'NotFound', Message: 'Object not found.', Data: { ObjectType: 'Supplier', ObjectID: 'simple-B2C-starter' } } (node:52768) UnhandledPromiseRejectionWarning: OrderCloudError at new OrderCloudError (C:\Users\CrhistianR\AppData\Roaming\npm-cache_npx\52768\node_modules\@ordercloud\seeding\node_modules\ordercloud-javascript-sdk\dist\index.js:126:24) at C:\Users\CrhistianR\AppData\Roaming\npm-cache_npx\52768\node_modules\@ordercloud\seeding\node_modules\ordercloud-javascript-sdk\dist\index.js:7636:43 at processTicksAndRejections (internal/process/task_queues.js:97:5) (node:52768) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (node:52768) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

oliverheywood451 commented 3 years ago

I figured out this was caused by the platform release on 6/21. It doesn't appear since that was rolled back. I'll leave the issue open though for when that release is attempted again.