ionoscloud.compute.IPFailover
Explore with Pulumi AI
Manages IP Failover groups on IonosCloud.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as ionoscloud from "@ionos-cloud/sdk-pulumi";
import * as random from "@pulumi/random";
const example = new ionoscloud.compute.Datacenter("example", {
name: "Datacenter Example",
location: "us/las",
description: "Datacenter Description",
secAuthProtection: false,
});
const exampleIPBlock = new ionoscloud.compute.IPBlock("example", {
location: "us/las",
size: 1,
name: "IP Block Example",
});
const exampleLan = new ionoscloud.compute.Lan("example", {
datacenterId: example.id,
"public": true,
name: "Lan Example",
});
const serverImagePassword = new random.index.Password("server_image_password", {
length: 16,
special: false,
});
const exampleServer = new ionoscloud.compute.Server("example", {
name: "Server Example",
datacenterId: example.id,
cores: 1,
ram: 1024,
availabilityZone: "ZONE_1",
cpuFamily: "INTEL_XEON",
imageName: "Ubuntu-20.04",
imagePassword: serverImagePassword.result,
volume: {
name: "system",
size: 14,
diskType: "SSD",
},
nic: {
lan: 1,
dhcp: true,
firewallActive: true,
ips: [exampleIPBlock.ips[0]],
},
});
const exampleIPFailover = new ionoscloud.compute.IPFailover("example", {
datacenterId: example.id,
lanId: exampleLan.id,
ip: exampleIPBlock.ips[0],
nicuuid: exampleServer.primaryNic,
}, {
dependsOn: [exampleLan],
});
import pulumi
import pulumi_ionoscloud as ionoscloud
import pulumi_random as random
example = ionoscloud.compute.Datacenter("example",
name="Datacenter Example",
location="us/las",
description="Datacenter Description",
sec_auth_protection=False)
example_ip_block = ionoscloud.compute.IPBlock("example",
location="us/las",
size=1,
name="IP Block Example")
example_lan = ionoscloud.compute.Lan("example",
datacenter_id=example.id,
public=True,
name="Lan Example")
server_image_password = random.index.Password("server_image_password",
length=16,
special=False)
example_server = ionoscloud.compute.Server("example",
name="Server Example",
datacenter_id=example.id,
cores=1,
ram=1024,
availability_zone="ZONE_1",
cpu_family="INTEL_XEON",
image_name="Ubuntu-20.04",
image_password=server_image_password["result"],
volume={
"name": "system",
"size": 14,
"disk_type": "SSD",
},
nic={
"lan": 1,
"dhcp": True,
"firewall_active": True,
"ips": [example_ip_block.ips[0]],
})
example_ip_failover = ionoscloud.compute.IPFailover("example",
datacenter_id=example.id,
lan_id=example_lan.id,
ip=example_ip_block.ips[0],
nicuuid=example_server.primary_nic,
opts = pulumi.ResourceOptions(depends_on=[example_lan]))
package main
import (
"github.com/ionos-cloud/pulumi-ionoscloud/sdk/go/ionoscloud/compute"
"github.com/pulumi/pulumi-random/sdk/go/random"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
example, err := compute.NewDatacenter(ctx, "example", &compute.DatacenterArgs{
Name: pulumi.String("Datacenter Example"),
Location: pulumi.String("us/las"),
Description: pulumi.String("Datacenter Description"),
SecAuthProtection: pulumi.Bool(false),
})
if err != nil {
return err
}
exampleIPBlock, err := compute.NewIPBlock(ctx, "example", &compute.IPBlockArgs{
Location: pulumi.String("us/las"),
Size: pulumi.Int(1),
Name: pulumi.String("IP Block Example"),
})
if err != nil {
return err
}
exampleLan, err := compute.NewLan(ctx, "example", &compute.LanArgs{
DatacenterId: example.ID(),
Public: pulumi.Bool(true),
Name: pulumi.String("Lan Example"),
})
if err != nil {
return err
}
serverImagePassword, err := random.NewPassword(ctx, "server_image_password", &random.PasswordArgs{
Length: 16,
Special: false,
})
if err != nil {
return err
}
exampleServer, err := compute.NewServer(ctx, "example", &compute.ServerArgs{
Name: pulumi.String("Server Example"),
DatacenterId: example.ID(),
Cores: pulumi.Int(1),
Ram: pulumi.Int(1024),
AvailabilityZone: pulumi.String("ZONE_1"),
CpuFamily: pulumi.String("INTEL_XEON"),
ImageName: pulumi.String("Ubuntu-20.04"),
ImagePassword: serverImagePassword.Result,
Volume: &compute.ServerVolumeArgs{
Name: pulumi.String("system"),
Size: pulumi.Int(14),
DiskType: pulumi.String("SSD"),
},
Nic: &compute.ServerNicArgs{
Lan: pulumi.Int(1),
Dhcp: pulumi.Bool(true),
FirewallActive: pulumi.Bool(true),
Ips: pulumi.StringArray{
exampleIPBlock.Ips.ApplyT(func(ips []string) (string, error) {
return ips[0], nil
}).(pulumi.StringOutput),
},
},
})
if err != nil {
return err
}
_, err = compute.NewIPFailover(ctx, "example", &compute.IPFailoverArgs{
DatacenterId: example.ID(),
LanId: exampleLan.ID(),
Ip: exampleIPBlock.Ips.ApplyT(func(ips []string) (string, error) {
return ips[0], nil
}).(pulumi.StringOutput),
Nicuuid: exampleServer.PrimaryNic,
}, pulumi.DependsOn([]pulumi.Resource{
exampleLan,
}))
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Ionoscloud = Ionoscloud.Pulumi.Ionoscloud;
using Random = Pulumi.Random;
return await Deployment.RunAsync(() =>
{
var example = new Ionoscloud.Compute.Datacenter("example", new()
{
Name = "Datacenter Example",
Location = "us/las",
Description = "Datacenter Description",
SecAuthProtection = false,
});
var exampleIPBlock = new Ionoscloud.Compute.IPBlock("example", new()
{
Location = "us/las",
Size = 1,
Name = "IP Block Example",
});
var exampleLan = new Ionoscloud.Compute.Lan("example", new()
{
DatacenterId = example.Id,
Public = true,
Name = "Lan Example",
});
var serverImagePassword = new Random.Index.Password("server_image_password", new()
{
Length = 16,
Special = false,
});
var exampleServer = new Ionoscloud.Compute.Server("example", new()
{
Name = "Server Example",
DatacenterId = example.Id,
Cores = 1,
Ram = 1024,
AvailabilityZone = "ZONE_1",
CpuFamily = "INTEL_XEON",
ImageName = "Ubuntu-20.04",
ImagePassword = serverImagePassword.Result,
Volume = new Ionoscloud.Compute.Inputs.ServerVolumeArgs
{
Name = "system",
Size = 14,
DiskType = "SSD",
},
Nic = new Ionoscloud.Compute.Inputs.ServerNicArgs
{
Lan = 1,
Dhcp = true,
FirewallActive = true,
Ips = new[]
{
exampleIPBlock.Ips.Apply(ips => ips[0]),
},
},
});
var exampleIPFailover = new Ionoscloud.Compute.IPFailover("example", new()
{
DatacenterId = example.Id,
LanId = exampleLan.Id,
Ip = exampleIPBlock.Ips.Apply(ips => ips[0]),
Nicuuid = exampleServer.PrimaryNic,
}, new CustomResourceOptions
{
DependsOn =
{
exampleLan,
},
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.ionoscloud.compute.Datacenter;
import com.pulumi.ionoscloud.compute.DatacenterArgs;
import com.pulumi.ionoscloud.compute.IPBlock;
import com.pulumi.ionoscloud.compute.IPBlockArgs;
import com.pulumi.ionoscloud.compute.Lan;
import com.pulumi.ionoscloud.compute.LanArgs;
import com.pulumi.random.password;
import com.pulumi.random.PasswordArgs;
import com.pulumi.ionoscloud.compute.Server;
import com.pulumi.ionoscloud.compute.ServerArgs;
import com.pulumi.ionoscloud.compute.inputs.ServerVolumeArgs;
import com.pulumi.ionoscloud.compute.inputs.ServerNicArgs;
import com.pulumi.ionoscloud.compute.IPFailover;
import com.pulumi.ionoscloud.compute.IPFailoverArgs;
import com.pulumi.resources.CustomResourceOptions;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var example = new Datacenter("example", DatacenterArgs.builder()
.name("Datacenter Example")
.location("us/las")
.description("Datacenter Description")
.secAuthProtection(false)
.build());
var exampleIPBlock = new IPBlock("exampleIPBlock", IPBlockArgs.builder()
.location("us/las")
.size(1)
.name("IP Block Example")
.build());
var exampleLan = new Lan("exampleLan", LanArgs.builder()
.datacenterId(example.id())
.public_(true)
.name("Lan Example")
.build());
var serverImagePassword = new Password("serverImagePassword", PasswordArgs.builder()
.length(16)
.special(false)
.build());
var exampleServer = new Server("exampleServer", ServerArgs.builder()
.name("Server Example")
.datacenterId(example.id())
.cores(1)
.ram(1024)
.availabilityZone("ZONE_1")
.cpuFamily("INTEL_XEON")
.imageName("Ubuntu-20.04")
.imagePassword(serverImagePassword.result())
.volume(ServerVolumeArgs.builder()
.name("system")
.size(14)
.diskType("SSD")
.build())
.nic(ServerNicArgs.builder()
.lan("1")
.dhcp(true)
.firewallActive(true)
.ips(exampleIPBlock.ips().applyValue(ips -> ips[0]))
.build())
.build());
var exampleIPFailover = new IPFailover("exampleIPFailover", IPFailoverArgs.builder()
.datacenterId(example.id())
.lanId(exampleLan.id())
.ip(exampleIPBlock.ips().applyValue(ips -> ips[0]))
.nicuuid(exampleServer.primaryNic())
.build(), CustomResourceOptions.builder()
.dependsOn(exampleLan)
.build());
}
}
resources:
example:
type: ionoscloud:compute:Datacenter
properties:
name: Datacenter Example
location: us/las
description: Datacenter Description
secAuthProtection: false
exampleIPBlock:
type: ionoscloud:compute:IPBlock
name: example
properties:
location: us/las
size: 1
name: IP Block Example
exampleLan:
type: ionoscloud:compute:Lan
name: example
properties:
datacenterId: ${example.id}
public: true
name: Lan Example
exampleServer:
type: ionoscloud:compute:Server
name: example
properties:
name: Server Example
datacenterId: ${example.id}
cores: 1
ram: 1024
availabilityZone: ZONE_1
cpuFamily: INTEL_XEON
imageName: Ubuntu-20.04
imagePassword: ${serverImagePassword.result}
volume:
name: system
size: 14
diskType: SSD
nic:
lan: '1'
dhcp: true
firewallActive: true
ips:
- ${exampleIPBlock.ips[0]}
exampleIPFailover:
type: ionoscloud:compute:IPFailover
name: example
properties:
datacenterId: ${example.id}
lanId: ${exampleLan.id}
ip: ${exampleIPBlock.ips[0]}
nicuuid: ${exampleServer.primaryNic}
options:
dependsOn:
- ${exampleLan}
serverImagePassword:
type: random:password
name: server_image_password
properties:
length: 16
special: false
A note on multiple NICs on an IP Failover
If you want to add a secondary NIC to an IP Failover, follow these steps:
- Creating NIC A with failover IP on LAN 1
- Create NIC B unde the same LAN but with a different IP
- Create the IP Failover on LAN 1 with NIC A and failover IP of NIC A (A becomes now “master”, no slaves)
- Update NIC B IP to be the failover IP ( B becomes now a slave, A remains master)
After this you can create a new NIC C, NIC D and so on, in LAN 1, directly with the failover IP.
Please check examples for a full example with the above steps.
Create IPFailover Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new IPFailover(name: string, args: IPFailoverArgs, opts?: CustomResourceOptions);
@overload
def IPFailover(resource_name: str,
args: IPFailoverArgs,
opts: Optional[ResourceOptions] = None)
@overload
def IPFailover(resource_name: str,
opts: Optional[ResourceOptions] = None,
datacenter_id: Optional[str] = None,
ip: Optional[str] = None,
lan_id: Optional[str] = None,
nicuuid: Optional[str] = None)
func NewIPFailover(ctx *Context, name string, args IPFailoverArgs, opts ...ResourceOption) (*IPFailover, error)
public IPFailover(string name, IPFailoverArgs args, CustomResourceOptions? opts = null)
public IPFailover(String name, IPFailoverArgs args)
public IPFailover(String name, IPFailoverArgs args, CustomResourceOptions options)
type: ionoscloud:compute:IPFailover
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args IPFailoverArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args IPFailoverArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args IPFailoverArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args IPFailoverArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args IPFailoverArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var ipfailoverResource = new Ionoscloud.Compute.IPFailover("ipfailoverResource", new()
{
DatacenterId = "string",
Ip = "string",
LanId = "string",
Nicuuid = "string",
});
example, err := compute.NewIPFailover(ctx, "ipfailoverResource", &compute.IPFailoverArgs{
DatacenterId: pulumi.String("string"),
Ip: pulumi.String("string"),
LanId: pulumi.String("string"),
Nicuuid: pulumi.String("string"),
})
var ipfailoverResource = new IPFailover("ipfailoverResource", IPFailoverArgs.builder()
.datacenterId("string")
.ip("string")
.lanId("string")
.nicuuid("string")
.build());
ipfailover_resource = ionoscloud.compute.IPFailover("ipfailoverResource",
datacenter_id="string",
ip="string",
lan_id="string",
nicuuid="string")
const ipfailoverResource = new ionoscloud.compute.IPFailover("ipfailoverResource", {
datacenterId: "string",
ip: "string",
lanId: "string",
nicuuid: "string",
});
type: ionoscloud:compute:IPFailover
properties:
datacenterId: string
ip: string
lanId: string
nicuuid: string
IPFailover Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The IPFailover resource accepts the following input properties:
- Datacenter
Id string - [string] The ID of a Virtual Data Center.
- Ip string
- [string] The reserved IP address to be used in the IP failover group.
- Lan
Id string - [string] The ID of a LAN.
- Nicuuid string
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- Datacenter
Id string - [string] The ID of a Virtual Data Center.
- Ip string
- [string] The reserved IP address to be used in the IP failover group.
- Lan
Id string - [string] The ID of a LAN.
- Nicuuid string
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter
Id String - [string] The ID of a Virtual Data Center.
- ip String
- [string] The reserved IP address to be used in the IP failover group.
- lan
Id String - [string] The ID of a LAN.
- nicuuid String
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter
Id string - [string] The ID of a Virtual Data Center.
- ip string
- [string] The reserved IP address to be used in the IP failover group.
- lan
Id string - [string] The ID of a LAN.
- nicuuid string
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter_
id str - [string] The ID of a Virtual Data Center.
- ip str
- [string] The reserved IP address to be used in the IP failover group.
- lan_
id str - [string] The ID of a LAN.
- nicuuid str
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter
Id String - [string] The ID of a Virtual Data Center.
- ip String
- [string] The reserved IP address to be used in the IP failover group.
- lan
Id String - [string] The ID of a LAN.
- nicuuid String
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
Outputs
All input properties are implicitly available as output properties. Additionally, the IPFailover resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing IPFailover Resource
Get an existing IPFailover resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: IPFailoverState, opts?: CustomResourceOptions): IPFailover
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
datacenter_id: Optional[str] = None,
ip: Optional[str] = None,
lan_id: Optional[str] = None,
nicuuid: Optional[str] = None) -> IPFailover
func GetIPFailover(ctx *Context, name string, id IDInput, state *IPFailoverState, opts ...ResourceOption) (*IPFailover, error)
public static IPFailover Get(string name, Input<string> id, IPFailoverState? state, CustomResourceOptions? opts = null)
public static IPFailover get(String name, Output<String> id, IPFailoverState state, CustomResourceOptions options)
resources: _: type: ionoscloud:compute:IPFailover get: id: ${id}
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Datacenter
Id string - [string] The ID of a Virtual Data Center.
- Ip string
- [string] The reserved IP address to be used in the IP failover group.
- Lan
Id string - [string] The ID of a LAN.
- Nicuuid string
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- Datacenter
Id string - [string] The ID of a Virtual Data Center.
- Ip string
- [string] The reserved IP address to be used in the IP failover group.
- Lan
Id string - [string] The ID of a LAN.
- Nicuuid string
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter
Id String - [string] The ID of a Virtual Data Center.
- ip String
- [string] The reserved IP address to be used in the IP failover group.
- lan
Id String - [string] The ID of a LAN.
- nicuuid String
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter
Id string - [string] The ID of a Virtual Data Center.
- ip string
- [string] The reserved IP address to be used in the IP failover group.
- lan
Id string - [string] The ID of a LAN.
- nicuuid string
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter_
id str - [string] The ID of a Virtual Data Center.
- ip str
- [string] The reserved IP address to be used in the IP failover group.
- lan_
id str - [string] The ID of a LAN.
- nicuuid str
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
- datacenter
Id String - [string] The ID of a Virtual Data Center.
- ip String
- [string] The reserved IP address to be used in the IP failover group.
- lan
Id String - [string] The ID of a LAN.
- nicuuid String
[string] The ID of a NIC.
⚠ WARNING: Do not modify the IP for an IP failover group (that was provisioned via Pulumi) using the DCD, the API or other means because it may lead to unexpected behavior. If you provisioned an IP failover group using Pulumi, please use only Pulumi in order to manage the created IP failover group.
⚠ WARNING: For creating multiple IP failover groups at the same time, you can use one of the following options:
- Create multiple IP failover groups resources and use
depends_on
meta-argument to specify the order of creation, for example:
resource "ionoscloud_ipfailover" "firstexample" { datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
resource "ionoscloud_ipfailover" "secondexample" { depends_on = [ ionoscloud_ipfailover.firstexample ] datacenter_id = "datacenter ID" lan_id = "LAN ID" ip = "IP address" nicuuid = "NIC UUID" }
- Define the resources as presented above, but without using the
depends_on
meta-argument and run the apply command using-parallelism=1
as presented below:
pulumi up -parallelism=1
- Create multiple IP failover groups resources and use
Import
Resource IpFailover can be imported using the resource id
, e.g.
$ pulumi import ionoscloud:compute/iPFailover:IPFailover myipfailover datacenter uuid/lan uuid
To learn more about importing existing cloud resources, see Importing resources.
Package Details
- Repository
- ionoscloud ionos-cloud/pulumi-ionoscloud
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
ionoscloud
Terraform Provider.