Now, my build and deploy which currently contains just the oicd login job fails with “OIDC Token cannot be found. A CircleCI context must be specified.”. What am I missing here? It looks to be the same as per tutorial, as the install steps ensures aws cli is available. Logs are showing that the orb would try to do the assume role bit but it’s missing the “CIRCLE_OIDC_TOKEN” variable which it’s supposed to exist?
Hi @andrei-dascalu, could you please double check that you don’t have a typo in the context name by any chance?
Alternatively you can check in the job log, the 2nd step - Preparing environment variables should list it at the bottom - like this CIRCLE_OIDC_TOKEN=**REDACTED**
@zmarkan I’m having this same problem. The CIRCLE_OIDC_TOKEN environment variable has been present and working for several months, and just a few days ago it stopped being present in the list of environment variables. I confirmed that the context exists, and git blame tells me there hasn’t been any interesting changes to my CircleCI config in some time.
Is there anything else that needs to happen for CircleCI to provide the token? We haven’t made any changes to our AWS Identity Provider either.
We aren’t using any of those orbs; our build job installs the AWS CLI as an explicit run step. This has been working fine as well for several months, but I am looking for confirmation that the orb isn’t required to make the CIRCLE_OIDC_TOKEN env var available.
BTW, I confirmed that the context in question (called vm-aws), is being used by the job, because I added an arbitrary environment variable to it, and confirmed that the variable shows up in the build. So it seems that just “having a context” is insufficient to get the CIRCLE_OIDC_TOKEN to appear.