NodeBalancerConfig
Provides a Linode NodeBalancer Config resource. This can be used to create, modify, and delete Linodes NodeBalancer Configs. For more information, see Getting Started with NodeBalancers and the Linode APIv4 docs.
Attributes
This resource exports the following attributes:
ssl_commonname- The common name for the SSL certification this port is serving if this port is not configured to use SSL.ssl_fingerprint- The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.node_status_up- The number of backends considered to be ‘UP’ and healthy, and that are serving requests.node_status_down- The number of backends considered to be ‘DOWN’ and unhealthy. These are not in rotation, and not serving requests.
Example Usage
using Pulumi;
using Linode = Pulumi.Linode;
class MyStack : Stack
{
public MyStack()
{
var foobar = new Linode.NodeBalancer("foobar", new Linode.NodeBalancerArgs
{
ClientConnThrottle = 20,
Label = "mynodebalancer",
Region = "us-east",
});
var foofig = new Linode.NodeBalancerConfig("foofig", new Linode.NodeBalancerConfigArgs
{
Algorithm = "source",
Check = "http",
CheckAttempts = 3,
CheckPath = "/foo",
CheckTimeout = 30,
NodebalancerId = foobar.Id,
Port = 8088,
Protocol = "http",
Stickiness = "http_cookie",
});
}
}
Coming soon!
import pulumi
import pulumi_linode as linode
foobar = linode.NodeBalancer("foobar",
client_conn_throttle=20,
label="mynodebalancer",
region="us-east")
foofig = linode.NodeBalancerConfig("foofig",
algorithm="source",
check="http",
check_attempts=3,
check_path="/foo",
check_timeout=30,
nodebalancer_id=foobar.id,
port=8088,
protocol="http",
stickiness="http_cookie")import * as pulumi from "@pulumi/pulumi";
import * as linode from "@pulumi/linode";
const foobar = new linode.NodeBalancer("foobar", {
clientConnThrottle: 20,
label: "mynodebalancer",
region: "us-east",
});
const foofig = new linode.NodeBalancerConfig("foofig", {
algorithm: "source",
check: "http",
checkAttempts: 3,
checkPath: "/foo",
checkTimeout: 30,
nodebalancerId: foobar.id.apply(id => Number.parseFloat(id)),
port: 8088,
protocol: "http",
stickiness: "http_cookie",
});Create a NodeBalancerConfig Resource
new NodeBalancerConfig(name: string, args: NodeBalancerConfigArgs, opts?: CustomResourceOptions);def NodeBalancerConfig(resource_name, opts=None, algorithm=None, check=None, check_attempts=None, check_body=None, check_interval=None, check_passive=None, check_path=None, check_timeout=None, cipher_suite=None, nodebalancer_id=None, port=None, protocol=None, ssl_cert=None, ssl_key=None, stickiness=None, __props__=None);func NewNodeBalancerConfig(ctx *Context, name string, args NodeBalancerConfigArgs, opts ...ResourceOption) (*NodeBalancerConfig, error)public NodeBalancerConfig(string name, NodeBalancerConfigArgs args, CustomResourceOptions? opts = null)- name string
- The unique name of the resource.
- args NodeBalancerConfigArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- opts ResourceOptions
- A bag of options that control this resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args NodeBalancerConfigArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args NodeBalancerConfigArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
NodeBalancerConfig Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Programming Model docs.
Inputs
The NodeBalancerConfig resource accepts the following input properties:
- Nodebalancer
Id int The ID of the NodeBalancer to access.
- Algorithm string
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- Check string
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- Check
Attempts int How many times to attempt a check before considering a backend to be down. (1-30)
- Check
Body string This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- Check
Interval int How often, in seconds, to check that backends are up and serving requests.
- Check
Passive bool If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- Check
Path string The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- Check
Timeout int How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- Cipher
Suite string What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- Port int
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- Protocol string
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- Ssl
Cert string The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Ssl
Key string The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Stickiness string
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
- Nodebalancer
Id int The ID of the NodeBalancer to access.
- Algorithm string
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- Check string
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- Check
Attempts int How many times to attempt a check before considering a backend to be down. (1-30)
- Check
Body string This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- Check
Interval int How often, in seconds, to check that backends are up and serving requests.
- Check
Passive bool If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- Check
Path string The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- Check
Timeout int How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- Cipher
Suite string What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- Port int
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- Protocol string
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- Ssl
Cert string The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Ssl
Key string The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Stickiness string
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
- nodebalancer
Id number The ID of the NodeBalancer to access.
- algorithm string
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- check string
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- check
Attempts number How many times to attempt a check before considering a backend to be down. (1-30)
- check
Body string This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- check
Interval number How often, in seconds, to check that backends are up and serving requests.
- check
Passive boolean If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- check
Path string The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- check
Timeout number How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- cipher
Suite string What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- port number
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- protocol string
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- ssl
Cert string The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- ssl
Key string The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- stickiness string
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
- nodebalancer_
id float The ID of the NodeBalancer to access.
- algorithm str
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- check str
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- check_
attempts float How many times to attempt a check before considering a backend to be down. (1-30)
- check_
body str This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- check_
interval float How often, in seconds, to check that backends are up and serving requests.
- check_
passive bool If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- check_
path str The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- check_
timeout float How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- cipher_
suite str What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- port float
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- protocol str
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- ssl_
cert str The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- ssl_
key str The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- stickiness str
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
Outputs
All input properties are implicitly available as output properties. Additionally, the NodeBalancerConfig resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Node
Status NodeBalancer Config Node Status - Ssl
Commonname string The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- Ssl
Fingerprint string The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- Id string
- The provider-assigned unique ID for this managed resource.
- Node
Status NodeBalancer Config Node Status - Ssl
Commonname string The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- Ssl
Fingerprint string The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- id string
- The provider-assigned unique ID for this managed resource.
- node
Status NodeBalancer Config Node Status - ssl
Commonname string The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- ssl
Fingerprint string The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- id str
- The provider-assigned unique ID for this managed resource.
- node_
status Dict[NodeBalancer Config Node Status] - ssl_
commonname str The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- ssl_
fingerprint str The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
Look up an Existing NodeBalancerConfig Resource
Get an existing NodeBalancerConfig 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?: NodeBalancerConfigState, opts?: CustomResourceOptions): NodeBalancerConfigstatic get(resource_name, id, opts=None, algorithm=None, check=None, check_attempts=None, check_body=None, check_interval=None, check_passive=None, check_path=None, check_timeout=None, cipher_suite=None, node_status=None, nodebalancer_id=None, port=None, protocol=None, ssl_cert=None, ssl_commonname=None, ssl_fingerprint=None, ssl_key=None, stickiness=None, __props__=None);func GetNodeBalancerConfig(ctx *Context, name string, id IDInput, state *NodeBalancerConfigState, opts ...ResourceOption) (*NodeBalancerConfig, error)public static NodeBalancerConfig Get(string name, Input<string> id, NodeBalancerConfigState? state, CustomResourceOptions? opts = null)- 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.
The following state arguments are supported:
- Algorithm string
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- Check string
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- Check
Attempts int How many times to attempt a check before considering a backend to be down. (1-30)
- Check
Body string This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- Check
Interval int How often, in seconds, to check that backends are up and serving requests.
- Check
Passive bool If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- Check
Path string The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- Check
Timeout int How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- Cipher
Suite string What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- Node
Status NodeBalancer Config Node Status Args - Nodebalancer
Id int The ID of the NodeBalancer to access.
- Port int
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- Protocol string
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- Ssl
Cert string The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Ssl
Commonname string The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- Ssl
Fingerprint string The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- Ssl
Key string The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Stickiness string
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
- Algorithm string
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- Check string
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- Check
Attempts int How many times to attempt a check before considering a backend to be down. (1-30)
- Check
Body string This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- Check
Interval int How often, in seconds, to check that backends are up and serving requests.
- Check
Passive bool If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- Check
Path string The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- Check
Timeout int How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- Cipher
Suite string What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- Node
Status NodeBalancer Config Node Status - Nodebalancer
Id int The ID of the NodeBalancer to access.
- Port int
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- Protocol string
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- Ssl
Cert string The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Ssl
Commonname string The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- Ssl
Fingerprint string The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- Ssl
Key string The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- Stickiness string
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
- algorithm string
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- check string
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- check
Attempts number How many times to attempt a check before considering a backend to be down. (1-30)
- check
Body string This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- check
Interval number How often, in seconds, to check that backends are up and serving requests.
- check
Passive boolean If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- check
Path string The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- check
Timeout number How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- cipher
Suite string What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- node
Status NodeBalancer Config Node Status - nodebalancer
Id number The ID of the NodeBalancer to access.
- port number
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- protocol string
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- ssl
Cert string The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- ssl
Commonname string The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- ssl
Fingerprint string The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- ssl
Key string The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- stickiness string
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
- algorithm str
What algorithm this NodeBalancer should use for routing traffic to backends: roundrobin, leastconn, source
- check str
The type of check to perform against backends to ensure they are serving requests. This is used to determine if backends are up or down. If none no check is performed. connection requires only a connection to the backend to succeed. http and http_body rely on the backend serving HTTP, and that the response returned matches what is expected.
- check_
attempts float How many times to attempt a check before considering a backend to be down. (1-30)
- check_
body str This value must be present in the response body of the check in order for it to pass. If this value is not present in the response body of a check request, the backend is considered to be down
- check_
interval float How often, in seconds, to check that backends are up and serving requests.
- check_
passive bool If true, any response from this backend with a 5xx status code will be enough for it to be considered unhealthy and taken out of rotation.
- check_
path str The URL path to check on each backend. If the backend does not respond to this request it is considered to be down.
- check_
timeout float How long, in seconds, to wait for a check attempt before considering it failed. (1-30)
- cipher_
suite str What ciphers to use for SSL connections served by this NodeBalancer.
legacyis considered insecure and should only be used if necessary.- node_
status Dict[NodeBalancer Config Node Status] - nodebalancer_
id float The ID of the NodeBalancer to access.
- port float
The TCP port this Config is for. These values must be unique across configs on a single NodeBalancer (you can’t have two configs for port 80, for example). While some ports imply some protocols, no enforcement is done and you may configure your NodeBalancer however is useful to you. For example, while port 443 is generally used for HTTPS, you do not need SSL configured to have a NodeBalancer listening on port 443. (Defaults to 80)
- protocol str
The protocol this port is configured to serve. If this is set to https you must include an ssl_cert and an ssl_key. (Defaults to “http”)
- ssl_
cert str The certificate this port is serving. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- ssl_
commonname str The common name for the SSL certification this port is serving if this port is not configured to use SSL.
- ssl_
fingerprint str The fingerprint for the SSL certification this port is serving if this port is not configured to use SSL.
- ssl_
key str The private key corresponding to this port’s certificate. This is not returned. If set, this field will come back as
<REDACTED>. Please use the ssl_commonname and ssl_fingerprint to identify the certificate.- stickiness str
Controls how session stickiness is handled on this port: ‘none’, ‘table’, ‘http_cookie’
Supporting Types
NodeBalancerConfigNodeStatus
See the output API doc for this type.
See the output API doc for this type.
See the output API doc for this type.
Package Details
- Repository
- https://github.com/pulumi/pulumi-linode
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
linodeTerraform Provider.