We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
autosize
ontap_storage_volume_resource
Add autosize to ontap_storage_volume_resource
netapp-ontap_storage_volume_resource
resource "netapp-ontap_storage_volume_resource" "example" { cx_profile_name = "cluster5" name = "vol1" svm_name = "svm2" aggregates = [ { name = "aggr2" }, ] space_guarantee = "none" snapshot_policy = "default-1weekly" encryption = true snaplock = { type = "non_snaplock" } space = { size = 30 size_unit = "mb" percent_snapshot_space = 20 logical_space = { enforcement = true reporting = true } } tiering = { policy_name = "all" } nas = { export_policy_name = "test" group_id = 10 user_id = 20 unix_permissions = "755" security_style = "mixed" junction_path = "/testacc" } ## New autosize autosize { grow_threshold = 50 maximum = 1000 # Maximum size in bytes minimum = 7000 # Minimum size in bytes mode = grow # or `grow_shrink` or `off` shrink_threshold = 20 size_unit = 'gb' # Not part of the API but useful for Code } }
https://docs.netapp.com/us-en/ontap-restapi-9131//ontap/patch-storage-volumes-.html#definitions
None
The text was updated successfully, but these errors were encountered:
I've added this to the next major release, which will be 1.2.
Sorry, something went wrong.
csahu9
Successfully merging a pull request may close this issue.
Description
Add
autosize
toontap_storage_volume_resource
Affected Resource(s) and/or Data Source(s)
netapp-ontap_storage_volume_resource
Potential Terraform Configuration
References
https://docs.netapp.com/us-en/ontap-restapi-9131//ontap/patch-storage-volumes-.html#definitions
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: