-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
internal/framework/types: surface ARN validation errors #40008
Conversation
Community NoteVoting for Prioritization
For Submitters
|
Previously the `ARNType`s `ValueFromString` method parsed the string value and set the value to Unknown in cases where validation failed. This caused a plan time failure indicating a difference between the planned value (unknown) and config value (known string). This obfuscated the underlying error which is actually an invalid ARN value. Invalid ARNs provided in a configuration will now produce errors similar to the following: ``` │ Error: Invalid ARN Value │ │ with aws_bedrockagent_agent.test, │ on main.tf line 16, in resource "aws_bedrockagent_agent" "test": │ 16: agent_resource_role_arn = "INVALID-ARN" │ │ The provided value cannot be parsed as an ARN. │ │ Path: agent_resource_role_arn │ Value: INVALID-ARN ```
896689a
to
a3fef14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀
This functionality has been released in v5.75.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Previously the
ARNType
sValueFromString
method parsed the string value and set the value to Unknown in cases where validation failed. This caused a plan time failure indicating a difference between the planned value (unknown) and config value (known string). This obfuscated the underlying error which is actually an invalid ARN value.Invalid ARNs provided in a configuration will now produce errors similar to the following:
Relations
Closes #39227