Docs Home Pulumi IaC Pulumi ESC Pulumi Cloud Packages Tutorials
  1. Packages
  2. Bigip Provider
  3. API Docs
  4. EventServiceDiscovery
f5 BIG-IP v3.17.6 published on Monday, Oct 28, 2024 by Pulumi
pulumi/pulumi-f5bigip

f5bigip.EventServiceDiscovery

Explore with Pulumi AI

f5bigip logo
f5 BIG-IP v3.17.6 published on Monday, Oct 28, 2024 by Pulumi
pulumi/pulumi-f5bigip

    Example Usage

    import * as pulumi from "@pulumi/pulumi";
import * as f5bigip from "@pulumi/f5bigip";

const test = new f5bigip.EventServiceDiscovery("test", {
    taskid: "~Sample_event_sd~My_app~My_pool",
    nodes: [
        {
            id: "newNode1",
            ip: "192.168.2.3",
            port: 8080,
        },
        {
            id: "newNode2",
            ip: "192.168.2.4",
            port: 8080,
        },
    ],
});

    import pulumi
import pulumi_f5bigip as f5bigip

test = f5bigip.EventServiceDiscovery("test",
    taskid="~Sample_event_sd~My_app~My_pool",
    nodes=[
        {
            "id": "newNode1",
            "ip": "192.168.2.3",
            "port": 8080,
        },
        {
            "id": "newNode2",
            "ip": "192.168.2.4",
            "port": 8080,
        },
    ])

    package main

import (
	"github.com/pulumi/pulumi-f5bigip/sdk/v3/go/f5bigip"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)

func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := f5bigip.NewEventServiceDiscovery(ctx, "test", &f5bigip.EventServiceDiscoveryArgs{
			Taskid: pulumi.String("~Sample_event_sd~My_app~My_pool"),
			Nodes: f5bigip.EventServiceDiscoveryNodeArray{
				&f5bigip.EventServiceDiscoveryNodeArgs{
					Id:   pulumi.String("newNode1"),
					Ip:   pulumi.String("192.168.2.3"),
					Port: pulumi.Int(8080),
				},
				&f5bigip.EventServiceDiscoveryNodeArgs{
					Id:   pulumi.String("newNode2"),
					Ip:   pulumi.String("192.168.2.4"),
					Port: pulumi.Int(8080),
				},
			},
		})
		if err != nil {
			return err
		}
		return nil
	})
}

    using System.Collections.Generic;
using System.Linq;
using Pulumi;
using F5BigIP = Pulumi.F5BigIP;

return await Deployment.RunAsync(() => 
{
    var test = new F5BigIP.EventServiceDiscovery("test", new()
    {
        Taskid = "~Sample_event_sd~My_app~My_pool",
        Nodes = new[]
        {
            new F5BigIP.Inputs.EventServiceDiscoveryNodeArgs
            {
                Id = "newNode1",
                Ip = "192.168.2.3",
                Port = 8080,
            },
            new F5BigIP.Inputs.EventServiceDiscoveryNodeArgs
            {
                Id = "newNode2",
                Ip = "192.168.2.4",
                Port = 8080,
            },
        },
    });

});

    package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.f5bigip.EventServiceDiscovery;
import com.pulumi.f5bigip.EventServiceDiscoveryArgs;
import com.pulumi.f5bigip.inputs.EventServiceDiscoveryNodeArgs;
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 test = new EventServiceDiscovery("test", EventServiceDiscoveryArgs.builder()
            .taskid("~Sample_event_sd~My_app~My_pool")
            .nodes(            
                EventServiceDiscoveryNodeArgs.builder()
                    .id("newNode1")
                    .ip("192.168.2.3")
                    .port(8080)
                    .build(),
                EventServiceDiscoveryNodeArgs.builder()
                    .id("newNode2")
                    .ip("192.168.2.4")
                    .port(8080)
                    .build())
            .build());

    }
}

    resources:
  test:
    type: f5bigip:EventServiceDiscovery
    properties:
      taskid: ~Sample_event_sd~My_app~My_pool
      nodes:
        - id: newNode1
          ip: 192.168.2.3
          port: 8080
        - id: newNode2
          ip: 192.168.2.4
          port: 8080

    Create EventServiceDiscovery Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new EventServiceDiscovery(name: string, args: EventServiceDiscoveryArgs, opts?: CustomResourceOptions);
    @overload
def EventServiceDiscovery(resource_name: str,
                          args: EventServiceDiscoveryArgs,
                          opts: Optional[ResourceOptions] = None)

@overload
def EventServiceDiscovery(resource_name: str,
                          opts: Optional[ResourceOptions] = None,
                          taskid: Optional[str] = None,
                          nodes: Optional[Sequence[EventServiceDiscoveryNodeArgs]] = None)
    func NewEventServiceDiscovery(ctx *Context, name string, args EventServiceDiscoveryArgs, opts ...ResourceOption) (*EventServiceDiscovery, error)
    public EventServiceDiscovery(string name, EventServiceDiscoveryArgs args, CustomResourceOptions? opts = null)
    public EventServiceDiscovery(String name, EventServiceDiscoveryArgs args)
public EventServiceDiscovery(String name, EventServiceDiscoveryArgs args, CustomResourceOptions options)

    type: f5bigip:EventServiceDiscovery
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 EventServiceDiscoveryArgs
    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 EventServiceDiscoveryArgs
    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 EventServiceDiscoveryArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args EventServiceDiscoveryArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args EventServiceDiscoveryArgs
    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 eventServiceDiscoveryResource = new F5BigIP.EventServiceDiscovery("eventServiceDiscoveryResource", new()
{
    Taskid = "string",
    Nodes = new[]
    {
        new F5BigIP.Inputs.EventServiceDiscoveryNodeArgs
        {
            Id = "string",
            Ip = "string",
            Port = 0,
        },
    },
});

    example, err := f5bigip.NewEventServiceDiscovery(ctx, "eventServiceDiscoveryResource", &f5bigip.EventServiceDiscoveryArgs{
	Taskid: pulumi.String("string"),
	Nodes: f5bigip.EventServiceDiscoveryNodeArray{
		&f5bigip.EventServiceDiscoveryNodeArgs{
			Id:   pulumi.String("string"),
			Ip:   pulumi.String("string"),
			Port: pulumi.Int(0),
		},
	},
})

    var eventServiceDiscoveryResource = new EventServiceDiscovery("eventServiceDiscoveryResource", EventServiceDiscoveryArgs.builder()
    .taskid("string")
    .nodes(EventServiceDiscoveryNodeArgs.builder()
        .id("string")
        .ip("string")
        .port(0)
        .build())
    .build());

    event_service_discovery_resource = f5bigip.EventServiceDiscovery("eventServiceDiscoveryResource",
    taskid="string",
    nodes=[{
        "id": "string",
        "ip": "string",
        "port": 0,
    }])

    const eventServiceDiscoveryResource = new f5bigip.EventServiceDiscovery("eventServiceDiscoveryResource", {
    taskid: "string",
    nodes: [{
        id: "string",
        ip: "string",
        port: 0,
    }],
});

    type: f5bigip:EventServiceDiscovery
properties:
    nodes:
        - id: string
          ip: string
          port: 0
    taskid: string

    EventServiceDiscovery 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 EventServiceDiscovery resource accepts the following input properties:

    Taskid string
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    Nodes List<Pulumi.F5BigIP.Inputs.EventServiceDiscoveryNode>

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    Taskid string
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    Nodes []EventServiceDiscoveryNodeArgs

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid String
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes List<EventServiceDiscoveryNode>

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid string
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes EventServiceDiscoveryNode[]

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid str
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes Sequence[EventServiceDiscoveryNodeArgs]

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid String
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes List<Property Map>

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    Outputs

    All input properties are implicitly available as output properties. Additionally, the EventServiceDiscovery 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 EventServiceDiscovery Resource

    Get an existing EventServiceDiscovery 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?: EventServiceDiscoveryState, opts?: CustomResourceOptions): EventServiceDiscovery
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        nodes: Optional[Sequence[EventServiceDiscoveryNodeArgs]] = None,
        taskid: Optional[str] = None) -> EventServiceDiscovery
    func GetEventServiceDiscovery(ctx *Context, name string, id IDInput, state *EventServiceDiscoveryState, opts ...ResourceOption) (*EventServiceDiscovery, error)
    public static EventServiceDiscovery Get(string name, Input<string> id, EventServiceDiscoveryState? state, CustomResourceOptions? opts = null)
    public static EventServiceDiscovery get(String name, Output<String> id, EventServiceDiscoveryState state, CustomResourceOptions options)
    Resource lookup is not supported in YAML
    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.
    The following state arguments are supported:
    Nodes List<Pulumi.F5BigIP.Inputs.EventServiceDiscoveryNode>

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    Taskid string
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    Nodes []EventServiceDiscoveryNodeArgs

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    Taskid string
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes List<EventServiceDiscoveryNode>

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid String
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes EventServiceDiscoveryNode[]

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid string
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes Sequence[EventServiceDiscoveryNodeArgs]

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid str
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )
    nodes List<Property Map>

    Map of node which will be added to pool which will be having node name(id),node address(ip) and node port(port)

    For more information, please refer below document https://clouddocs.f5.com/products/extensions/f5-appsvcs-extension/latest/declarations/discovery.html?highlight=service%20discovery#event-driven-service-discovery

    Below example shows how to use event-driven service discovery, introduced in AS3 3.9.0.

    With event-driven service discovery, you POST a declaration with the addressDiscovery property set to event. This creates a new endpoint which you can use to add nodes that does not require an AS3 declaration, so it can be more efficient than using PATCH or POST to add nodes.

    When you use the event value for addressDiscovery, the system creates the new endpoint with the following syntax: https:///mgmt/shared/service-discovery/task/~~~/nodes.

    For example, in the following declaration, assuming 192.0.2.14 is our BIG-IP, the endpoint that is created is: https://192.0.2.14/mgmt/shared/service-discovery/task/~Sample_event_sd~My_app~My_pool/nodes

    Once the endpoint is created( taskid ), you can use it to add nodes to the BIG-IP pool First we show the initial declaration to POST to the BIG-IP system.

    { "class": "ADC", "schemaVersion": "3.9.0", "id": "Pool", "Sample_event_sd": { "class": "Tenant", "My_app": { "class": "Application", "My_pool": { "class": "Pool", "members": [ { "servicePort": 8080, "addressDiscovery": "static", "serverAddresses": [ "192.0.2.2" ] }, { "servicePort": 8080, "addressDiscovery": "event" } ] } } } }

    Once the declaration has been sent to the BIG-IP, we can use taskid/id ( ~Sample_event_sd~My_app~My_pool" ) and node list for the resource to dynamically update the node list.

    taskid String
    servicediscovery endpoint ( Below example shows how to create endpoing using AS3 )

    Supporting Types

    EventServiceDiscoveryNode, EventServiceDiscoveryNodeArgs

    Id string
    name of node
    Ip string
    ip of nonde
    Port int
    port
    Id string
    name of node
    Ip string
    ip of nonde
    Port int
    port
    id String
    name of node
    ip String
    ip of nonde
    port Integer
    port
    id string
    name of node
    ip string
    ip of nonde
    port number
    port
    id str
    name of node
    ip str
    ip of nonde
    port int
    port
    id String
    name of node
    ip String
    ip of nonde
    port Number
    port

    Package Details

    Repository
    f5 BIG-IP pulumi/pulumi-f5bigip
    License
    Apache-2.0
    Notes
    This Pulumi package is based on the bigip Terraform Provider.
    f5bigip logo
    f5 BIG-IP v3.17.6 published on Monday, Oct 28, 2024 by Pulumi
    pulumi/pulumi-f5bigip