pvimg: Add comment why cck and not cck-available is required

Add a comment to the code to explain why cck and not cck-available is
required.

Reviewed-by: Steffen Eiden <seiden@linux.ibm.com>
Signed-off-by: Marc Hartmayer <marc@linux.ibm.com>
Signed-off-by: Jan Höppner <hoeppner@linux.ibm.com>
This commit is contained in:
Marc Hartmayer
2026-06-18 10:28:04 +02:00
committed by Jan Höppner
parent 6c67f05ca7
commit 367ca6e16b

View File

@@ -154,6 +154,9 @@ pub struct CreateBootImageLegacyFlags {
/// Add-secret requests must provide an extension secret that matches the
/// CCK-derived extension secret. This option requires the '--cck'
/// option.
// Note: We intentionally require 'cck' (not 'cck-available') because
// enable-cck-extension-secret cannot be used together with
// --enable-cck-update.
#[arg(long, action = clap::ArgAction::SetTrue, requires="cck", group="header-flags")]
pub enable_cck_extension_secret: Option<bool>,