-
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
resource/aws_transfer_user: add home_directory_type and home_directory_mappings arguments #13591
resource/aws_transfer_user: add home_directory_type and home_directory_mappings arguments #13591
Conversation
…s_transfer_user resource
Thanks for the PR! Does this functionality differ from the functionality in #12599? |
This functionality is a subset of the pr you mention, which could (and possibly should) have been separated so it could add value sooner. I could revise the code so it matches the mentioned pr? |
Is it possible to merge this PR? It's indeed covered by 12599 - however that one implements several features and seems to be blocked on an unrelated topic, waiting for another PR itself (VPC endpoint). Without this functionality we must fall back to CloudFormation to manage AWS Transfer users, especially as directory mappings are not available in the AWS Console. Thanks. |
Who is this "AWS Provider" guy and why hasn't he reviewed this PR? I've been waiting for this for weeks now and it looks like others have been waiting even longer. How is it this simple, yet valuable fix hasn't made it into one of the several releases since this PRs creation? |
In case it helps you out, I worked around this issue by:
|
Thank you very much, I'll give it a shot! I'm trying to run this from Terraform Cloud, hopefully their executors allow local-exec operations..... |
I used Terraform Cloud before at a previous company, and local-exec was not the problem but i'd image you don't have AWS cli available in the images they run on 😅 |
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.
This looks good, thanks for the updates here, @quinyx-tjeerd 🚀
Output from acceptance testing:
--- PASS: TestAccAWSTransferUser_basic (20.00s)
--- PASS: TestAccAWSTransferUser_disappears (16.77s)
--- PASS: TestAccAWSTransferUser_homeDirectoryMappings (30.78s)
--- PASS: TestAccAWSTransferUser_modifyWithOptions (43.38s)
--- PASS: TestAccAWSTransferUser_UserName_Validation (8.93s)
|
||
resource "aws_iam_role_policy" "foo" { | ||
name = "tf-test-transfer-user-iam-policy-%s" | ||
role = "${aws_iam_role.foo.id}" |
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.
Nit: We are now using Terraform 0.12+ syntax in test configurations, will adjust on merge. 👍
This has been released in version 3.8.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
Original PR:
#11483
I resolved the conflict
Closes #11281
Relates #11632
Release note for CHANGELOG:
Output from acceptance testing: