Closed VelinGeorgievGP closed 9 months ago
All right, I got it working by dropping the 'deploymentStrategy' prop from the POST payload.
curl https://api.amazonaws.com/prod/projects/d7859c4c-77a2-4b49-a54d-0b407492a31e/microFrontends/17d12cd5-d7fa-4f80-a378-0e3ed20ef8f9/versions -H "Authorization: Bearer <TOKEN>" --request POST --data '{ "version": { "url": "https://static.example.com/my-account-1.0.0.js", "metadata": { "version": "1.0.0", "integrity": "e0d123e5f317bef78bfdf5a008837200" }, "fallbackUrl": "https://alt-cdn.com/my-account-1.0.0.js" } }' -H "Content-Type: application/json"
Cheers,
Hey @lucamezzalira , guys,
I am playing with the solutions and I managed to successfully deploy it, however I struggle to register my very first version of a MFE via the Admin API.
I am following the API documentation and here are the steps I performed:
I am getting response
The specified version could not be found.
but got the following error:
Unable to create deployment when no existing version is currently receiving 100% traffic.
However the MFE entry gets created in the table dropping the activeVersions property.
What am I doing wrong?
Thanks!