aws_lakeformation_permissions throwing "no permissions found" for wildcard table

[josh-aguilar]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform: v0.13.5
Provider: v0.34.0

Affected Resource(s)

• aws_lakeformation_permissions

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

resource "aws_lakeformation_permissions" "test" {
  principal = "arn:aws:iam::XXXXXXXXXXXX:role/MyRole"
  permissions = ["ALL", "ALTER", "DELETE", "DESCRIBE", "DROP", "INSERT", "SELECT"]
  permissions_with_grant_option = ["ALL", "ALTER", "DELETE", "DESCRIBE", "DROP", "INSERT", "SELECT"]
  table {
    database_name = "my_database"
    wildcard = true
  }
}

Debug Output

Panic Output

Expected Behavior

Running a terraform apply should succeed without any error messages.

Actual Behavior

When running a terraform apply the permissions are applied successfully as shown in this screenshot.

However, terraform throws the following error after finishing.

Error: error reading Lake Formation permissions: no permissions found

Steps to Reproduce

1. terraform apply

Important Factoids

• Only happens when wildcard is set to true for the table argument.
• This error only started showing up after version v3.33.0 of the AWS provider was released which included this fix
  r/aws_lakeformation_permissions: Fix bug where SELECT permissions are not properly read in from AWS #18203
• Downgrading the provider to v3.32.0 seems to work for us at the moment but would be good to have the latest version working.

References

[jackbatzner]

I can take a look at this one considering I caused it 😊 . I know the fix and just want to write a test first to confirm the situation here

[YakDriver]

Additional Principals	Perm Delete/Revoke
Related #16848 (Issue) Related #16916 Related #18034 (Issue) Related #18374	Related #17633 (Issue) Related #18446 (Issue) Related #18505 Related #19063 (Issue) Related #19064 (Issue)

[akuzni2]

That would be great to get a fix for this one - currently I have to write a block of TF to specify permissions for every table in my lake formation DB.

[ghost]

This has been released in version 3.39.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 for triage. Thanks!

[github-actions]

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.