-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Lake Formation Resource #13267
Lake Formation Resource #13267
Conversation
This is really great! I started working on this as well, and managed to get the data sources for |
@robertstettner Yes it would be great! Good new for data sources support. In a draft pull request #13396 for permissions support. Work well for my first local tests, I need to improve acceptance tests but I will keep you posted in a few days to get your feedback. |
Notification of Recent and Upcoming Changes to ContributionsThank you for this contribution! There have been a few recent development changes that affect this pull request. We apologize for the inconvenience, especially if there have been long review delays up until now. Please note that this is automated message from an unmonitored account. See the FAQ for additional information on the maintainer team and review prioritization. If you are unable to complete these updates, please leave a comment for the community and maintainers so someone can potentially continue the work. The maintainers will encourage other contributors to use the existing contribution as the base for additional changes as appropriate. Otherwise, contributions that do not receive updated code or comments from the original contributor may be closed in the future so the maintainers can focus on active items. For the most up to date information about Terraform AWS Provider development, see the Contributing Guide. Additional technical debt changes can be tracked with the As part of updating a pull request with these changes, the most current unit testing and linting will run. These may report issues that were not previously reported. Action Required: Terraform 0.12 SyntaxReference: #8950 Version 3 and later of the Terraform AWS Provider, which all existing contributions would potentially be added, only supports Terraform 0.12 and later. Certain syntax elements of Terraform 0.11 and earlier show deprecation warnings during runs with Terraform 0.12. Documentation and test configurations, such as those including deprecated string interpolations ( Action Required: Terraform Plugin SDK Version 2Reference: #14551 The Terraform AWS Provider has been upgraded to the latest version of the Terraform Plugin SDK. Generally, most changes to contributions should only involve updating Go import paths in source code files. Please see the referenced issue for additional information. Action Required: Removal of website/aws.erb FileReference: #14712 Any changes to the Upcoming Change of Git Branch NamingReference: #14292 Development environments will need their upstream Git branch updated from Upcoming Change of GitHub OrganizationReference: #14715 This repository will be migrating from https://github.com/terraform-providers/terraform-provider-aws to https://github.com/hashicorp/terraform-provider-aws. No practitioner or developer action is anticipated and most GitHub functionality will automatically redirect to the new location. Go import paths including |
7f583ec
to
7455563
Compare
@gmazelier @ewbankkit I think this is in a pretty good place. I'm waiting to get the other PRs in shape, and add a few data sources before merging. If you have any feedback on this after the changes, please let me know! Acceptance tests,
|
if _, ok := d.GetOk("role_arn"); !ok { | ||
return resourceAwsLakeFormationResourceCreate(d, meta) | ||
} |
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.
Maybe clearer to call RegisterResource()
here directly rather than call resourceAwsLakeFormationResourceCreate()
.
My head initially went to Why is role_arn
not ForceNew: true
?.
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.
After more investigating, I agree with the original approach of @gmazelier. ForceNew
is better. The UpdateResource()
API call is quirky and only works for IAM role to IAM role updates. I added new acceptance tests, docs to show the limits.
Co-authored-by: Kit Ewbank <Kit_Ewbank@hotmail.com>
58a01e6
to
870c35d
Compare
Latest: Acceptance tests,
|
Verified acceptance tests ( $ make testacc TEST=./aws/ TESTARGS='-run=TestAccAWSLakeFormationResource_'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAWSLakeFormationResource_ -timeout 120m
=== RUN TestAccAWSLakeFormationResource_basic
=== PAUSE TestAccAWSLakeFormationResource_basic
=== RUN TestAccAWSLakeFormationResource_disappears
=== PAUSE TestAccAWSLakeFormationResource_disappears
=== RUN TestAccAWSLakeFormationResource_serviceLinkedRole
=== PAUSE TestAccAWSLakeFormationResource_serviceLinkedRole
=== RUN TestAccAWSLakeFormationResource_updateRoleToRole
=== PAUSE TestAccAWSLakeFormationResource_updateRoleToRole
=== RUN TestAccAWSLakeFormationResource_updateSLRToRole
=== PAUSE TestAccAWSLakeFormationResource_updateSLRToRole
=== CONT TestAccAWSLakeFormationResource_basic
=== CONT TestAccAWSLakeFormationResource_updateRoleToRole
=== CONT TestAccAWSLakeFormationResource_updateSLRToRole
=== CONT TestAccAWSLakeFormationResource_serviceLinkedRole
=== CONT TestAccAWSLakeFormationResource_disappears
=== CONT TestAccAWSLakeFormationResource_updateSLRToRole
provider_test.go:777: skipping tests; missing IAM service-linked role /aws-service-role/lakeformation.amazonaws.com. Please create the role and retry
--- SKIP: TestAccAWSLakeFormationResource_updateSLRToRole (0.91s)
=== CONT TestAccAWSLakeFormationResource_serviceLinkedRole
provider_test.go:777: skipping tests; missing IAM service-linked role /aws-service-role/lakeformation.amazonaws.com. Please create the role and retry
--- SKIP: TestAccAWSLakeFormationResource_serviceLinkedRole (0.92s)
--- PASS: TestAccAWSLakeFormationResource_basic (26.26s)
--- PASS: TestAccAWSLakeFormationResource_disappears (26.30s)
--- PASS: TestAccAWSLakeFormationResource_updateRoleToRole (47.26s)
PASS
ok github.com/terraform-providers/terraform-provider-aws/aws 47.385s |
@YakDriver great! |
This has been released in version 3.22.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! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Relates #9700
Depends on #13250
AWS Lake Formation support: manages the data (Amazon S3 buckets and folders) that is being registered with AWS Lake Formation.
Release note for CHANGELOG:
Output from acceptance testing: