Allow overriding a zarf package's source at deploy time

[blancharda]

Context

When developing a bundle using remote packages, the cycle time and process for consuming upstream changes can be cumbersome. If a bundle consumes a tagged and published Zarf artifact, absent other workarounds, the developer must publish a new artifact before being able to test the change to the bundle. That can include significant time sinks (code review, automated tests, PR process etc) in the individual package repo and significantly slow down the dev cycle for a bundle.

Feature Request

Allow the user to override a package repository source at deploy time to leverage a local build path for the given package.

Example

Given:

kind: UDSBundle
metadata:
  name: software-factory-nutanix
  description: A UDS bundle for deploying a software factory to an RKE2 cluster
  version: 0.0.1
  architecture: amd64

zarf-packages:
  # Zarf init
  - name: init
    repository: ghcr.io/defenseunicorns/packages/init
    ref: v0.29.1
    optional-components:
      - git-server

  # Gitlab
  - name: gitlab-redis
    repository: ghcr.io/defenseunicorns/uds-capability/gitlab/dev-dependency/gitlab-redis
    ref: 0.0.2

Allow the user to replace a bundled package at deploy time with something like --local-package-redirect gitlab-redis=<path_to_local_zarf_package_dir>

In this way, a user could develop and test changes to component packages in the bundle and ensure they are functional prior to working through the change process in the other repo.

[UncleGedd]

This sounds good to me! I might suggest a different flag but I think the premise is strong. Local bundles were def meant to be used for dev purposes, so supporting this flag to make that easier sounds like a nice feature. Curious if @jeff-mccoy or @mikevanhemert have thoughts as well?

[blancharda]

@UncleGedd -- is this resolved by the new dev mode?

[UncleGedd]

It's a comin'! #638

Expected to be merged by the next release

[UncleGedd]

@blancharda does dev deploy resolve this issue for you?

[blancharda]

I'm not positive, but I don't think so..

As I understand it, dev deploy can be used to quickly iterate with local packages, but I'm not sure it let's you specify a local source for a remote package included in the bundle.

If I'm mistaken and there's a way to do this today, I'd love to see it!