CI should test for a zarf package upgrade & init package upgrade #679
Comments
jeff-mccoy
pushed a commit
that referenced
this issue
Dec 5, 2022
## Description Introduces a PR check to see if Zarf is upgradeable version over version ## Related Issue Fixes #679 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) ## Checklist before merging - [X] Tests have been added/updated as necessary (add the `needs-tests` label)
Repository owner
moved this from Backlog
to Done
in Zarf Project Board
Dec 5, 2022
Noxsios
pushed a commit
that referenced
this issue
Mar 8, 2023
## Description Introduces a PR check to see if Zarf is upgradeable version over version ## Related Issue Fixes #679 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) ## Checklist before merging - [X] Tests have been added/updated as necessary (add the `needs-tests` label)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we only test for
zarf initandzarf package deploythat do not present upgrades across the package. Zarf should be able to demonstrate an upgrade as well as clean install. We do not need to validate component upgrades otherwise as we already do this ootb with the zarf-registry.Outcomes:
zarf initworkflow that initializes a clean cluster with built-in K3s as well as K3d/KinDzarf initworkflow that first performs a clean install with the latest release version of zarf and then performs a secondzarf initwith the current version to verify the upgrade pathThe text was updated successfully, but these errors were encountered: