While we initially decided against it, this otherwise causes the regexp validator to error on an empty field when it goes through a YAML -> JSON encode loop (even when marked with `+optional`). This is not actually a viable path the controller could take, as the controller trying to update the Artifact with an older version of the API package would omit the `Digest` field (because it does not exist in that version), while a newer version of the controller would always include the field (because we produce it for all kinds). While in cases where the controller would be backed by a Persistent Volume (and a partial status update is made), the validation rule would not be triggered because the field is not part of the patch. However, for sake of correctness, we still issue a patch. Signed-off-by: Hidde Beydals <hello@hidde.co> |
||
---|---|---|
.. | ||
artifact_types.go | ||
artifact_types_test.go | ||
bucket_types.go | ||
condition_types.go | ||
doc.go | ||
gitrepository_types.go | ||
groupversion_info.go | ||
helmchart_types.go | ||
helmrepository_types.go | ||
ocirepository_types.go | ||
source.go | ||
zz_generated.deepcopy.go |