-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Confusing error message from the S3 backend with empty-string argument values #29557
Comments
Thanks for reporting this, @alFReD-NSH! Based on the terminology in that error message it seems like this is something being returned from the underlying AWS SDK rather than directly by Terraform, so I suppose the S3 backend must be just passing the message through verbatim without interpreting it into Terraform terminology first. (I'm assuming that You're right that it's weird that this error isn't at least being annotated by the source location of the data resource that caused it. Along with that, it also seems like the S3 backend's configuration processing logic is missing some validation rules to detect if the If the S3 backend were handling this validation itself then I think it should be possible to return a pair of higher-quality error messages referring directly to the problematic expressions:
It's possible that this might run into some unusual extra challenges because for Thanks again! |
This has been fixed at some point since the issue was filed |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Version
Terraform Configuration Files
Debug Output
https://gist.github.com/alFReD-NSH/517e76e09d9e6733174f76b4d37d9a5f
Crash Output
Expected Behavior
The error should state which file and which line or which resource/datasource it came from.
Actual Behavior
The error does not state which file and which line or which resource/datasource it came from.
Steps to Reproduce
terraform init
terraform apply
The text was updated successfully, but these errors were encountered: