Add YOLO mode

[jeff-mccoy]

Provides the ability to create Zarf packages intended to work in online-only environments, i.e., without the internal Zarf airgap components typically provided by zarf init.

Related Issue

Fixes #1051
Fixes #1046
Related to #1134

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist before merging

• Tests have been added/updated as necessary (add the needs-tests label)
• Documentation has been updated as necessary (add the needs-docs label)
• An ADR has been written as necessary (add the needs-adr label) [ 1 2 3 ]

[jeff-mccoy]

Deployment of the yolo package to a clean cluster

Failure on OCI image inclusion

Failure on git repo inclusion

[Racer159]

Not going to put this in the needs changes category, but this does feel like it would warrant more user messaging on deploy (i.e. a big warning note that this will attempt to pull things from an online source). A real Zarf package could look this small, and the yolo part likely wouldn't really be understood by our deploy persona on an airgapped system. In the future this could lead to confusion for what is (at least mostly still) an airgap tool @Madeline-UX for thoughts as well

[jeff-mccoy]

Not going to put this in the needs changes category, but this does feel like it would warrant more user messaging on deploy (i.e. a big warning note that this will attempt to pull things from an online source). A real Zarf package could look this small, and the yolo part likely wouldn't really be understood by our deploy persona on an airgapped system. In the future this could lead to confusion for what is (at least mostly still) an airgap tool @Madeline-UX for thoughts as well

Yeah that's a good point. But also don't want to totally scare ppl off either with some big scary message. * thinking * 🤔

[Madeline-UX]

Right now the UI forces Zarf to run init before it is able to deploy a package. How might this change with YOLO mode? Is there a check in place where Zarf can see if it has access to the internet before deploying a package? Like a pre-flight check?

[Madeline-UX]

Not going to put this in the needs changes category, but this does feel like it would warrant more user messaging on deploy (i.e. a big warning note that this will attempt to pull things from an online source). A real Zarf package could look this small, and the yolo part likely wouldn't really be understood by our deploy persona on an airgapped system. In the future this could lead to confusion for what is (at least mostly still) an airgap tool @Madeline-UX for thoughts as well

Yeah that's a good point. But also don't want to totally scare ppl off either with some big scary message. * thinking * 🤔

What about following the pattern that has already been established when Zarf downloads a package from the internet? It asks and double confirms that this is the action the user wishes to take. Considering the security posture of default to not harming a system I could see a warrant here for a check

Another option is to add a separate field or type to the packages? Maybe this has already been done and I missed it