Skip to content

Updatecli automation bumps patch release images without image present #500

@viccuad

Description

@viccuad

It seems that the updatecli automation for patch releases bumps images even if they don't exist.

For example, here it bumped the audit-scanner image to v1.15.1 even if no such tag or release exists.
(yet there is the usual draft release).

This may be because updatecli.d/patch-kubewarden-kubewraden-*.yaml lack some conditions to check for the image version, e.g:

conditions:
# All the major components must have the same tag
kwctlTag:
name: Test if kwctl has the required tag
disablesourceinput: true
kind: gittag
scmid: kwctlGit
spec:
versionfilter:
kind: "semver"
pattern: "{{ requiredEnv .releaseVersion }}"
kubewardenControllerTag:
name: Test if kubewarden-controller has the required tag
disablesourceinput: true
kind: gittag
scmid: kubewardenControllerGit
spec:
versionfilter:
kind: "semver"
pattern: "{{ requiredEnv .releaseVersion }}"
policyServerTag:
name: Test if Policy Server has the required tag
disablesourceinput: true
kind: gittag
scmid: policyServerGit
spec:
versionfilter:
kind: "semver"
pattern: "{{ requiredEnv .releaseVersion }}"
auditScannerTag:
name: Test if audit-scanner has the required tag
disablesourceinput: true
kind: gittag
scmid: auditScannerGit
spec:
versionfilter:
kind: "semver"
pattern: "{{ requiredEnv .releaseVersion }}"

See:
https://github.com/kubewarden/helm-charts/actions/runs/10181224959/job/28160875951#step:9:83
Noticed here:
#499 (comment)

Acceptance criteria

  • Automations on updatecli.d/patch-kubewarden-kubewraden-*.yaml checks that all images exist prior to bumping them.

Metadata

Metadata

Assignees

No one assigned

    Type

    No fields configured for Bug.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions