Terraform-provider-aws: AWS DataSync SMB locations

[ewbankkit]

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 "me too" comments, 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

Description

AWS DataSync now supports the Server Message Block (SMB) protocol.

New or Affected Resource(s)

• aws_datasync_location_smb

Potential Terraform Configuration

resource "aws_datasync_location_smb" "example" {
  agent_arns = ["${aws_datasync_agent.example.arn}"]

  server_hostname = "smb.example.com"
  subdirectory    = "/exported/path"
}

References

Announcement.
API reference.

Requires:

• https://github.com/terraform-providers/terraform-provider-aws/pull/9770

[cjbeckwith]

Curious where you are at in regards to the aws_datasync_location_smb resource. I see that AWS PS just released a cmdlet for it, but as of 2.31 I don't see reference to this particular resource. Looking to use it sooner rather than later.

[mark-bixler]

How many votes are needed before this becomes priority? :) Tasked with a massive project to roll-out 27 agents and various tasks to SMB Share

[thatderek]

@mark-bixler If you want to go upvote #10381, that one is ready for review and your :+1: might help it get visibility.

[bflad]

Support for this new resource has been merged and will release with version 2.48.0 of the Terraform AWS Provider, Thursday this week. Thanks to @thatderek for the implementation. 👍

[hashibot[bot]]

This has been released in version 2.48.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!

[hashibot[bot]]

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!