are zarf packages idempotent #4956
Unanswered
Dialgatrainer02
asked this question in
Q&A
Replies: 1 comment
-
|
In its most general form the answer is yes. Image and Repo push (to internal or external registry/git server) by design are idempotent. The caveat here is that Zarf generally expects the update workflow to these targets to happen through Zarf itself (Zarf deploy + idempotent processes). Zarf handles the same base-name for images (ie docker.io/library/nginx vs ghcr.io/nginx/nginx) in its push gracefully (separating by CRC hash based on the full name) - but two packages that contain the same mutable image tag with different layer(s) might create some issues. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
i am looking into zarf packages to simplify alot of my infrastructure around external registries and git servers. are zarf packages idempotently deployed or will it make duplicates and otherwise break things when deployed twice?
Beta Was this translation helpful? Give feedback.
All reactions