hashicorp / terraform-provider-aws

The AWS Provider enables Terraform to manage AWS resources.
https://registry.terraform.io/providers/hashicorp/aws
Mozilla Public License 2.0
9.74k stars 9.1k forks source link

aws_lakeformation_permissions column level permission is not working #19409

Closed surendarkaniops closed 3 years ago

surendarkaniops commented 3 years ago

aws_lakeformation_permissions column level permission is not working even i tried wild card value.

resource "aws_lakeformation_permissions" "grantpermission-columns-users_wildcard" { count = var.columns_wildcard ? 1 : 0 principal = var.user_principal permissions = var.user_permissions_coloumn table_with_columns { database_name = var.user_database name = var.user_database_table excluded_column_names = var.excluded_column_names wildcard = var.columns_wildcard } }

user_permissions_table = ["CREATE_TABLE", "ALTER", "DROP"] user_permissions_coloumn = ["CREATE_TABLE", "ALTER", "DROP"] columns_wildcard = true excluded_column_names = ["policyid"] ## must and only when columns_wildcard arguement is enabled user_principal = "arn:aws:iam:::role/LakeFormationAnalyst" athena_query_savings = "supertest-dataprocessed" crawler_data_source = "supertest-datasource"

YakDriver commented 3 years ago

@surendarkaniops You cannot apply CREATE_TABLE permission this way as it is not a columnar permission. Besides that issue, I have verified that your test case works with #19817. I added a new acceptance test called TestAccAWSLakeFormation_serial/TableWithColumnsPermissions/columnWildcardExcludedColumnsPermissions specifically to test that wildcard + excluded column names works.

github-actions[bot] commented 3 years ago

This functionality has been released in v3.46.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!

github-actions[bot] commented 3 years ago

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.