You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,15 @@
1
+
## 27.2.0
2
+
3
+
NEW FEATURES:
4
+
* resource/cvo_gcp: Added support for `iops` and `throughput` parameters during GCP CVO creation with `hyperdisk-balanced` volume type.
5
+
* resource/aggregate: Added support for `iops` and `throughput` parameters during aggregate creation with `hyperdisk-balanced` provider volume type.
6
+
* resource/aggregate: Added support for in-place update of `iops` and `throughput` on existing `hyperdisk-balanced` aggregates without requiring resource recreation.
7
+
8
+
ENHANCEMENTS:
9
+
* resource/aggregate: Added `Computed` attribute for `iops` and `throughput` to support import and drift detection by reading actual values from the API.
10
+
* resource/aggregate: Added conditional `ForceNew` via `CustomizeDiff` for `iops` and `throughput` — in-place update for `hyperdisk-balanced`, destroy+recreate for other volume types (backward compatible).
11
+
* resource/aggregate: Updated import to populate `iops` and `throughput` from the API response.
Description: "Provisioned IOPS. Applicable when provider_volume_type is 'io1', 'gp3', or 'hyperdisk-balanced'. For 'hyperdisk-balanced', valid range is 3000-160000.",
81
82
},
82
83
"throughput": {
83
-
Type: schema.TypeInt,
84
-
Optional: true,
85
-
ForceNew: true,
84
+
Type: schema.TypeInt,
85
+
Optional: true,
86
+
Computed: true,
87
+
Description: "Provisioned throughput in MBps. Applicable when provider_volume_type is 'gp3' or 'hyperdisk-balanced'. For 'hyperdisk-balanced', valid range is 140-2400.",
Description: "Provisioned IOPS for the initial aggregate. Only applicable when gcp_volume_type is 'hyperdisk-balanced'. Valid range is 3000-160000. To update IOPS after creation, use the netapp-cloudmanager_aggregate resource.",
82
+
},
83
+
"throughput": {
84
+
Type: schema.TypeInt,
85
+
Optional: true,
86
+
ForceNew: true,
87
+
Description: "Provisioned throughput for the initial aggregate. Only applicable when gcp_volume_type is 'hyperdisk-balanced'. Valid range is 140-2400. To update throughput after creation, use the netapp-cloudmanager_aggregate resource.",
if (hasIops||hasThroughput) &&gcpVolumeType!="hyperdisk-balanced" {
995
+
returnfmt.Errorf("performance parameters (iops, throughput) can only be specified when gcp_volume_type is 'hyperdisk-balanced', current type is '%s'", gcpVolumeType)
@@ -85,10 +103,10 @@ The following arguments are supported:
85
103
*`disk_size_size` - (Optional, Forces new resource) The required size of the disks. The max number depends on the `provider_volume_type`. Details in this document: AWS: [https://docs.netapp.com/us-en/cloud-volumes-ontap-relnotes/reference-limits-aws.html#aggregate-limits] Azure: [https://docs.netapp.com/us-en/cloud-volumes-ontap-relnotes/reference-limits-azure.html#aggregate-limits] GCP: [https://docs.netapp.com/us-en/cloud-volumes-ontap-relnotes/reference-limits-gcp.html#disk-and-tiering-limits]**Note: Must be provided together with `disk_size_unit`**
86
104
*`disk_size_unit` - (Optional, Forces new resource) The disk size unit ['GB' or 'TB']. **Note: Must be provided together with `disk_size_size`**
87
105
*`home_node` - (Optional, Forces new resource) The home node that the new aggregate should belong to. The default is the first node.
88
-
*`provider_volume_type` - (Optional, Forces new resource) The cloud provider volume type. For AWS: ['gp3', 'gp2', 'io1', 'st1', 'sc1']. For Azure: ['Premium_LRS','Standard_LRS','StandardSSD_LRS']. For GCP: ['pd-balanced', 'pd-ssd','pd-standard']
106
+
*`provider_volume_type` - (Optional, Forces new resource) The cloud provider volume type. For AWS: ['gp3', 'gp2', 'io1', 'st1', 'sc1']. For Azure: ['Premium_LRS','Standard_LRS','StandardSSD_LRS']. For GCP: ['pd-balanced', 'pd-ssd','pd-standard', 'hyperdisk-balanced']
89
107
*`capacity_tier` - (Optional, Forces new resource) The aggregate's capacity tier for tiering cold data to object storage: ['S3', 'Blob', 'cloudStorage']. The default values for each cloud provider are as follows: Amazon => 'S3', Azure => 'Blob', GCP => 'cloudStorage'. If NONE, the capacity tier won't be set on aggregate creation.
90
-
*`iops` - (Optional, Forces new resource) Provisioned IOPS. Needed only when 'providerVolumeType' is 'io1'or 'gp3'
91
-
*`throughput` - (Optional, Forces new resource) Required only when 'providerVolumeType' is 'gp3'.
108
+
*`iops` - (Optional) Provisioned IOPS. Applicable when 'providerVolumeType' is 'io1', 'gp3', or 'hyperdisk-balanced'. For 'hyperdisk-balanced', valid range is 3000-160000. Can be updated in-place for 'hyperdisk-balanced'; for other disk types, changing this value requires resource recreation.
109
+
*`throughput` - (Optional) Provisioned throughput in MBps. Applicable when 'providerVolumeType' is 'gp3' or 'hyperdisk-balanced'. For 'hyperdisk-balanced', valid range is 140-2400. Can be updated in-place for 'hyperdisk-balanced'; for other disk types, changing this value requires resource recreation.
92
110
*`initial_ev_aggregate_size` - (Optional, Forces new resource) Initial size for EBS Elastic Volumes aggregate (AWS only). This enables the aggregate to support capacity expansion using Amazon EBS Elastic Volumes. **Creation time only** - cannot be modified after aggregate creation. **Note: Must be provided together with `initial_ev_aggregate_unit`**
93
111
*`initial_ev_aggregate_unit` - (Optional, Forces new resource) Unit for initial EBS Elastic Volumes aggregate size (GB, TB, GiB, or TiB). Only used with `initial_ev_aggregate_size`. Defaults to 'GB' if not specified. **Creation time only** - cannot be modified after aggregate creation. **Note: Must be provided together with `initial_ev_aggregate_size`**
94
112
*`increase_capacity_size` - (Optional, Computed) Additional capacity to add to the aggregate using Amazon EBS Elastic Volumes. **Only supported for AWS aggregates with EBS Elastic Volumes enabled**. **Update operation only** - cannot be used during aggregate creation. The aggregate must be created with `initial_ev_aggregate_size` to support capacity increases. **Important:** After a successful capacity increase operation, remove the parameter from your configuration to prevent unnecessary state changes and achieve idempotency in subsequent Terraform runs. **Note: Must be provided together with `increase_capacity_unit`**
0 commit comments