It may be worth including in the documentation that if you are in a segregated/restricted network that requires a Proxy to access the internet, you may have issues with dispatch accessing github.com unless the proxy is configured.
In my instance I observed that I was not receiving any of the SEV-3.0 Report Issues created when sev-certify had run successfully.
There are no proxy configuration options in dispatch, however it is simple to work around it on Linux. Either have your HTTP_PROXY / HTTPS_PROXY variables set up in your environment, or pass them through when you use dispatch.
export HTTP_PROXY="http://some-proxy.domain:port"
export HTTPS_PROXY="https://some-proxy.domain:port"
or
HTTP_PROXY="http://some-proxy.domain:port" HTTPS_PROXY="http://some-proxy.domain:port" ./dispatch-linux-x86_64 --owner AMDEPYC --repo sev-certify --tag main ubuntu
It may be worth including in the documentation that if you are in a segregated/restricted network that requires a Proxy to access the internet, you may have issues with dispatch accessing github.com unless the proxy is configured.
In my instance I observed that I was not receiving any of the SEV-3.0 Report Issues created when sev-certify had run successfully.
There are no proxy configuration options in dispatch, however it is simple to work around it on Linux. Either have your HTTP_PROXY / HTTPS_PROXY variables set up in your environment, or pass them through when you use dispatch.
export HTTP_PROXY="http://some-proxy.domain:port"export HTTPS_PROXY="https://some-proxy.domain:port"or
HTTP_PROXY="http://some-proxy.domain:port" HTTPS_PROXY="http://some-proxy.domain:port" ./dispatch-linux-x86_64 --owner AMDEPYC --repo sev-certify --tag main ubuntu