Skip to content

Commit

Permalink
doc update for vni in instance and shares
Browse files Browse the repository at this point in the history
  • Loading branch information
ujjwal-ibm authored and hkantare committed Jun 18, 2024
1 parent 8bf6bfb commit b405819
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions website/docs/r/is_instance.html.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -590,7 +590,7 @@ Review the argument references that you can specify for your resource.
- `allow_ip_spoofing` - (Optional, Boolean) Indicates whether source IP spoofing is allowed on this interface. If false, source IP spoofing is prevented on this interface. If true, source IP spoofing is allowed on this interface.
- `auto_delete` - (Optional, Boolean) Indicates whether this virtual network interface will be automatically deleted when target is deleted
- `enable_infrastructure_nat` - (Optional, Boolean) If true: The VPC infrastructure performs any needed NAT operations and floating_ips must not have more than one floating IP. If false: Packets are passed unchanged to/from the virtual network interface, allowing the workload to perform any needed NAT operations, allow_ip_spoofing must be false, can only be attached to a target with a resource_type of bare_metal_server_network_attachment.
- `name` - (Optional, String) The resource type.
- `name` - (Optional, String) The virtual network interface name. The name must not be used by another virtual network interface in the VPC.
- `ips` - (Optional, Array of String) Additional IP addresses to bind to the virtual network interface. Each item may be either a reserved IP identity, or a reserved IP prototype object which will be used to create a new reserved IP. All IP addresses must be in the primary IP's subnet.
~> **NOTE** to add `ips` only existing `reserved_ip` is supported, new reserved_ip creation is not supported as it leads to unmanaged(dangling) reserved ips. Use `ibm_is_subnet_reserved_ip` to create a reserved_ip
- `resource_group` - (Optional, String) The resource type.
Expand Down Expand Up @@ -644,7 +644,7 @@ Review the argument references that you can specify for your resource.
- `allow_ip_spoofing` - (Optional, Boolean) Indicates whether source IP spoofing is allowed on this interface. If false, source IP spoofing is prevented on this interface. If true, source IP spoofing is allowed on this interface.
- `auto_delete` - (Optional, Boolean) Indicates whether this virtual network interface will be automatically deleted when target is deleted
- `enable_infrastructure_nat` - (Optional, Boolean) If true: The VPC infrastructure performs any needed NAT operations and floating_ips must not have more than one floating IP. If false: Packets are passed unchanged to/from the virtual network interface, allowing the workload to perform any needed NAT operations, allow_ip_spoofing must be false, can only be attached to a target with a resource_type of bare_metal_server_network_attachment.
- `name` - (Optional, String) The resource type.
- `name` - (Optional, String) The virtual network interface name. The name must not be used by another virtual network interface in the VPC.
- `ips` - (Optional, Array of String) Additional IP addresses to bind to the virtual network interface. Each item may be either a reserved IP identity, or a reserved IP prototype object which will be used to create a new reserved IP. All IP addresses must be in the primary IP's subnet.
- `resource_group` - (Optional, String) The resource type.
- `security_groups` - (Optional, Array of String) The resource type.
Expand Down
4 changes: 2 additions & 2 deletions website/docs/r/is_share.html.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ The following arguments are supported:
- `virtual_network_interface` (Optional, List) The virtual network interface for this share mount target. Required if the share's `access_control_mode` is `security_group`.

Nested scheme for `virtual_network_interface`:
- `name` - (Required, String) Name for this virtual network interface.
- `name` - (Required, String) Name for this virtual network interface. The name must not be used by another virtual network interface in the VPC.
- `id` - (Optional) The ID for virtual network interface. Mutually exclusive with other `virtual_network_interface` arguments.

~> **Note**
Expand Down Expand Up @@ -158,7 +158,7 @@ The following arguments are supported:
- `name` - (Optional, String)
- `virtual_network_interface` (Optional, List) The virtual network interface for this share mount target. Required if the share's `access_control_mode` is `security_group`.
Nested scheme for `virtual_network_interface`:
- `name` - (Required, String) Name for this virtual network interface.
- `name` - (Required, String) Name for this virtual network interface. The name must not be used by another virtual network interface in the VPC.
- `id` - (Optional) The ID for virtual network interface. Mutually exclusive with other `virtual_network_interface` arguments.

~> **Note**
Expand Down
2 changes: 1 addition & 1 deletion website/docs/r/is_share_mount_target.html.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The following arguments are supported:

- `share` - (Required, String) The file share identifier.
- `virtual_network_interface` (Optional, List) The virtual network interface for this share mount target. Required if the share's `access_control_mode` is `security_group`.
- `name` - (Required, String) Name for this virtual network interface.
- `name` - (Required, String) Name for this virtual network interface. The name must not be used by another virtual network interface in the VPC.
Nested scheme for `virtual_network_interface`:
- `id` - (Optional) The ID for virtual network interface. Mutually exclusive with other `virtual_network_interface` arguments.

Expand Down

0 comments on commit b405819

Please sign in to comment.