feat: add dev deploy hot reload workflow #2470
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new flag to
zarf dev deploy
to enable hot reloading while developing Zarf packages.The goal of adding this flag is to help create a tight feedback loop while adding features, fixing bugs, or tweaking configurations in Zarf packages. This allows package developers to focus on their package changes and get fast feedback from them.
Zarf watches the directory provided in
zarf dev deploy
and all of its subdirectories for changes to any files. If a change to any files in the watched path(s) is detected, Zarf will automatically executezarf dev deploy
for the user to instantly deploy the latest changes to the cluster.Zarf ignores any paths defined in a
.gitignore
file if one is present in the provided directory.Checklist before merging