Bryon Nevis
Bryon Nevis
Perhaps an easier workaround? ``` command: cmd: dnf config-manager --add-repo (url) warn: false args: creates: /etc/yum.repos.d/(something).repo ```
What makes this difficult is that even if you have an alpine go build container, if the go version doesn't match IDENTICALLY, the go-check will fire and try to download...
Additional input: if the release spire binaries were statically linked, or came in a MUSL version, I would just use the precompiled binaries.
Good suggestion! That will save so much time!
@azdagron Is there an ARM64 version as well?
Apologies for the random comment, but it might be worthwhile to generate some signed SLSA provenance as well, to provide traceability to the commit ID, the workflow used to build...
Also be aware that there is a DevID provisioning tool that probably needs a bit of work before it can be made production-worthy. https://github.com/HewlettPackard/devid-provisioning-tool
@ProvoK this is a dup of #1015
@ProvoK No problem. I'm in the same situation as you, checking to see whether or not the other one got merged yet. There seems to be something wrong with the...
+1 This PR seems to be stuck in automated test.