You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Terraform v1.2.5
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v4.32.0
+ provider registry.terraform.io/integrations/github v5.3.0
Your version of Terraform is out of date! The latest version
is 1.3.0. You can update by downloading from https://www.terraform.io/downloads.html
Issue not related to terraform version (see later)
Please list the steps required to reproduce the issue, for example:
Use a GITHUB_TOKEN that expired (it was my case)
try to terraform plan any code that use a github resource.
Important Factoids
The provider version in our codebase is pinned to 4.23 and has been working well for months.
The CI started to fail with the provider panic without any significant change in the code.
After raising Terraform logs to debug, I could identify the source of the problem to origin from the Bad credentials response from the API.
I double checked the validity of my token and could see that it expired. After I re-generated a token, I got rid of the error.
I reproduced the issue with the latest provider version (v5.3.0 when writting these lines).
The problem seems to come from an unhandle response type when credentials are invalid.
👋 Hey Friends, this issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Please add the Status: Pinned label if you feel that this issue needs to remain open/active. Thank you for your contributions and help in keeping things tidy!
Terraform Version
Issue not related to terraform version (see later)
Affected Resource(s)
Provider authentication
Terraform Configuration Files
N/A
Debug Output
Copying the interesting part:
Expected Behavior
No error
Actual Behavior
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
any code that use a github resource.Important Factoids
The provider version in our codebase is pinned to 4.23 and has been working well for months.
The CI started to fail with the provider panic without any significant change in the code.
After raising Terraform logs to debug, I could identify the source of the problem to origin from the
Bad credentials
response from the API.I double checked the validity of my token and could see that it expired. After I re-generated a token, I got rid of the error.
I reproduced the issue with the latest provider version (
v5.3.0
when writting these lines).The problem seems to come from an unhandle response type when credentials are invalid.
References
The text was updated successfully, but these errors were encountered: