New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing required GCS remote state configuration project since Terragrunt 0.44.2 #2477
Comments
Further testing reveals that removing the service account impersonation also fixes the problem. |
We encountered a similar issue with Terragrunt 0.45.
A downgrade to 0.44.1 helped. |
It's probably caused by an update of the underlying dependency cloud.google.com/go/storage from v1.16.0 to v1.27.0 introduced by github.com/hashicorp/go-getter v1.6.2 => v1.7.0 #2454 |
This PR was merged for the google-cloud-go/storage v1.27.0 release, that might be a starting point? |
Any chance on this getting resolved? Service Account Impersonation with remote state configuration is just broken at the moment. :-( |
Fix released in https://github.com/gruntwork-io/terragrunt/releases/tag/v0.50.6 |
This doesn't seem to be actually fixed. I'm getting this error with the current version today. Unsetting my GOOGLE_APPLICATION_CREDENTIALS and just using my user account worked fine but as soon as I set GOOGLE_APPLICATION_CREDENTIALS to a service account key file, it gets this error again. |
@yinzara is correct. I am also still getting this error with the current version as well. |
Could we get this issue reopened? |
Hey there, since updating to Terragrunt 0.44.2 we have problems with our GCS remote state configuration.
Reverting to 0.44.1 fixes the error.
The debug logs show terragrunt searching for the bucket but nothing changed on the remote end or at the authentication level. The only difference is the terragrunt version.
Were there any breaking changes regarding the GCS remote state configuration? I can see that 0.44.4 introduces new authentication method, but the error appears for 0.44.2 AND 0.44.4 but not for 0.44.1
Anything I can try on my side?
The text was updated successfully, but these errors were encountered: