You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@YrrepNoj is this more of an *ility on the issue you are already working?
Racer159
changed the title
backwards compatibility is maintained via only using new capabilities if they exist
Document strategies around compatibility of zarf packages between Zarf verisons
Feb 28, 2023
We could also in a future ticket compare the zarf.schema.json if we include it in the zarf package. This would allow us to check for new keys more dynamically and also show descriptions of what those keys are for.
Racer159
changed the title
Document strategies around compatibility of zarf packages between Zarf verisons
Warn users about compatibility of zarf packages between Zarf verisons
Mar 1, 2023
Is your feature request related to a problem? Please describe.
Deploy users don't have a way to ensure that the zarf package they are accepting from the creator will run with their current version of the Zarf CLI.
Describe the solution you'd like
On deploy we should check the Zarf version in the build data of the Zarf package and warn the user if it does not match the current CLI version.
Describe alternatives you've considered
We could try another more complicated solution but this would be the simplest way to notify the user for now.
Additional context
Loosely tied to:
Discussion #1298
Epic #1319
The text was updated successfully, but these errors were encountered: