I think adding a note to the documentation is the most sensible option for now - I've submitted a PR.

from terraform-provider-aws.

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

from terraform-provider-aws.

If I am not mistaken, FSx for ONTAP file systems would only provide DNS names for the management and inter-cluster endpoint. To access the file system and volumes, you also need to use a Storage Virtual Machine (SVM), which should provide you with the endpoint (DNS name) to connect to it for different protocols (SMB, NFS, iSCSI). See the aws_fsx_ontap_storage_virtual_machine resource for details.

The aws_fsx_ontap_file_system resource likely just inherited the dns_name attribute that is part of the more general FileSystem data type that is common across different flavors of FSx, but not "used" for FSx for ONTAP file systems.

from terraform-provider-aws.

You're right. I resolved it in my case by using the DNS name from data.aws_fsx_ontap_storage_virtual_machine and concatenating it with the junction path of the volume. Although it might even be slightly cleaner to use the data block for the SVM in the first place, I think it would be better to either:

• remove the DNS name property from aws_fsx_ontap_file_system
• make it work, by populating the field with the expected DNS name
• clearly state in the documentation, that the field is not populated with any data, because it's inherited but not used

Otherwise one is just questioning why the code is not working, even though there's an underlying reason.
Currently, the documentation is misleading to:
dns_name - DNS name for the file system (e.g. fs-12345678.corp.example.com).

from terraform-provider-aws.

from terraform-provider-aws.

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

from terraform-provider-aws.