Currently calling the regenerate upload token endpoint returns an HTTP status code of 204 with no response body. I would like to receive back the generated token so I can integrate it into my CI pipeline automation.
I have a CI pipeline that allows my dev team to generate new services from a dashboard. As part of the service provisioning, I would like to inject the
CODECOV_TOKEN env var into an encrypted secrets file along with other provisioning artifacts. Our CI can then decrypt this value and use it when new service builds are generated.
We are trying to reduce the number of unique vendor page visits that our developers have to make when setting up their services. Right now, developers have to go to Codecov and manually fetch the upload token. This wouldn’t be problematic in most cases, but in some instances we are working with other organizations and dont share IT or other administrative access, and in those cases our IT has to intervene and either set up the token or give the developer temporary access.
Is it possible to expose this token as a result of the regenerate token call?
No applicable examples
Most of our services are written in Go. We use GitHub Enterprise for code hosting. Our current CI is Codeship, but we are comtemplating GitHub Actions