You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
The text was updated successfully, but these errors were encountered:
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 thenzarf 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
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.The text was updated successfully, but these errors were encountered: