Skip to content

Conversation

@rain-on
Copy link
Contributor

@rain-on rain-on commented Jan 30, 2026

Currently, the Argo Image Update step accepts a list of packages which are to be updated.

Calamari filters this list, removing any packages which are not flagged with a purpose of "DockerImageReference".

What is the risk of removing this?

Someone creates a step which has a non-docker package - this package therefore will not exist within the k8s yaml which is to be updated. So we may perform extra iterations for packages which cannot be updated (thus the step takes longer), but it will not functionally change the behaviour.

It should be noted that the step-UI prevents the inclusion of any packages which are not containers - thus 'bad' packages must be added to the step via other means (eg Terraform, via the API etc.).

@rain-on rain-on requested review from APErebus and flin-8 January 30, 2026 01:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant