Agency Update - Integration Field Support for Migration API

Updates from last week:

✅

Release Basic Integration Field Support

Basic support means that we accept integration fields on POST and PUT requests, and users can update these fields via the Migration API.

We will work on adding validation errors for these fields in a separate ticket in a few weeks.

❌

Release PUT request follow-up for handling draft documents in document list

We ran into an issue during testing where we experienced timeouts with PUT requests going to the migration release, which we are investigating before being able to release.

✅

Release change to default all Migration API POST and PUT requests to migration release

With the exception of the PUT request for draft documents as mentioned just above, all other documents created or updated the Migration API are going to the migration release by default. Users can still explicitly specify that their documents should go into the document list using an additional property in their API request.

Goals for the next week:

Open PR for HTML/Markdown to PrismicRichText conversion
In order to provide a lightweight solution for conversion, we decided to open a PR to update the existing third party conversion tool maintained by our community before spending significantly more effort to build and support such a tool internally. We have been in contact with the repo owner and will open a PR over the course of this week.
Support for permanent token (Machine2Machine) after Asset API changes

We have uncovered errors occurring when creating or updating documents with images in the Migration API in combination with a permanent token. We will now ensure full support of permanent tokens and M2M requests on the Asset API to solve this issue.