I ran into a resource sequencing issue that was not immediately apparent because of the generic error message returned during an apply failure. The aws_verifiedpermissions_policy resource will fail to apply with a generic "invalid input" error if the aws_verifiedpermissions_policy_store it is created within has the validation_settings set to STRICT mode, and the schema is not present yet. The debug logs show that the Go SDK returns a more detailed error message within the "fieldList" attribute, and my request is that these more detailed error messages be surfaced in the apply error message shown by terraform.
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Description
I ran into a resource sequencing issue that was not immediately apparent because of the generic error message returned during an apply failure. The aws_verifiedpermissions_policy resource will fail to apply with a generic "invalid input" error if the aws_verifiedpermissions_policy_store it is created within has the
validation_settings
set toSTRICT
mode, and the schema is not present yet. The debug logs show that the Go SDK returns a more detailed error message within the "fieldList" attribute, and my request is that these more detailed error messages be surfaced in the apply error message shown by terraform.Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
References
Terraform error message:
Relevant log snippet showing the more detailed message being available within the "fieldList" attribute:
Would you like to implement a fix?
None