-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[New Data Source]: aws_fsx_ontap_storage_virtual_machine #30348
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.18.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. |
Description
Currently there is no way to query an existing FSxN storage virtual machine.
The SVM ID is required by the
aws_fsx_ontap_volume
resource to create/manage volumes. Without being able to query existing SVMs, we are not able to manage FSxN volumes from external Terraform codebases. Our use case is we'd like to manage a central FSxN file system but allow individual teams to create and manage volumes as part of their own platform deployments.Requested Resource(s) and/or Data Source(s)
aws_fsx_ontap_storage_virtual_machine
Potential Terraform Configuration
References
Ideally would be implemented along with
aws_fsx_ontap_file_system
, which was requested here: #25166Would you like to implement a fix?
No
The text was updated successfully, but these errors were encountered: