wolfictl adv doesn't like my directory tree / adv create complains about loading APKINDEX

[smoser]

When using wolfictl adv I end up with:

$ wolfictl adv create --fixed-version=3.13.0-r0 --type=fixed \
   --vuln=CVE-2024-6232 --package=python-3.13 \
   --distro-repo-dir=$HOME/src/wolfi/os  \
   --advisories-repo-dir=$HOME/src/advisories 
2024/09/18 13:54:38 ERRO unable to load APKINDEX for x86_64: opening "": open : no such file or directory

My source tree there is kind of funny/non-standard, i'm not even particularly sure why i chose to put os under ~/src/wolfi while putting advisories right in ~/src. Who knows why I do anything? @luhring implied that maybe that was the cause of my pain.

So, 2 things that I'd like:

1. i'd like the above to work (or be told how to i'm doing it wrong)
2. I think it'd be nice to have a wolfictl rc file maybe... that read default vaules for --distro-repo-dir and --advisories-repo-dir instead of making me type those strings.

[philroche]

I have the same with the following command

wolfictl advisory update --vuln GHSA-j2rp-gmqv-frhv --type fix-not-planned --advisories-repo-dir /home/philroche/Working/enterprise-advisories --package vault-fips-1.14 --no-prompt --distro-repo-dir /home/philroche/Working/enterprise-packages
2024/09/19 15:58:53 ERRO unable to load APKINDEX for x86_64: opening "": open : no such file or directory

[luhring]

I believe the confusing error message was cleared up in #1310 — so try out wolfictl at HEAD and let me know if that's any better. It won't fully solve your issue but wolfictl should explain its problem better.

I think it'd be nice to have a wolfictl rc file maybe... that read default vaules for --distro-repo-dir and --advisories-repo-dir instead of making me type those strings.

☝️ This is an excellent idea...