View and Edit Docs via Migration Release and fix for missing LinktoMedia ids on APIv2

Updates from last week:

✅

Release view and edit of documents in migration release

Users that create documents via the Migration API can now view and edit them via the Migration release when using PageBuilder. They can also see the migration release on the version panel, making it easier for marketers to spot any other potential updates to a page they are editing.

Legacy editor is not currently enabled, so users will have to be on PageBuilder in order to use this new feature.

We are still assessing if the effort of implementation in Legacy editor makes sense, given how close to feature parity we currently are in PageBuilder.

✅

Develop a solution for Asset IDs not being exposed in API v2

Ids were not being exposed properly for non-image files via the read-only Document API, such as PDFs and videos. This led to issues on bulk updates of documents via the Migration API. We fixed the issue and released it late last week, so that users can now update without getting errors and having to manually search for the respective id they were missing.

Goals for the next week:

More detailed monitoring in Grafana for Migration API

In an effort to recognize and improve the frequency of errors for repositories, we are implementing more detailed monitoring of API calls and errors via Grafana. This will help activate Migration API users and get them to first success more quickly, one of our focuses of Q2.

Start outlining strategy for bulk action performance

This is currently blocking us from having a migration release size larger than 1k. The team will outline the strategy now, so we do not lose sight of the investigation already done on this topic and have a concrete plan in place.

However, we will likely have some time before implementation. This is because this topic requires input from Seb and Arnaud, and we do not want to interrupt the crucial work on db migration being done in the platform team for now.