Merge pull request #13509 from hashicorp/sethvargo/syntax
Update syntax on some providers
This commit is contained in:
commit
5f4b98866d
|
@ -16,12 +16,12 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the Chef provider
|
||||
provider "chef" {
|
||||
server_url = "https://api.chef.io/organizations/example/"
|
||||
|
||||
// You can set up a "Client" within the Chef Server management console.
|
||||
# You can set up a "Client" within the Chef Server management console.
|
||||
client_name = "terraform"
|
||||
key_material = "${file("chef-terraform.pem")}"
|
||||
}
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates and manages a data bag in Chef Server.
|
||||
---
|
||||
|
||||
# chef\_data\_bag
|
||||
# chef_data_bag
|
||||
|
||||
A [data bag](http://docs.chef.io/data_bags.html) is a collection of
|
||||
configuration objects that are stored as JSON in Chef Server and can be
|
||||
|
@ -17,7 +17,7 @@ of items which can be created using the ``chef_data_bag_item`` resource.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "chef_data_bag" "example" {
|
||||
name = "example-data-bag"
|
||||
}
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates and manages an object within a data bag in Chef Server.
|
||||
---
|
||||
|
||||
# chef\_data\_bag\_item
|
||||
# chef_data_bag_item
|
||||
|
||||
A [data bag](http://docs.chef.io/data_bags.html) is a collection of
|
||||
configuration objects that are stored as JSON in Chef Server and can be
|
||||
|
@ -17,7 +17,7 @@ data bag itself, use the ``chef_data_bag`` resource.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "chef_data_bag_item" "example" {
|
||||
data_bag_name = "example-data-bag"
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates and manages an environment in Chef Server.
|
||||
---
|
||||
|
||||
# chef\_environment
|
||||
# chef_environment
|
||||
|
||||
An [environment](http://docs.chef.io/environments.html) is a container for
|
||||
Chef nodes that share a set of attribute values and may have a set of version
|
||||
|
@ -14,7 +14,7 @@ constraints for which cookbook versions may be used on its nodes.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "chef_environment" "example" {
|
||||
name = "example-environment"
|
||||
}
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates and manages a node in Chef Server.
|
||||
---
|
||||
|
||||
# chef\_node
|
||||
# chef_node
|
||||
|
||||
A [node](http://docs.chef.io/nodes.html) is a computer whose
|
||||
configuration is managed by Chef.
|
||||
|
@ -19,7 +19,7 @@ Chef server.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "chef_node" "example" {
|
||||
name = "example-environment"
|
||||
environment_name = "${chef_environment.example.name}"
|
||||
|
|
|
@ -13,7 +13,7 @@ that can apply across multiple nodes that perform the same function.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "chef_role" "example" {
|
||||
name = "example-role"
|
||||
run_list = ["recipe[example]"]
|
||||
|
|
|
@ -20,7 +20,7 @@ about a specific Circonus Account.
|
|||
The following example shows how the resource might be used to obtain the metrics
|
||||
usage and limit of a given Circonus Account.
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "circonus_account" "current" {
|
||||
current = true
|
||||
}
|
||||
|
@ -79,4 +79,3 @@ The following attributes are exported:
|
|||
* `users` - A list of users who have access to this account. Each element in
|
||||
the list has both an `id` and a `role`. The `id` is a Circonus ID referencing
|
||||
the user.
|
||||
|
||||
|
|
|
@ -29,7 +29,7 @@ either pulls or has metrics pushed into it and funneled back through Circonus.
|
|||
The following example shows how the resource might be used to obtain
|
||||
the name of the Circonus Collector configured on the provider.
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "circonus_collector" "ashburn" {
|
||||
id = "/broker/1"
|
||||
}
|
||||
|
|
|
@ -14,9 +14,9 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "circonus" {
|
||||
key = "b8fec159-f9e5-4fe6-ad2c-dc1ec6751586"
|
||||
key = "b8fec159-f9e5-4fe6-ad2c-dc1ec6751586"
|
||||
}
|
||||
```
|
||||
|
||||
|
|
|
@ -20,7 +20,7 @@ underlying Circonus API.
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
variable api_token {
|
||||
default = "my-token"
|
||||
}
|
||||
|
@ -202,7 +202,7 @@ either `60s` or `300s` for CloudWatch metrics.
|
|||
|
||||
Example CloudWatch check (partial metrics collection):
|
||||
|
||||
```
|
||||
```hcl
|
||||
variable "cloudwatch_rds_tags" {
|
||||
type = "list"
|
||||
default = [
|
||||
|
@ -336,7 +336,7 @@ check also returns a set of metrics that are a variant of:
|
|||
|
||||
Example Consul check (partial metrics collection):
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "circonus_check" "consul_server" {
|
||||
active = true
|
||||
name = "%s"
|
||||
|
@ -579,7 +579,7 @@ for additional details.
|
|||
|
||||
Sample `tcp` check:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "circonus_check" "tcp_check" {
|
||||
name = "TCP and TLS check"
|
||||
notes = "Obtains the connect time and TTL for the TLS cert"
|
||||
|
@ -643,7 +643,7 @@ resource "circonus_check" "tcp_check" {
|
|||
Terraform (and that the referenced [`circonus_metric`](metric.html) has already
|
||||
been imported):
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "circonus" {
|
||||
alias = "b8fec159-f9e5-4fe6-ad2c-dc1ec6751586"
|
||||
}
|
||||
|
|
|
@ -14,7 +14,7 @@ The ``circonus_contact_group`` resource creates and manages a
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "circonus_contact_group" "myteam-alerts" {
|
||||
name = "MyTeam Alerts"
|
||||
|
||||
|
@ -259,7 +259,7 @@ Either an `address` or `user` attribute is required.
|
|||
`circonus_contact_group` supports importing resources. Supposing the following
|
||||
Terraform:
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "circonus" {
|
||||
alias = "b8fec159-f9e5-4fe6-ad2c-dc1ec6751586"
|
||||
}
|
||||
|
|
|
@ -15,35 +15,35 @@ https://login.circonus.com/resources/api/calls/graph).
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
variable "myapp-tags" {
|
||||
type = "list"
|
||||
type = "list"
|
||||
default = [ "app:myapp", "owner:myteam" ]
|
||||
}
|
||||
|
||||
resource "circonus_graph" "latency-graph" {
|
||||
name = "Latency Graph"
|
||||
name = "Latency Graph"
|
||||
description = "A sample graph showing off two data points"
|
||||
notes = "Misc notes about this graph"
|
||||
notes = "Misc notes about this graph"
|
||||
graph_style = "line"
|
||||
line_style = "stepped"
|
||||
line_style = "stepped"
|
||||
|
||||
metric {
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
metric_name = "maximum"
|
||||
metric_type = "numeric"
|
||||
name = "Maximum Latency"
|
||||
axis = "left"
|
||||
color = "#657aa6"
|
||||
name = "Maximum Latency"
|
||||
axis = "left"
|
||||
color = "#657aa6"
|
||||
}
|
||||
|
||||
metric {
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
metric_name = "minimum"
|
||||
metric_type = "numeric"
|
||||
name = "Minimum Latency"
|
||||
axis = "right"
|
||||
color = "#0000ff"
|
||||
name = "Minimum Latency"
|
||||
axis = "right"
|
||||
color = "#0000ff"
|
||||
}
|
||||
|
||||
tags = [ "${var.myapp-tags}" ]
|
||||
|
@ -151,18 +151,18 @@ set to the graph rendering engine.
|
|||
Terraform (and that the referenced [`circonus_metric`](metric.html)
|
||||
and [`circonus_check`](check.html) have already been imported):
|
||||
|
||||
```
|
||||
```text
|
||||
resource "circonus_graph" "icmp-graph" {
|
||||
name = "Test graph"
|
||||
name = "Test graph"
|
||||
graph_style = "line"
|
||||
line_style = "stepped"
|
||||
line_style = "stepped"
|
||||
|
||||
metric {
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
metric_name = "maximum"
|
||||
metric_type = "numeric"
|
||||
name = "Maximum Latency"
|
||||
axis = "left"
|
||||
name = "Maximum Latency"
|
||||
axis = "left"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
|
|
@ -15,10 +15,10 @@ created.
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "circonus_metric" "used" {
|
||||
name = "_usage`0`_used"
|
||||
type = "numeric"
|
||||
name = "_usage`0`_used"
|
||||
type = "numeric"
|
||||
units = "qty"
|
||||
|
||||
tags = {
|
||||
|
@ -49,7 +49,7 @@ resource "circonus_metric" "used" {
|
|||
`circonus_metric` supports importing resources. Supposing the following
|
||||
Terraform:
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "circonus" {
|
||||
alias = "b8fec159-f9e5-4fe6-ad2c-dc1ec6751586"
|
||||
}
|
||||
|
|
|
@ -13,7 +13,7 @@ The ``circonus_metric_cluster`` resource creates and manages a
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "circonus_metric_cluster" "nomad-job-memory-rss" {
|
||||
name = "My Job's Resident Memory"
|
||||
description = <<-EOF
|
||||
|
@ -59,7 +59,7 @@ EOF
|
|||
`circonus_metric_cluster` supports importing resources. Supposing the following
|
||||
Terraform:
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "circonus" {
|
||||
alias = "b8fec159-f9e5-4fe6-ad2c-dc1ec6751586"
|
||||
}
|
||||
|
|
|
@ -13,16 +13,16 @@ The ``circonus_rule_set`` resource creates and manages a
|
|||
|
||||
## Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
variable "myapp-tags" {
|
||||
type = "list"
|
||||
type = "list"
|
||||
default = [ "app:myapp", "owner:myteam" ]
|
||||
}
|
||||
|
||||
resource "circonus_rule_set" "myapp-cert-ttl-alert" {
|
||||
check = "${circonus_check.myapp-https.checks[0]}"
|
||||
check = "${circonus_check.myapp-https.checks[0]}"
|
||||
metric_name = "cert_end_in"
|
||||
link = "https://wiki.example.org/playbook/how-to-renew-cert"
|
||||
link = "https://wiki.example.org/playbook/how-to-renew-cert"
|
||||
|
||||
if {
|
||||
value {
|
||||
|
@ -106,7 +106,7 @@ resource "circonus_rule_set" "myapp-healthy-alert" {
|
|||
# average over the last 10min. Any transient problems should have
|
||||
# resolved themselves by now. Something's wrong, need to page someone.
|
||||
over {
|
||||
last = "10m"
|
||||
last = "10m"
|
||||
using = "average"
|
||||
}
|
||||
max_value = "500"
|
||||
|
@ -127,7 +127,7 @@ resource "circonus_rule_set" "myapp-healthy-alert" {
|
|||
}
|
||||
|
||||
then {
|
||||
notify = [ "${circonus_contact_group.myapp-owners.id}" ]
|
||||
notify = [ "${circonus_contact_group.myapp-owners.id}" ]
|
||||
severity = 3
|
||||
}
|
||||
}
|
||||
|
@ -331,7 +331,7 @@ A `then` block can have the following attributes:
|
|||
Terraform (and that the referenced [`circonus_metric`](metric.html)
|
||||
and [`circonus_check`](check.html) have already been imported):
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "circonus_rule_set" "icmp-latency-alert" {
|
||||
check = "${circonus_check.api_latency.checks[0]}"
|
||||
metric_name = "maximum"
|
||||
|
|
|
@ -20,7 +20,7 @@ For additional documentation, see the [CLC Developer Center](https://www.ctl.io/
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the CLC Provider
|
||||
provider "clc" {
|
||||
username = "${var.clc_username}"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Manages a CLC server group.
|
||||
---
|
||||
|
||||
# clc\_group
|
||||
# clc_group
|
||||
|
||||
Manages a CLC server group. Either provisions or resolves to an existing group.
|
||||
|
||||
|
@ -14,7 +14,7 @@ See also [Complete API documentation](https://www.ctl.io/api-docs/v2/#groups).
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Provision/Resolve a server group
|
||||
resource "clc_group" "frontends" {
|
||||
location_id = "WA1"
|
||||
|
@ -51,4 +51,3 @@ up in advance. Each `custom_fields` block supports the following:
|
|||
|
||||
* `id` - (Required, string) The ID of the custom field to set.
|
||||
* `value` - (Required, string) The value for the specified field.
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Manages a CLC load balacner.
|
||||
---
|
||||
|
||||
# clc\_load\_balancer
|
||||
# clc_load_balancer
|
||||
|
||||
Manages a CLC load balancer. Manage connected backends with [clc_load_balancer_pool](load_balancer_pool.html)
|
||||
|
||||
|
@ -14,8 +14,7 @@ See also [Complete API documentation](https://www.ctl.io/api-docs/v2/#shared-loa
|
|||
|
||||
## Example Usage
|
||||
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Provision a load balancer
|
||||
resource "clc_load_balancer" "api" {
|
||||
data_center = "${clc_group.frontends.location_id}"
|
||||
|
@ -38,8 +37,3 @@ The following arguments are supported:
|
|||
* `data_center` - (Required, string) The datacenter location of both parent group and this group.
|
||||
* `status` - (Required, string) Either "enabled" or "disabled"
|
||||
* `description` - (Optional, string) Description for server group (visible in control portal only)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Manages a CLC load balancer pool.
|
||||
---
|
||||
|
||||
# clc\_load\_balancer\_pool
|
||||
# clc_load_balancer_pool
|
||||
|
||||
Manages a CLC load balancer pool. Manage related frontend with [clc_load_balancer](load_balancer.html)
|
||||
|
||||
|
@ -15,7 +15,7 @@ See also [Complete API documentation](https://www.ctl.io/api-docs/v2/#shared-loa
|
|||
## Example Usage
|
||||
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Provision a load balancer pool
|
||||
resource "clc_load_balancer_pool" "pool" {
|
||||
data_center = "${clc_group.frontends.location_id}"
|
||||
|
@ -68,9 +68,3 @@ following:
|
|||
* `ipAddress` (Required, string) The destination internal ip of pool node.
|
||||
* `privatePort` (Required, int) The destination port on the pool node.
|
||||
* `status` (Optional, string) Either "enabled" or "disabled".
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Manages a CLC public ip.
|
||||
---
|
||||
|
||||
# clc\_public\_ip
|
||||
# clc_public_ip
|
||||
|
||||
Manages a CLC public ip (for an existing server).
|
||||
|
||||
|
@ -14,7 +14,7 @@ See also [Complete API documentation](https://www.ctl.io/api-docs/v2/#public-ip)
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Provision a public ip
|
||||
resource "clc_public_ip" "backdoor" {
|
||||
server_id = "${clc_server.node.0.id}"
|
||||
|
@ -79,7 +79,3 @@ repeated to restrict ingress traffic on specified CIDR blocks. Each
|
|||
`source_restrictions` block supports the following:
|
||||
|
||||
* `cidr` (Required, string) The IP or range of IPs in CIDR notation.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Manages the lifecycle of a CLC server.
|
||||
---
|
||||
|
||||
# clc\_server
|
||||
# clc_server
|
||||
|
||||
Manages a CLC server.
|
||||
|
||||
|
@ -19,7 +19,7 @@ Resources and Documentation:
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Provision a server
|
||||
resource "clc_server" "node" {
|
||||
name_template = "trusty"
|
||||
|
@ -162,7 +162,7 @@ are configured via this block.
|
|||
|
||||
Example:
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the CLC Provider
|
||||
provider "clc_server" "ubuntu" {
|
||||
# ...
|
||||
|
@ -172,8 +172,3 @@ provider "clc_server" "ubuntu" {
|
|||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the Cloudflare provider
|
||||
provider "cloudflare" {
|
||||
email = "${var.cloudflare_email}"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Provides a Cloudflare record resource.
|
||||
---
|
||||
|
||||
# cloudflare\_record
|
||||
# cloudflare_record
|
||||
|
||||
Provides a Cloudflare record resource.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a record to the domain
|
||||
resource "cloudflare_record" "foobar" {
|
||||
domain = "${var.cloudflare_domain}"
|
||||
|
@ -47,4 +47,3 @@ The following attributes are exported:
|
|||
* `priority` - The priority of the record
|
||||
* `hostname` - The FQDN of the record
|
||||
* `proxied` - (Optional) Whether the record gets Cloudflare's origin protection.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the CloudStack Provider
|
||||
provider "cloudstack" {
|
||||
api_url = "${var.cloudstack_api_url}"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates an affinity group.
|
||||
---
|
||||
|
||||
# cloudstack\_affinity\_group
|
||||
# cloudstack_affinity_group
|
||||
|
||||
Creates an affinity group.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_affinity_group" "default" {
|
||||
name = "test-affinity-group"
|
||||
type = "host anti-affinity"
|
||||
|
|
|
@ -6,14 +6,14 @@ description: |-
|
|||
Creates a disk volume from a disk offering. This disk volume will be attached to a virtual machine if the optional parameters are configured.
|
||||
---
|
||||
|
||||
# cloudstack\_disk
|
||||
# cloudstack_disk
|
||||
|
||||
Creates a disk volume from a disk offering. This disk volume will be attached to
|
||||
a virtual machine if the optional parameters are configured.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_disk" "default" {
|
||||
name = "test-disk"
|
||||
attach = "true"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates egress firewall rules for a given network.
|
||||
---
|
||||
|
||||
# cloudstack\_egress\_firewall
|
||||
# cloudstack_egress_firewall
|
||||
|
||||
Creates egress firewall rules for a given network.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_egress_firewall" "default" {
|
||||
network_id = "6eb22f91-7454-4107-89f4-36afcdf33021"
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates firewall rules for a given IP address.
|
||||
---
|
||||
|
||||
# cloudstack\_firewall
|
||||
# cloudstack_firewall
|
||||
|
||||
Creates firewall rules for a given IP address.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_firewall" "default" {
|
||||
ip_address_id = "30b21801-d4b3-4174-852b-0c0f30bdbbfb"
|
||||
|
||||
|
|
|
@ -6,14 +6,14 @@ description: |-
|
|||
Creates and automatically starts a virtual machine based on a service offering, disk offering, and template.
|
||||
---
|
||||
|
||||
# cloudstack\_instance
|
||||
# cloudstack_instance
|
||||
|
||||
Creates and automatically starts a virtual machine based on a service offering,
|
||||
disk offering, and template.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_instance" "web" {
|
||||
name = "server-1"
|
||||
service_offering = "small"
|
||||
|
@ -82,4 +82,3 @@ The following attributes are exported:
|
|||
|
||||
* `id` - The instance ID.
|
||||
* `display_name` - The display name of the instance.
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Acquires and associates a public IP.
|
||||
---
|
||||
|
||||
# cloudstack\_ipaddress
|
||||
# cloudstack_ipaddress
|
||||
|
||||
Acquires and associates a public IP.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_ipaddress" "default" {
|
||||
network_id = "6eb22f91-7454-4107-89f4-36afcdf33021"
|
||||
}
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates a load balancer rule.
|
||||
---
|
||||
|
||||
# cloudstack\_loadbalancer\_rule
|
||||
# cloudstack_loadbalancer_rule
|
||||
|
||||
Creates a loadbalancer rule.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_loadbalancer_rule" "default" {
|
||||
name = "loadbalancer-rule-1"
|
||||
description = "Loadbalancer rule 1"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates a network.
|
||||
---
|
||||
|
||||
# cloudstack\_network
|
||||
# cloudstack_network
|
||||
|
||||
Creates a network.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates a network.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_network" "default" {
|
||||
name = "test-network"
|
||||
cidr = "10.0.0.0/16"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates a Network ACL for the given VPC.
|
||||
---
|
||||
|
||||
# cloudstack\_network\_acl
|
||||
# cloudstack_network_acl
|
||||
|
||||
Creates a Network ACL for the given VPC.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_network_acl" "default" {
|
||||
name = "test-acl"
|
||||
vpc_id = "76f6e8dc-07e3-4971-b2a2-8831b0cc4cb4"
|
||||
|
@ -40,4 +40,3 @@ The following arguments are supported:
|
|||
The following attributes are exported:
|
||||
|
||||
* `id` - The ID of the Network ACL
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates network ACL rules for a given network ACL.
|
||||
---
|
||||
|
||||
# cloudstack\_network\_acl\_rule
|
||||
# cloudstack_network_acl_rule
|
||||
|
||||
Creates network ACL rules for a given network ACL.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_network_acl_rule" "default" {
|
||||
acl_id = "f3843ce0-334c-4586-bbd3-0c2e2bc946c6"
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates an additional NIC to add a VM to the specified network.
|
||||
---
|
||||
|
||||
# cloudstack\_nic
|
||||
# cloudstack_nic
|
||||
|
||||
Creates an additional NIC to add a VM to the specified network.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates an additional NIC to add a VM to the specified network.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_nic" "test" {
|
||||
network_id = "6eb22f91-7454-4107-89f4-36afcdf33021"
|
||||
ip_address = "192.168.1.1"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates port forwards.
|
||||
---
|
||||
|
||||
# cloudstack\_port\_forward
|
||||
# cloudstack_port_forward
|
||||
|
||||
Creates port forwards.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_port_forward" "default" {
|
||||
ip_address_id = "30b21801-d4b3-4174-852b-0c0f30bdbbfb"
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates a private gateway.
|
||||
---
|
||||
|
||||
# cloudstack\_private\_gateway
|
||||
# cloudstack_private_gateway
|
||||
|
||||
Creates a private gateway for the given VPC.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates a private gateway for the given VPC.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_private_gateway" "default" {
|
||||
gateway = "10.0.0.1"
|
||||
ip_address = "10.0.0.2"
|
||||
|
@ -55,4 +55,3 @@ The following arguments are supported:
|
|||
The following attributes are exported:
|
||||
|
||||
* `id` - The ID of the private gateway.
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Assigns a secondary IP to a NIC.
|
||||
---
|
||||
|
||||
# cloudstack\_secondary\_ipaddress
|
||||
# cloudstack_secondary_ipaddress
|
||||
|
||||
Assigns a secondary IP to a NIC.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_secondary_ipaddress" "default" {
|
||||
virtual_machine_id = "server-1"
|
||||
}
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates a security group.
|
||||
---
|
||||
|
||||
# cloudstack\_security\_group
|
||||
# cloudstack_security_group
|
||||
|
||||
Creates a security group.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_security_group" "default" {
|
||||
name = "allow_web"
|
||||
description = "Allow access to HTTP and HTTPS"
|
||||
|
@ -37,4 +37,3 @@ The following arguments are supported:
|
|||
The following attributes are exported:
|
||||
|
||||
* `id` - The ID of the security group.
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Authorizes and revokes both ingress and egress rulea for a given security group.
|
||||
---
|
||||
|
||||
# cloudstack\_security\_group\_rule
|
||||
# cloudstack_security_group_rule
|
||||
|
||||
Authorizes and revokes both ingress and egress rulea for a given security group.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_security_group_rule" "web" {
|
||||
security_group_id = "e340b62b-fbc2-4081-8f67-e40455c44bce"
|
||||
|
||||
|
@ -69,4 +69,3 @@ The `rule` block supports:
|
|||
The following attributes are exported:
|
||||
|
||||
* `id` - The security group ID for which the rules are created.
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates or registers an SSH key pair.
|
||||
---
|
||||
|
||||
# cloudstack\_ssh\_keypair
|
||||
# cloudstack_ssh_keypair
|
||||
|
||||
Creates or registers an SSH key pair.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_ssh_keypair" "default" {
|
||||
name = "myKey"
|
||||
public_key = "${file("~/.ssh/id_rsa.pub")}"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Enables static NAT for a given IP address.
|
||||
---
|
||||
|
||||
# cloudstack\_static\_nat
|
||||
# cloudstack_static_nat
|
||||
|
||||
Enables static NAT for a given IP address
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_static_nat" "default" {
|
||||
ip_address_id = "f8141e2f-4e7e-4c63-9362-986c908b7ea7"
|
||||
virtual_machine_id = "6ca2a163-bc68-429c-adc8-ab4a620b1bb3"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Creates a static route.
|
||||
---
|
||||
|
||||
# cloudstack\_static\_route
|
||||
# cloudstack_static_route
|
||||
|
||||
Creates a static route for the given private gateway or VPC.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_static_route" "default" {
|
||||
cidr = "10.0.0.0/16"
|
||||
gateway_id = "76f607e3-e8dc-4971-8831-b2a2b0cc4cb4"
|
||||
|
@ -34,4 +34,3 @@ The following arguments are supported:
|
|||
The following attributes are exported:
|
||||
|
||||
* `id` - The ID of the static route.
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Registers an existing template into the CloudStack cloud.
|
||||
---
|
||||
|
||||
# cloudstack\_template
|
||||
# cloudstack_template
|
||||
|
||||
Registers an existing template into the CloudStack cloud.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_template" "centos64" {
|
||||
name = "CentOS 6.4 x64"
|
||||
format = "VHD"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates a VPC.
|
||||
---
|
||||
|
||||
# cloudstack\_vpc
|
||||
# cloudstack_vpc
|
||||
|
||||
Creates a VPC.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates a VPC.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_vpc" "default" {
|
||||
name = "test-vpc"
|
||||
cidr = "10.0.0.0/16"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates a site to site VPN connection.
|
||||
---
|
||||
|
||||
# cloudstack\_vpn\_connection
|
||||
# cloudstack_vpn_connection
|
||||
|
||||
Creates a site to site VPN connection.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates a site to site VPN connection.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_vpn_connection" "default" {
|
||||
customer_gateway_id = "8dab9381-ae73-48b8-9a3d-c460933ef5f7"
|
||||
vpn_gateway_id = "a7900060-f8a8-44eb-be15-ea54cf499703"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates a site to site VPN local customer gateway.
|
||||
---
|
||||
|
||||
# cloudstack\_vpn\_customer\_gateway
|
||||
# cloudstack_vpn_customer_gateway
|
||||
|
||||
Creates a site to site VPN local customer gateway.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates a site to site VPN local customer gateway.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_vpn_customer_gateway" "default" {
|
||||
name = "test-vpc"
|
||||
cidr = "10.0.0.0/8"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates a site to site VPN local gateway.
|
||||
---
|
||||
|
||||
# cloudstack\_vpn\_gateway
|
||||
# cloudstack_vpn_gateway
|
||||
|
||||
Creates a site to site VPN local gateway.
|
||||
|
||||
|
@ -14,7 +14,7 @@ Creates a site to site VPN local gateway.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cloudstack_vpn_gateway" "default" {
|
||||
vpc_id = "f8141e2f-4e7e-4c63-9362-986c908b7ea7"
|
||||
}
|
||||
|
|
|
@ -17,7 +17,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the Cobbler provider
|
||||
provider "cobbler" {
|
||||
username = "${var.cobbler_username}"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Manages a distribution within Cobbler.
|
||||
---
|
||||
|
||||
# cobbler\_distro
|
||||
# cobbler_distro
|
||||
|
||||
Manages a distribution within Cobbler.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cobbler_distro" "ubuntu-1404-x86_64" {
|
||||
name = "foo"
|
||||
breed = "ubuntu"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Manages a Kickstart File within Cobbler.
|
||||
---
|
||||
|
||||
# cobbler\_kickstart\_file
|
||||
# cobbler_kickstart_file
|
||||
|
||||
Manages a Kickstart File within Cobbler.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cobbler_kickstart_file" "my_kickstart" {
|
||||
name = "/var/lib/cobbler/kickstarts/my_kickstart.ks"
|
||||
body = "<content of kickstart file>"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Manages a Profile within Cobbler.
|
||||
---
|
||||
|
||||
# cobbler\_profile
|
||||
# cobbler_profile
|
||||
|
||||
Manages a Profile within Cobbler.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cobbler_profile" "my_profile" {
|
||||
name = "/var/lib/cobbler/snippets/my_snippet"
|
||||
distro = "ubuntu-1404-x86_64"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Manages a Snippet within Cobbler.
|
||||
---
|
||||
|
||||
# cobbler\_snippet
|
||||
# cobbler_snippet
|
||||
|
||||
Manages a Snippet within Cobbler.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cobbler_snippet" "my_snippet" {
|
||||
name = "/var/lib/cobbler/snippets/my_snippet"
|
||||
body = "<content of snippet>"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Manages a System within Cobbler.
|
||||
---
|
||||
|
||||
# cobbler\_system
|
||||
# cobbler_system
|
||||
|
||||
Manages a System within Cobbler.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "cobbler_system" "my_system" {
|
||||
name = "my_system"
|
||||
profile = "${cobbler_profile.my_profile.name}"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides the configuration information of the local Consul agent.
|
||||
---
|
||||
|
||||
# consul\_agent_\_self
|
||||
# consul_agent__self
|
||||
|
||||
The `consul_agent_self` data source returns
|
||||
[configuration and status data](https://www.consul.io/docs/agent/http/agent.html#agent_self)
|
||||
|
@ -14,9 +14,12 @@ from the agent specified in the `provider`.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "consul_agent_self" "read-dc1-agent" {
|
||||
# query_options { # # Optional parameter: implicitly uses the current datacenter of the agent # datacenter = "dc1" # }
|
||||
query_options {
|
||||
# Optional parameter: implicitly uses the current datacenter of the agent
|
||||
datacenter = "dc1"
|
||||
}
|
||||
}
|
||||
|
||||
# Set the description to a whitespace delimited list of the services
|
||||
|
|
|
@ -6,14 +6,14 @@ description: |-
|
|||
Reads values from the Consul key/value store.
|
||||
---
|
||||
|
||||
# consul\_keys
|
||||
# consul_keys
|
||||
|
||||
The `consul_keys` resource reads values from the Consul key/value store.
|
||||
This is a powerful way dynamically set values in templates.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "consul_keys" "app" {
|
||||
datacenter = "nyc1"
|
||||
token = "abcd"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides a list of nodes in a given Consul datacenter.
|
||||
---
|
||||
|
||||
# consul\_catalog\_nodes
|
||||
# consul_catalog_nodes
|
||||
|
||||
The `consul_catalog_nodes` data source returns a list of Consul nodes that have
|
||||
been registered with the Consul cluster in a given datacenter. By specifying a
|
||||
|
@ -15,9 +15,12 @@ nodes from a different WAN-attached Consul datacenter.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "consul_catalog_nodes" "read-dc1-nodes" {
|
||||
# query_options { # # Optional parameter: implicitly uses the current datacenter of the agent # datacenter = "dc1" # }
|
||||
query_options {
|
||||
# Optional parameter: implicitly uses the current datacenter of the agent
|
||||
datacenter = "dc1"
|
||||
}
|
||||
}
|
||||
|
||||
# Set the description to a whitespace delimited list of the node names
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides details about a specific Consul service
|
||||
---
|
||||
|
||||
# consul\_catalog\_service
|
||||
# consul_catalog_service
|
||||
|
||||
`consul_catalog_service` provides details about a specific Consul service in a
|
||||
given datacenter. The results include a list of nodes advertising the specified
|
||||
|
@ -19,9 +19,12 @@ source, which provides a summary of the current Consul services.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "consul_catalog_service" "read-consul-dc1" {
|
||||
# query_options { # # Optional parameter: implicitly uses the current datacenter of the agent # datacenter = "dc1" # }
|
||||
query_options {
|
||||
# Optional parameter: implicitly uses the current datacenter of the agent
|
||||
datacenter = "dc1"
|
||||
}
|
||||
|
||||
name = "consul"
|
||||
}
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides a list of services in a given Consul datacenter.
|
||||
---
|
||||
|
||||
# consul\_catalog\_services
|
||||
# consul_catalog_services
|
||||
|
||||
The `consul_catalog_services` data source returns a list of Consul services that
|
||||
have been registered with the Consul cluster in a given datacenter. By
|
||||
|
@ -18,9 +18,12 @@ source, which provides a detailed response about a specific Consul service.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "consul_catalog_services" "read-dc1" {
|
||||
# query_options { # # Optional parameter: implicitly uses the current datacenter of the agent # datacenter = "dc1" # }
|
||||
query_options {
|
||||
# Optional parameter: implicitly uses the current datacenter of the agent
|
||||
datacenter = "dc1"
|
||||
}
|
||||
}
|
||||
|
||||
# Set the description to a whitespace delimited list of the services
|
||||
|
|
|
@ -17,7 +17,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the Consul provider
|
||||
provider "consul" {
|
||||
address = "demo.consul.io:80"
|
||||
|
@ -51,4 +51,3 @@ The following arguments are supported:
|
|||
* `ca_file` - (Optional) A path to a PEM-encoded certificate authority used to verify the remote agent's certificate.
|
||||
* `cert_file` - (Optional) A path to a PEM-encoded certificate provided to the remote agent; requires use of `key_file`.
|
||||
* `key_file`- (Optional) A path to a PEM-encoded private key, required if `cert_file` is specified.
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides access to Agent Service data in Consul. This can be used to define a service associated with a particular agent. Currently, defining health checks for an agent service is not supported.
|
||||
---
|
||||
|
||||
# consul\_agent\_service
|
||||
# consul_agent_service
|
||||
|
||||
Provides access to the agent service data in Consul. This can be used to
|
||||
define a service associated with a particular agent. Currently, defining
|
||||
|
@ -14,7 +14,7 @@ health checks for an agent service is not supported.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "consul_agent_service" "app" {
|
||||
address = "www.google.com"
|
||||
name = "google"
|
||||
|
|
|
@ -6,14 +6,14 @@ description: |-
|
|||
Registers a node or service with the Consul Catalog. Currently, defining health checks is not supported.
|
||||
---
|
||||
|
||||
# consul\_catalog\_entry
|
||||
# consul_catalog_entry
|
||||
|
||||
Registers a node or service with the [Consul Catalog](https://www.consul.io/docs/agent/http/catalog.html#catalog_register).
|
||||
Currently, defining health checks is not supported.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "consul_catalog_entry" "app" {
|
||||
address = "192.168.10.10"
|
||||
node = "foobar"
|
||||
|
|
|
@ -7,7 +7,7 @@ description: |-
|
|||
common name prefix.
|
||||
---
|
||||
|
||||
# consul\_key\_prefix
|
||||
# consul_key_prefix
|
||||
|
||||
Allows Terraform to manage a "namespace" of Consul keys that share a common
|
||||
name prefix.
|
||||
|
@ -33,7 +33,7 @@ those keys were created outside of Terraform.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "consul_key_prefix" "myapp_config" {
|
||||
datacenter = "nyc1"
|
||||
token = "abcd"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Writes values into the Consul key/value store.
|
||||
---
|
||||
|
||||
# consul\_keys
|
||||
# consul_keys
|
||||
|
||||
The `consul_keys` resource writes sets of individual values into Consul.
|
||||
This is a powerful way to expose infrastructure details to clients.
|
||||
|
@ -20,7 +20,7 @@ remove errant keys not present in the configuration, consider using the
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "consul_keys" "app" {
|
||||
datacenter = "nyc1"
|
||||
token = "abcd"
|
||||
|
|
|
@ -6,14 +6,14 @@ description: |-
|
|||
Provides access to Node data in Consul. This can be used to define a node.
|
||||
---
|
||||
|
||||
# consul\_node
|
||||
# consul_node
|
||||
|
||||
Provides access to Node data in Consul. This can be used to define a
|
||||
node. Currently, defining health checks is not supported.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "consul_node" "foobar" {
|
||||
address = "192.168.10.10"
|
||||
name = "foobar"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Allows Terraform to manage a Consul prepared query
|
||||
---
|
||||
|
||||
# consul\_prepared\_query
|
||||
# consul_prepared_query
|
||||
|
||||
Allows Terraform to manage a Consul prepared query.
|
||||
|
||||
|
@ -16,57 +16,57 @@ queries in your Consul cluster using Terraform.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Creates a prepared query myquery.query.consul that finds the nearest
|
||||
# healthy myapp.service.consul instance that has the active tag and not
|
||||
# the standby tag.
|
||||
resource "consul_prepared_query" "myapp-query" {
|
||||
name = "myquery"
|
||||
datacenter = "us-central1"
|
||||
token = "abcd"
|
||||
stored_token = "wxyz"
|
||||
only_passing = true
|
||||
near = "_agent"
|
||||
name = "myquery"
|
||||
datacenter = "us-central1"
|
||||
token = "abcd"
|
||||
stored_token = "wxyz"
|
||||
only_passing = true
|
||||
near = "_agent"
|
||||
|
||||
service = "myapp"
|
||||
tags = ["active","!standby"]
|
||||
service = "myapp"
|
||||
tags = ["active", "!standby"]
|
||||
|
||||
failover {
|
||||
nearest_n = 3
|
||||
datacenters = ["us-west1", "us-east-2", "asia-east1"]
|
||||
}
|
||||
failover {
|
||||
nearest_n = 3
|
||||
datacenters = ["us-west1", "us-east-2", "asia-east1"]
|
||||
}
|
||||
|
||||
dns {
|
||||
ttl = "30s"
|
||||
}
|
||||
dns {
|
||||
ttl = "30s"
|
||||
}
|
||||
}
|
||||
|
||||
# Creates a Prepared Query Template that matches *-near-self.query.consul
|
||||
# and finds the nearest service that matches the glob character (e.g.
|
||||
# foo-near-self.query.consul will find the nearest healthy foo.service.consul).
|
||||
resource "consul_prepared_query" "service-near-self" {
|
||||
datacenter = "nyc1"
|
||||
token = "abcd"
|
||||
stored_token = "wxyz"
|
||||
name = ""
|
||||
only_passing = true
|
||||
near = "_agent"
|
||||
datacenter = "nyc1"
|
||||
token = "abcd"
|
||||
stored_token = "wxyz"
|
||||
name = ""
|
||||
only_passing = true
|
||||
near = "_agent"
|
||||
|
||||
template {
|
||||
type = "name_prefix_match"
|
||||
regexp = "^(.*)-near-self$"
|
||||
}
|
||||
template {
|
||||
type = "name_prefix_match"
|
||||
regexp = "^(.*)-near-self$"
|
||||
}
|
||||
|
||||
service = "$${match(1)}"
|
||||
service = "$${match(1)}"
|
||||
|
||||
failover {
|
||||
nearest_n = 3
|
||||
datacenters = ["dc2", "dc3", "dc4"]
|
||||
}
|
||||
failover {
|
||||
nearest_n = 3
|
||||
datacenters = ["dc2", "dc3", "dc4"]
|
||||
}
|
||||
|
||||
dns {
|
||||
ttl = "5m"
|
||||
}
|
||||
dns {
|
||||
ttl = "5m"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
|
|
|
@ -6,14 +6,14 @@ description: |-
|
|||
A high-level resource for creating a Service in Consul. Since Consul requires clients to register services with either the catalog or an agent, `consul_service` may register with either the catalog or an agent, depending on the configuration of `consul_service`. For now, `consul_service` always registers services with the agent running at the address defined in the `consul` resource. Health checks are not currently supported.
|
||||
---
|
||||
|
||||
# consul\_service
|
||||
# consul_service
|
||||
|
||||
A high-level resource for creating a Service in Consul. Currently,
|
||||
defining health checks for a service is not supported.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "consul_service" "google" {
|
||||
address = "www.google.com"
|
||||
name = "google"
|
||||
|
|
|
@ -16,7 +16,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the Datadog provider
|
||||
provider "datadog" {
|
||||
api_key = "${var.datadog_api_key}"
|
||||
|
@ -40,4 +40,3 @@ The following arguments are supported:
|
|||
|
||||
* `api_key` - (Required) Datadog API key. This can also be set via the `DATADOG_API_KEY` environment variable.
|
||||
* `app_key` - (Required) Datadog APP key. This can also be set via the `DATADOG_APP_KEY` environment variable.
|
||||
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Provides a Datadog downtime resource. This can be used to create and manage downtimes.
|
||||
---
|
||||
|
||||
# datadog\_downtime
|
||||
# datadog_downtime
|
||||
|
||||
Provides a Datadog downtime resource. This can be used to create and manage Datadog downtimes.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Create a new daily 1700-0900 Datadog downtime
|
||||
resource "datadog_downtime" "foo" {
|
||||
scope = ["*"]
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Provides a Datadog monitor resource. This can be used to create and manage monitors.
|
||||
---
|
||||
|
||||
# datadog\_monitor
|
||||
# datadog_monitor
|
||||
|
||||
Provides a Datadog monitor resource. This can be used to create and manage Datadog monitors.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Create a new Datadog monitor
|
||||
resource "datadog_monitor" "foo" {
|
||||
name = "Name for monitor foo"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Provides a Datadog timeboard resource. This can be used to create and manage timeboards.
|
||||
---
|
||||
|
||||
# datadog\_timeboard
|
||||
# datadog_timeboard
|
||||
|
||||
Provides a Datadog timeboard resource. This can be used to create and manage Datadog timeboards.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Create a new Datadog timeboard
|
||||
resource "datadog_timeboard" "redis" {
|
||||
title = "Redis Timeboard (created via Terraform)"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Provides a Datadog user resource. This can be used to create and manage users.
|
||||
---
|
||||
|
||||
# datadog\_user
|
||||
# datadog_user
|
||||
|
||||
Provides a Datadog user resource. This can be used to create and manage Datadog users.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Create a new Datadog user
|
||||
resource "datadog_user" "foo" {
|
||||
email = "new@example.com"
|
||||
|
|
|
@ -16,7 +16,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the DNSMadeEasy provider
|
||||
provider "dme" {
|
||||
akey = "${var.dme_akey}"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Provides a DNSMadeEasy record resource.
|
||||
---
|
||||
|
||||
# dme\_record
|
||||
# dme_record
|
||||
|
||||
Provides a DNSMadeEasy record resource.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add an A record to the domain
|
||||
resource "dme_record" "www" {
|
||||
domainid = "123456"
|
||||
|
@ -129,7 +129,7 @@ see DNS Record Types.
|
|||
|
||||
Following are examples of using each of the record types.
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Provide your API and Secret Keys, and whether the sandbox
|
||||
# is being used (defaults to false)
|
||||
provider "dme" {
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Get DNS A record set.
|
||||
---
|
||||
|
||||
# dns\_a\_record\_set
|
||||
# dns_a_record_set
|
||||
|
||||
Use this data source to get DNS A records of the host.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "dns_a_record_set" "google" {
|
||||
host = "google.com"
|
||||
}
|
||||
|
@ -34,4 +34,4 @@ The following attributes are exported:
|
|||
|
||||
* `id` - Set to `host`.
|
||||
|
||||
* `addrs` - A list of IP addresses. IP addresses are always sorted to avoid constant changing plans.
|
||||
* `addrs` - A list of IP addresses. IP addresses are always sorted to avoid constant changing plans.
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Get DNS CNAME record set.
|
||||
---
|
||||
|
||||
# dns\_cname\_record\_set
|
||||
# dns_cname_record_set
|
||||
|
||||
Use this data source to get DNS CNAME record set of the host.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "dns_cname_record_set" "hashicorp" {
|
||||
host = "www.hashicorp.com"
|
||||
}
|
||||
|
@ -34,4 +34,4 @@ The following attributes are exported:
|
|||
|
||||
* `id` - Set to `host`.
|
||||
|
||||
* `cname` - A CNAME record associated with host.
|
||||
* `cname` - A CNAME record associated with host.
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Get DNS TXT record set.
|
||||
---
|
||||
|
||||
# dns\_txt\_record\_set
|
||||
# dns_txt_record_set
|
||||
|
||||
Use this data source to get DNS TXT record set of the host.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "dns_txt_record_set" "hashicorp" {
|
||||
host = "www.hashicorp.com"
|
||||
}
|
||||
|
@ -40,4 +40,4 @@ The following attributes are exported:
|
|||
|
||||
* `record` - The first TXT record.
|
||||
|
||||
* `records` - A list of TXT records.
|
||||
* `records` - A list of TXT records.
|
||||
|
|
|
@ -14,7 +14,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the DNS Provider
|
||||
provider "dns" {
|
||||
update {
|
||||
|
|
|
@ -6,19 +6,23 @@ description: |-
|
|||
Creates a A type DNS record set.
|
||||
---
|
||||
|
||||
# dns\_a\_record\_set
|
||||
# dns_a_record_set
|
||||
|
||||
Creates a A type DNS record set.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
resource "dns_a_record_set" "www" {
|
||||
zone = "example.com."
|
||||
name = "www"
|
||||
addresses = ["192.168.0.1", "192.168.0.2", "192.168.0.3"]
|
||||
ttl = 300
|
||||
}
|
||||
```hcl
|
||||
resource "dns_a_record_set" "www" {
|
||||
zone = "example.com."
|
||||
name = "www"
|
||||
addresses = [
|
||||
"192.168.0.1",
|
||||
"192.168.0.2",
|
||||
"192.168.0.3",
|
||||
]
|
||||
ttl = 300
|
||||
}
|
||||
```
|
||||
|
||||
## Argument Reference
|
||||
|
@ -38,4 +42,3 @@ The following attributes are exported:
|
|||
* `name` - See Argument Reference above.
|
||||
* `addresses` - See Argument Reference above.
|
||||
* `ttl` - See Argument Reference above.
|
||||
|
||||
|
|
|
@ -6,19 +6,22 @@ description: |-
|
|||
Creates a AAAA type DNS record set.
|
||||
---
|
||||
|
||||
# dns\_aaaa\_record\_set
|
||||
# dns_aaaa_record_set
|
||||
|
||||
Creates a AAAA type DNS record set.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
resource "dns_aaaa_record_set" "www" {
|
||||
zone = "example.com."
|
||||
name = "www"
|
||||
addresses = ["fdd5:e282:43b8:5303:dead:beef:cafe:babe", "fdd5:e282:43b8:5303:cafe:babe:dead:beef"]
|
||||
ttl = 300
|
||||
}
|
||||
```hcl
|
||||
resource "dns_aaaa_record_set" "www" {
|
||||
zone = "example.com."
|
||||
name = "www"
|
||||
addresses = [
|
||||
"fdd5:e282:43b8:5303:dead:beef:cafe:babe",
|
||||
"fdd5:e282:43b8:5303:cafe:babe:dead:beef",
|
||||
]
|
||||
ttl = 300
|
||||
}
|
||||
```
|
||||
|
||||
## Argument Reference
|
||||
|
@ -38,4 +41,3 @@ The following attributes are exported:
|
|||
* `name` - See Argument Reference above.
|
||||
* `addresses` - See Argument Reference above.
|
||||
* `ttl` - See Argument Reference above.
|
||||
|
||||
|
|
|
@ -6,19 +6,19 @@ description: |-
|
|||
Creates a CNAME type DNS record.
|
||||
---
|
||||
|
||||
# dns\_cname\_record
|
||||
# dns_cname_record
|
||||
|
||||
Creates a CNAME type DNS record.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
resource "dns_cname_record" "foo" {
|
||||
zone = "example.com."
|
||||
name = "foo"
|
||||
cname = "bar.example.com."
|
||||
ttl = 300
|
||||
}
|
||||
```hcl
|
||||
resource "dns_cname_record" "foo" {
|
||||
zone = "example.com."
|
||||
name = "foo"
|
||||
cname = "bar.example.com."
|
||||
ttl = 300
|
||||
}
|
||||
```
|
||||
|
||||
## Argument Reference
|
||||
|
@ -38,4 +38,3 @@ The following attributes are exported:
|
|||
* `name` - See Argument Reference above.
|
||||
* `cname` - See Argument Reference above.
|
||||
* `ttl` - See Argument Reference above.
|
||||
|
||||
|
|
|
@ -6,19 +6,19 @@ description: |-
|
|||
Creates a PTR type DNS record.
|
||||
---
|
||||
|
||||
# dns\_ptr\_record
|
||||
# dns_ptr_record
|
||||
|
||||
Creates a PTR type DNS record.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
resource "dns_ptr_record" "dns-sd" {
|
||||
zone = "example.com."
|
||||
name = "r._dns-sd"
|
||||
ptr = "example.com."
|
||||
ttl = 300
|
||||
}
|
||||
```hcl
|
||||
resource "dns_ptr_record" "dns-sd" {
|
||||
zone = "example.com."
|
||||
name = "r._dns-sd"
|
||||
ptr = "example.com."
|
||||
ttl = 300
|
||||
}
|
||||
```
|
||||
|
||||
## Argument Reference
|
||||
|
@ -38,4 +38,3 @@ The following attributes are exported:
|
|||
* `name` - See Argument Reference above.
|
||||
* `ptr` - See Argument Reference above.
|
||||
* `ttl` - See Argument Reference above.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the DNSimple provider
|
||||
provider "dnsimple" {
|
||||
token = "${var.dnsimple_token}"
|
||||
|
|
|
@ -12,7 +12,7 @@ Provides a DNSimple record resource.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a record to the root domain
|
||||
resource "dnsimple_record" "foobar" {
|
||||
domain = "${var.dnsimple_domain}"
|
||||
|
@ -23,7 +23,7 @@ resource "dnsimple_record" "foobar" {
|
|||
}
|
||||
```
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a record to a sub-domain
|
||||
resource "dnsimple_record" "foobar" {
|
||||
domain = "${var.dnsimple_domain}"
|
||||
|
|
|
@ -6,13 +6,13 @@ description: |-
|
|||
Get information on Fastly IP ranges.
|
||||
---
|
||||
|
||||
# fastly\_ip_ranges
|
||||
# fastly_ip_ranges
|
||||
|
||||
Use this data source to get the [IP ranges][1] of Fastly edge nodes.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
data "fastly_ip_ranges" "fastly" {}
|
||||
|
||||
resource "aws_security_group" "from_fastly" {
|
||||
|
|
|
@ -18,7 +18,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the Fastly Provider
|
||||
provider "fastly" {
|
||||
api_key = "test"
|
||||
|
@ -49,7 +49,7 @@ Fastly provider block:
|
|||
|
||||
Usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "fastly" {
|
||||
api_key = "test"
|
||||
}
|
||||
|
@ -67,7 +67,7 @@ You can provide your API key via `FASTLY_API_KEY` environment variable,
|
|||
representing your Fastly API key. When using this method, you may omit the
|
||||
Fastly `provider` block entirely:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "fastly_service_v1" "myservice" {
|
||||
# ...
|
||||
}
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides an Fastly Service
|
||||
---
|
||||
|
||||
# fastly\_service\_v1
|
||||
# fastly_service_v1
|
||||
|
||||
Provides a Fastly Service, representing the configuration for a website, app,
|
||||
API, or anything else to be served through Fastly. A Service encompasses Domains
|
||||
|
@ -20,7 +20,7 @@ on their documentation site for guidance.
|
|||
|
||||
Basic usage:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "fastly_service_v1" "demo" {
|
||||
name = "demofastly"
|
||||
|
||||
|
@ -41,7 +41,7 @@ resource "fastly_service_v1" "demo" {
|
|||
|
||||
Basic usage with an Amazon S3 Website and that removes the `x-amz-request-id` header:
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "fastly_service_v1" "demo" {
|
||||
name = "demofastly"
|
||||
|
||||
|
@ -89,7 +89,7 @@ Basic usage with [custom
|
|||
VCL](https://docs.fastly.com/guides/vcl/uploading-custom-vcl) (must be
|
||||
enabled on your Fastly account):
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "fastly_service_v1" "demo" {
|
||||
name = "demofastly"
|
||||
|
||||
|
@ -322,7 +322,7 @@ The `sumologic` block supports:
|
|||
* `name` - (Required) A unique name to identify this Sumologic endpoint.
|
||||
* `url` - (Required) The URL to Sumologic collector endpoint
|
||||
* `format` - (Optional) Apache-style string or VCL variables to use for log formatting. Defaults to Apache Common Log format (`%h %l %u %t %r %>s`)
|
||||
* `format_version` - (Optional) The version of the custom logging format used for the configured endpoint. Can be either 1 (the default, version 1 log format) or 2 (the version 2 log format).
|
||||
* `format_version` - (Optional) The version of the custom logging format used for the configured endpoint. Can be either 1 (the default, version 1 log format) or 2 (the version 2 log format).
|
||||
* `response_condition` - (Optional) Name of already defined `condition` to apply. This `condition` must be of type `RESPONSE`. For detailed information about Conditionals, see [Fastly's Documentation on Conditionals][fastly-conditionals].
|
||||
* `message_type` - (Optional) How the message should be formatted. One of: classic, loggly, logplex, blank. See [Fastly's Documentation on Sumologic][fastly-sumologic]
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Configure the GitHub Provider
|
||||
provider "github" {
|
||||
token = "${var.github_token}"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides a GitHub membership resource.
|
||||
---
|
||||
|
||||
# github\_membership
|
||||
# github_membership
|
||||
|
||||
Provides a GitHub membership resource.
|
||||
|
||||
|
@ -16,7 +16,7 @@ destroyed, either the invitation will be cancelled or the user will be removed.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a user to the organization
|
||||
resource "github_membership" "membership_for_some_user" {
|
||||
username = "SomeUser"
|
||||
|
|
|
@ -6,20 +6,22 @@ description: |-
|
|||
Creates and manages webhooks for Github organizations
|
||||
---
|
||||
|
||||
# github\_organization\_webhook
|
||||
# github_organization_webhook
|
||||
|
||||
This resource allows you to create and manage webhooks for Github organization.
|
||||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "github_organization_webhook" "foo" {
|
||||
name = "web"
|
||||
|
||||
configuration {
|
||||
url = "https://google.de/"
|
||||
url = "https://google.de/"
|
||||
content_type = "form"
|
||||
insecure_ssl = false
|
||||
}
|
||||
|
||||
active = false
|
||||
|
||||
events = ["issues"]
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates and manages repositories within Github organizations
|
||||
---
|
||||
|
||||
# github\_repository
|
||||
# github_repository
|
||||
|
||||
This resource allows you to create and manage repositories within your
|
||||
Github organization.
|
||||
|
@ -16,7 +16,7 @@ outside of organizations.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "github_repository" "example" {
|
||||
name = "example"
|
||||
description = "My awesome codebase"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides a GitHub repository collaborator resource.
|
||||
---
|
||||
|
||||
# github\_repository_collaborator
|
||||
# github_repository_collaborator
|
||||
|
||||
Provides a GitHub repository collaborator resource.
|
||||
|
||||
|
@ -26,7 +26,7 @@ Further documentation on GitHub collaborators:
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a collaborator to a repository
|
||||
resource "github_repository_collaborator" "a_repo_collaborator" {
|
||||
repository = "our-cool-repo"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Creates and manages repository webhooks within Github organizations
|
||||
---
|
||||
|
||||
# github\_repository\_webhook
|
||||
# github_repository_webhook
|
||||
|
||||
This resource allows you to create and manage webhooks for repositories within your
|
||||
Github organization.
|
||||
|
@ -16,10 +16,10 @@ outside of organizations.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "github_repository" "repo" {
|
||||
name = "foo"
|
||||
description = "Terraform acceptance tests"
|
||||
name = "foo"
|
||||
description = "Terraform acceptance tests"
|
||||
homepage_url = "http://example.com/"
|
||||
|
||||
private = false
|
||||
|
@ -29,11 +29,13 @@ resource "github_repository_webhook" "foo" {
|
|||
repository = "${github_repository.repo.name}"
|
||||
|
||||
name = "web"
|
||||
|
||||
configuration {
|
||||
url = "https://google.de/"
|
||||
url = "https://google.de/"
|
||||
content_type = "form"
|
||||
insecure_ssl = false
|
||||
}
|
||||
|
||||
active = false
|
||||
|
||||
events = ["issues"]
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides a GitHub team resource.
|
||||
---
|
||||
|
||||
# github\_team
|
||||
# github_team
|
||||
|
||||
Provides a GitHub team resource.
|
||||
|
||||
|
@ -15,7 +15,7 @@ a new team will be created. When destroyed, that team will be removed.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a team to the organization
|
||||
resource "github_team" "some_team" {
|
||||
name = "some-team"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Provides a GitHub team membership resource.
|
||||
---
|
||||
|
||||
# github\_team_membership
|
||||
# github_team_membership
|
||||
|
||||
Provides a GitHub team membership resource.
|
||||
|
||||
|
@ -17,7 +17,7 @@ destroyed, the user will be removed from the team.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a user to the organization
|
||||
resource "github_membership" "membership_for_some_user" {
|
||||
username = "SomeUser"
|
||||
|
|
|
@ -6,7 +6,7 @@ description: |-
|
|||
Manages the associations between teams and repositories.
|
||||
---
|
||||
|
||||
# github\_team_repository
|
||||
# github_team_repository
|
||||
|
||||
This resource manages relationships between teams and repositories
|
||||
in your Github organization.
|
||||
|
@ -20,7 +20,7 @@ to do that, see [`github_repository`](repository.html).
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
# Add a repository to the team
|
||||
resource "github_team" "some_team" {
|
||||
name = "SomeTeam"
|
||||
|
|
|
@ -16,10 +16,10 @@ Use the navigation to the left to read about the available resources.
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "kubernetes" {
|
||||
config_context_auth_info = "ops"
|
||||
config_context_cluster = "mycluster"
|
||||
config_context_cluster = "mycluster"
|
||||
}
|
||||
|
||||
resource "kubernetes_namespace" "example" {
|
||||
|
@ -58,13 +58,14 @@ Read [more about `kubectl` in the official docs](https://kubernetes.io/docs/user
|
|||
|
||||
The other way is **statically** define all the credentials:
|
||||
|
||||
```
|
||||
```hcl
|
||||
provider "kubernetes" {
|
||||
host = "https://104.196.242.174"
|
||||
host = "https://104.196.242.174"
|
||||
username = "ClusterMaster"
|
||||
password = "MindTheGap"
|
||||
client_certificate = "${file("~/.kube/client-cert.pem")}"
|
||||
client_key = "${file("~/.kube/client-key.pem")}"
|
||||
|
||||
client_certificate = "${file("~/.kube/client-cert.pem")}"
|
||||
client_key = "${file("~/.kube/client-key.pem")}"
|
||||
cluster_ca_certificate = "${file("~/.kube/cluster-ca-cert.pem")}"
|
||||
}
|
||||
```
|
||||
|
|
|
@ -13,14 +13,15 @@ Config Map can be used to store fine-grained information like individual propert
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "kubernetes_config_map" "example" {
|
||||
metadata {
|
||||
name = "my-config"
|
||||
name = "my-config"
|
||||
}
|
||||
|
||||
data {
|
||||
api_host = "myhost:443"
|
||||
db_host = "dbhost:5432"
|
||||
api_host = "myhost:443"
|
||||
db_host = "dbhost:5432"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
|
|
@ -13,15 +13,17 @@ Read more about namespaces at https://kubernetes.io/docs/user-guide/namespaces/
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "kubernetes_namespace" "example" {
|
||||
metadata {
|
||||
annotations {
|
||||
name = "example-annotation"
|
||||
}
|
||||
|
||||
labels {
|
||||
mylabel = "label-value"
|
||||
}
|
||||
|
||||
name = "TerraformExampleNamespace"
|
||||
}
|
||||
}
|
||||
|
|
|
@ -18,7 +18,7 @@ The resource will by default create a secret which is available to any pod in th
|
|||
|
||||
## Example Usage
|
||||
|
||||
```
|
||||
```hcl
|
||||
resource "kubernetes_secret" "example" {
|
||||
metadata {
|
||||
name = "basic-auth"
|
||||
|
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue