<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/303120fe8c7347b4a4109613b214542c&quot; frameborder=&quot;0&quot; width=&quot;1662&quot; height=&quot;1246&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1246</height><width>1662</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1246</thumbnail_height><thumbnail_width>1662</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/303120fe8c7347b4a4109613b214542c-b15d5e6f149f5756.gif</thumbnail_url><duration>70.945</duration><title>Upsert_content without content_type</title><description>This Loom explains a test failure related to a missing content type and the steps needed to address it. The author notes they added the content type to the PR and test case, but when removed the test reported the test case was absent. They decided to add the content type in OpsCert concept content and also ensure it is included in the document inline in both places, noting they previously missed one case. They plan to rerun the test on the branch where the migration will be applied.</description></oembed>