Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
Load Balancer → Attach NIC
AI-generatedSummary
Attaches a network interface card (NIC) to a load balancer in the specified datacenter. The provided source pack contains no operation implementation, so the attachment’s required identifiers and return details cannot be confirmed from source.
Inputs
- Datacenter ID (required) — ID of the datacenter containing the load balancer.
- Include Request Status — Defaults to false. When enabled, includes the asynchronous request tracking ID and status URL when the API returns a Location header.
- Include Response Headers — Defaults to false. When enabled, nests the response body under
bodyand includesheadersandstatusCode. - Request Options — Optional batching, SSL certificate validation, HTTP proxy, and request timeout settings. Batching defaults to 50 items per batch with a 1000 ms interval; timeout defaults to 10000 ms.
Output shape
Not determinable from the supplied source pack.
The pack includes no implementation body for the load balancer operation. If response headers are enabled, the declared output format places the response body under
body, alongsideheadersandstatusCode; request status can also be included for asynchronous operations.