pub struct ManifestModifyOptions {Show 22 fields
    pub all: Option<bool>,
    pub annotation: Option<Vec<String>>,
    pub annotations: Option<HashMap<String, String>>,
    pub arch: Option<String>,
    pub artifact_annotations: Option<HashMap<String, String>>,
    pub artifact_config: Option<String>,
    pub artifact_config_type: Option<String>,
    pub artifact_exclude_titles: Option<bool>,
    pub artifact_files: Option<Vec<String>>,
    pub artifact_layer_type: Option<String>,
    pub artifact_subject: Option<String>,
    pub artifact_type: Option<String>,
    pub features: Option<Vec<String>>,
    pub images: Option<Vec<String>>,
    pub index_annotation: Option<Vec<String>>,
    pub index_annotations: Option<HashMap<String, String>>,
    pub operation: Option<String>,
    pub os: Option<String>,
    pub os_features: Option<Vec<String>>,
    pub os_version: Option<String>,
    pub subject: Option<String>,
    pub variant: Option<String>,
}v5 only.Expand description
ManifestModifyOptions provides the model for mutating a manifest swagger 2.0 does not support oneOf for schema validation.
Operation “update” uses all fields. Operation “remove” uses fields: Operation and Images Operation “annotate” uses fields: Operation and Annotations
Fields§
§all: Option<bool>True when operating on a list to include all images
annotation: Option<Vec<String>>Annotation to add to the item in the manifest list
annotations: Option<HashMap<String, String>>Annotations to add to the item in the manifest list by a map which is preferred over Annotation
arch: Option<String>Arch overrides the architecture for the item in the manifest list
artifact_annotations: Option<HashMap<String, String>>§artifact_config: Option<String>§artifact_config_type: Option<String>§artifact_exclude_titles: Option<bool>§artifact_files: Option<Vec<String>>§artifact_layer_type: Option<String>§artifact_subject: Option<String>§artifact_type: Option<String>The following are all of the fields from ManifestAddArtifactOptions. We can’t just embed the whole structure because it embeds a ManifestAnnotateOptions, which would conflict with the one that ManifestAddOptions embeds.
features: Option<Vec<String>>Feature list for the item in the manifest list
images: Option<Vec<String>>Images is an optional list of image references to add to manifest list
index_annotation: Option<Vec<String>>IndexAnnotation is a slice of key=value annotations to add to the manifest list itself
index_annotations: Option<HashMap<String, String>>IndexAnnotations is a map of key:value annotations to add to the manifest list itself, by a map which is preferred over IndexAnnotation
operation: Option<String>§os: Option<String>OS overrides the operating system for the item in the manifest list
os_features: Option<Vec<String>>OS features for the item in the manifest list
os_version: Option<String>OSVersion overrides the operating system for the item in the manifest list
subject: Option<String>IndexSubject is a subject value to set in the manifest list itself
variant: Option<String>Variant for the item in the manifest list