Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

uds-cli zarf #1089

Open
colton-freeman opened this issue Feb 12, 2025 · 0 comments
Open

uds-cli zarf #1089

colton-freeman opened this issue Feb 12, 2025 · 0 comments

Comments

@colton-freeman
Copy link

colton-freeman commented Feb 12, 2025

Good day all,
We just switched over to uds-cli in our gitlab pipeline from Zarf and I have a question.
We were doing zarf package create and then zarf package inspect --list-images which we were then outputting that to a .txt file we later used for scanning. Since switching to uds-cli, the .txt file includes the whole yaml file. If we use --no-color it keeps it clean so we can use yq if its saved to a yaml file but just thought id let yall know if this is an actual bug or i am just missing something.

uds-cli zarf package create . --confirm -m 0 -a $arch -o . > uds-cli zarf package inspect -a $arch --list-images . | tee ./images.txt
creates a file like so

- docker-nswccd.devops.nswccd.navy.mil/project-blue/certificate-to-ship/cts-e2e-projects/cts-pipeline-e2e-test/go-vulns:0.0.3
- ghcr.io/stefanprodan/podinfo:6.4.0

�[96mkind�[0m:�[95m ZarfPackageConfig�[0m
�[95m�[0m�[96mmetadata�[0m:�[96m�[0m
�[96m  name�[0m:�[95m e2e-test�[0m
�[95m  �[0m�[96mdescription�[0m:�[95m Test project for certificate-to-ship�[0m
�[95m  �[0m�[96mversion�[0m:�[95m 0.0.3�[0m
�[95m  �[0m�[96marchitecture�[0m:�[95m amd64�[0m
�[95m  �[0m�[96maggregateChecksum�[0m:�[95m
�[95m�[0m�[96mbuild�[0m:�[96m�[0m
�[96m  terminal�[0m:�[95m JK6YVJF4QL�[0m
�[95m  �[0m�[96muser�[0m:�[95m colton�[0m
�[95m  �[0m�[96marchitecture�[0m:�[95m amd64�[0m
�[95m  �[0m�[96mtimestamp�[0m:�[95m Wed, 12 Feb 2025 07:41:33 -0700�[0m
�[95m  �[0m�[96mversion�[0m:�[95m v0.45.0�[0m
�[95m  �[0m�[96mmigrations�[0m:
  -�[95m scripts-to-actions�[0m
�[95m  �[0m-�[95m pluralize-set-variable�[0m
�[95m  �[0m�[96mlastNonBreakingVersion�[0m:�[95m v0.27.0�[0m
�[95m�[0m�[96mcomponents�[0m:
-�[96m name�[0m:�[95m go-vulns-image�[0m
�[95m  �[0m�[96mrequired�[0m:�[97m true�[0m
�[97m  �[0m�[96mimages�[0m:
  -�[95m docker-nswccd.devops.nswccd.navy.mil/project-blue/certificate-to-ship/cts-e2e-projects/cts-pipeline-e2e-test/go-vulns:0.0.3�[0m
�[95m�[0m-�[96m name�[0m:�[95m podinfo�[0m
�[95m  �[0m�[96mrequired�[0m:�[97m true�[0m
�[97m  �[0m�[96mcharts�[0m:
  -�[96m name�[0m:�[95m podinfo�[0m
�[95m    �[0m�[96mversion�[0m:�[95m 6.4.0�[0m
�[95m    �[0m�[96murl�[0m:�[95m https://github.com/stefanprodan/podinfo.git�[0m
�[95m    �[0m�[96mgitPath�[0m:�[95m charts/podinfo�[0m
�[95m    �[0m�[96mnamespace�[0m:�[95m podinfo�[0m
�[95m  �[0m�[96mimages�[0m:
  -�[95m ghcr.io/stefanprodan/podinfo:6.4.0�[0m

uds-cli zarf package inspect -a $arch --no-color <zarf-package> | tee images.yaml >
yq eval '.components[].images[]' images.yaml | tee images.txt
Works for us. We were hoping to stick with the --list-images option but its just not feasible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant