-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reimplement packager functions parent issue #2969
Milestone
Comments
This was referenced Sep 11, 2024
Merged
This was referenced Sep 16, 2024
Merged
Closed
Merged
This was referenced Sep 23, 2024
Merged
This was referenced Oct 15, 2024
This was referenced Oct 22, 2024
2 tasks
This was referenced Nov 4, 2024
2 tasks
This was referenced Dec 12, 2024
This was referenced Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Purpose:
As part of schema work it has been identified that
src/packager
intertwines "deploy time" and "package create time" logic. This makes it burdensome, or possibly impossible, to implement versioned schemas without passing a versioned structs throughout the codebase.We will begin by refactoring the following pieces of
src/packager
intosrc/packager2
- this will allow us to re-implement this functionality without making breaking changes to Zarf in between releases. We will then swap over the calls topackager.()
functions topackager2.()
and deprecatesrc/packager
functionality forsrc/packager2
(while renaming packager2 to packager)Decisions Made:
Opts
will be moved into their respective "primary file". All exported functions will take its "related"Opts
struct as a function argument.E.g. - InspectOpts is moved into the inspect.go file within
packager2
To Be Worked:
The text was updated successfully, but these errors were encountered: