Deployed e804d09 with MkDocs version: 1.6.1

This commit is contained in:
2026-08-24 22:38:43 +00:00
parent 759ce1d4e8
commit c889ec725a
5 changed files with 18 additions and 3 deletions
+4
View File
@@ -3295,6 +3295,10 @@ and keeps the service's numbering unchanged. Pick an order that covers the whole
<td>Use only the CDM, or only Key Vaults, for key acquisition.</td>
</tr>
<tr>
<td><code>--cdm &lt;name&gt;</code></td>
<td>Use the named CDM device from the <code>cdm</code> config mapping for this run, ignoring the service/default mapping.</td>
</tr>
<tr>
<td><code>--skip-dl</code></td>
<td>Skip the download but still retrieve keys.</td>
</tr>
+6
View File
@@ -3921,6 +3921,7 @@ configured proxy providers), or a <code>provider:region</code> form.</p>
a content key when the vault misses. You can force one side or the other:</p>
<ul>
<li><code>--cdm-only</code>: only use the CDM (skip vaults).</li>
<li><code>--cdm &lt;name&gt;</code>: use the named CDM device for this run, ignoring the <code>cdm</code> config mapping (including its quality and Widevine/PlayReady sub-entries).</li>
<li><code>--vaults-only</code>: only use key vaults and never license through the CDM. A missing
content key fails.</li>
</ul>
@@ -4298,6 +4299,11 @@ authoritative list.</p>
<td>Content key source control.</td>
</tr>
<tr>
<td><code>--cdm &lt;name&gt;</code></td>
<td></td>
<td>Pin one CDM device, bypassing the <code>cdm</code> config mapping.</td>
</tr>
<tr>
<td><code>--export</code></td>
<td></td>
<td>Export track info and keys to JSON.</td>
+4
View File
@@ -2996,6 +2996,10 @@ control this trade-off on the <code>dl</code> command:</p>
<td><code>--cdm-only</code></td>
<td>Ignore vaults for sourcing keys and always perform a fresh license request.</td>
</tr>
<tr>
<td><code>--cdm &lt;name&gt;</code></td>
<td>Use the named CDM device for this run instead of the one the <code>cdm</code> config maps for the service.</td>
</tr>
</tbody>
</table>
<p>See <a href="../vaults/">key vaults</a> for how to configure vault backends.</p>