Closed relivnd closed 3 months ago
Voting for Prioritization
Volunteering to Work on This Issue
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.
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:
aws_fsx_ontap_file_system
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).
I think adding a note to the documentation is the most sensible option for now - I've submitted a PR.
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
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!
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.
Terraform Core Version
1.9.0
AWS Provider Version
5.56.0
Affected Resource(s)
aws_fsx_ontap_file_system
Expected Behavior
I expect a string containing the DNS name at the dns_name field in the state. The DNS name is visible in the AWS Console.
Actual Behavior
The field is null and thus can't be used e.g. to mount the file-share via nfs.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
terraform { required_version = ">= 1.8.4"
required_providers { aws = { source = "hashicorp/aws" version = ">= 5.0" } } }
provider "aws" { region = "eu-central-1"
default_tags { tags = { managed_by = "Terraform" repository = "something" } } }
data "aws_fsx_ontap_file_system" "example" { id = "id-of_deployed_fsx_ontap" }
Steps to Reproduce
terraform state show data.aws_fsx_ontap_file_system.example
==> Missing dns_nameDebug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None