Wrap the crane command to make it easier to use with Zarf

[Racer159]

Description

This wraps the crane command so that it is easier to use more directly with Zarf

Related Issue

Fixes #1186

Type of change

• New feature (non-breaking change which adds functionality)

Checklist before merging

• Documentation has been updated as necessary (add the needs-docs label)

[jeff-mccoy]

This is a great short-term add, I was actually thinking maybe we should just add a more top-level command to interact with artifacts/assets zarf deploys. Something like zarf artifact images orzarf assets images. I think it should probably be view-only since mutation would break the nature of declarative packages. Also zarf artifact repos. Thoughts?

[Racer159]

I think that could make sense, though we would likely need to pull that info from the zarf state instead of the actual service. Doing that for git repos might get tricky across git hosts.

[jeff-mccoy]

There's a lint error in tools.go. Also, since we're adding custom logic outside of just crane, we should add a test for this. Fortunately we also need this function in the src/test/e2e/21_connect_test.go test, so might be able to just drop it in there.

[Racer159]

There's a lint error in tools.go. Also, since we're adding custom logic outside of just crane, we should add a test for this. Fortunately we also need this function in the src/test/e2e/21_connect_test.go test, so might be able to just drop it in there.

Fixed

[jeff-mccoy]

💥