Skip to content

Commit

Permalink
Update network type
Browse files Browse the repository at this point in the history
  • Loading branch information
mahesh-hpe committed Jan 4, 2024
1 parent 3e16726 commit 2d9a732
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 4 deletions.
4 changes: 2 additions & 2 deletions examples/data-sources/hpegl_vmaas_network_type/data-source.tf
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# (C) Copyright 2021 Hewlett Packard Enterprise Development LP
# (C) Copyright 2021-2024 Hewlett Packard Enterprise Development LP

data "hpegl_vmaas_network_type" "nsxt_net_type" {
name = "NSX-T Segment"
name = "NSX Segment"
}
4 changes: 2 additions & 2 deletions internal/resources/data_source_network_type.go
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
// (C) Copyright 2021 Hewlett Packard Enterprise Development LP
// (C) Copyright 2021-2024 Hewlett Packard Enterprise Development LP

package resources

Expand All @@ -17,7 +17,7 @@ func NetworkTypeData() *schema.Resource {
"name": {
Type: schema.TypeString,
Required: true,
Description: "Name of the network type. Example 'NSX-T Segment' or 'Custom Network'",
Description: "Name of the network type. Example 'NSX Segment' or 'Custom Network'",
},
},
ReadContext: networkTypeReadContext,
Expand Down
2 changes: 2 additions & 0 deletions templates/resources/vmaas_network.md.tmpl
Original file line number Diff line number Diff line change
Expand Up @@ -31,4 +31,6 @@ For creating an NSX-T network, see the following examples.
This issue is already fixed in the later versions and will be released soon. For time being we are recommending manually
updating the IP pool from UI. This issue is fixed in 5.4.9 versions.

~> From 6.2.4 version, DataSource `hpegl_vmaas_network_type` expects `NSX Segment` instead of `NSX-T Segment` in the `name` attribute.

{{ .SchemaMarkdown | trimspace }}

0 comments on commit 2d9a732

Please sign in to comment.