-
-
Notifications
You must be signed in to change notification settings - Fork 58
/
Copy pathREADME.yaml
181 lines (150 loc) · 6.65 KB
/
README.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
name: terraform-terraform-label
license: APACHE2
github_repo: cloudposse/terraform-terraform-label
deprecated:
notice: |-
This module was an experimental fork and is now obsolete and will not be maintained.
Any projects using `terraform-terraform-label` are encouraged to switch to using
[terraform-null-label](https://github.com/cloudposse/terraform-null-label),
which is actively maintained and used by all current Cloud Posse Terraform modules.
This module was a fork of [terraform-null-label](https://github.com/cloudposse/terraform-null-label), made
at a time when that project was using the Terraform `null` provider (hence the "null" in the name), in order
to remove the `null` provider dependency. This was accomplished by removing outputs that required the `null`
provider.
With the features that became available in Terraform 0.12, the `terraform-null-label` project was able
to retain all of its features and also
[remove the `null` provider](https://github.com/cloudposse/terraform-null-label/commit/d6d24b80d687e76e029f39f444d0163b42c5d5e0),
removing any incentive to further develop `terraform-terraform-label`.
With the key distinguishing feature of `terraform-terraform-label` no longer being a distinguishing feature,
this module was no longer necessary, and all focus returned to maintaining and enhancing `terraform-null-label`,
which now far surpasses this module in functionality.
badges:
- name: Latest Release
image: https://img.shields.io/github/release/cloudposse/terraform-terraform-label.svg?style=for-the-badge
url: https://github.com/cloudposse/terraform-terraform-label/releases/latest
- name: Last Updated
image: https://img.shields.io/github/last-commit/cloudposse/terraform-terraform-label.svg?style=for-the-badge
url: https://github.com/cloudposse/terraform-terraform-label/commits
- name: Slack Community
image: https://slack.cloudposse.com/for-the-badge.svg
url: https://slack.cloudposse.com
# List any related terraform modules that this module may be used with or that this module depends on.
related:
- name: terraform-null-label
description: Terraform Module to define a consistent naming convention by (namespace, stage, name, [attributes])
url: https://github.com/cloudposse/terraform-null-label
description: |-
Terraform module designed to generate consistent label names and tags for resources. Use `terraform-terraform-label` to implement a strict naming convention.
#### `terraform-terraform-label` is a fork of [terraform-null-label](https://github.com/cloudposse/terraform-null-label) which uses only the core Terraform provider.
A label follows the following convention: `{namespace}-{stage}-{name}-{attributes}`. The delimiter (e.g. `-`) is interchangeable.
It's recommended to use one `terraform-terraform-label` module for every unique resource of a given resource type.
For example, if you have 10 instances, there should be 10 different labels.
However, if you have multiple different kinds of resources (e.g. instances, security groups, file systems, and elastic IPs), then they can all share the same label assuming they are logically related.
All [Cloud Posse modules](https://github.com/cloudposse?utf8=%E2%9C%93&q=terraform-&type=&language=) use
the related [terraform-null-label](https://github.com/cloudposse/terraform-null-label) module to ensure resources can be instantiated multiple times within an account and without conflict.
**NOTE:** The second `terraform` word in `terraform-terraform-label` refers to the primary Terraform provider used in this module.
usage: |-
### Simple Example
Include this repository as a module in your existing terraform code:
```hcl
module "eg_prod_bastion_label" {
source = "cloudposse/label/terraform"
# Cloud Posse recommends pinning every module to a specific version
# version = "x.x.x"
namespace = "eg"
stage = "prod"
name = "bastion"
attributes = ["public"]
delimiter = "-"
tags = {
"BusinessUnit" = "XYZ",
"Snapshot" = "true"
}
}
```
This will create an `id` with the value of `eg-prod-bastion-public`.
Now reference the label when creating an instance (for example):
```hcl
resource "aws_instance" "eg_prod_bastion_public" {
instance_type = "t1.micro"
tags = module.eg_prod_bastion_label.tags
}
```
Or define a security group:
```hcl
resource "aws_security_group" "eg_prod_bastion_public" {
vpc_id = var.vpc_id
name = module.eg_prod_bastion_label.id
tags = module.eg_prod_bastion_label.tags
egress {
from_port = 0
to_port = 0
protocol = "-1"
cidr_blocks = ["0.0.0.0/0"]
}
}
```
### Advanced Example
Here is a more complex example with two instances using two different labels. Note how efficiently the tags are defined for both the instance and the security group.
```hcl
module "eg_prod_bastion_abc_label" {
source = "cloudposse/label/terraform"
# Cloud Posse recommends pinning every module to a specific version
# version = "x.x.x"
namespace = "eg"
stage = "prod"
name = "bastion"
attributes = ["abc"]
delimiter = "-"
tags = {
"BusinessUnit" = "ABC"
}
}
resource "aws_security_group" "eg_prod_bastion_abc" {
name = module.eg_prod_bastion_abc_label.id
tags = module.eg_prod_bastion_abc_label.tags
ingress {
from_port = 22
to_port = 22
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
}
resource "aws_instance" "eg_prod_bastion_abc" {
instance_type = "t1.micro"
tags = module.eg_prod_bastion_abc_label.tags
vpc_security_group_ids = [aws_security_group.eg_prod_bastion_abc.id]
}
module "eg_prod_bastion_xyz_label" {
source = "cloudposse/label/terraform"
# Cloud Posse recommends pinning every module to a specific version
# version = "x.x.x"
namespace = "eg"
stage = "prod"
name = "bastion"
attributes = ["xyz"]
delimiter = "-"
tags = {
"BusinessUnit" = "XYZ"
}
}
resource "aws_security_group" "eg_prod_bastion_xyz" {
name = module.eg_prod_bastion_xyz_label.id
tags = module.eg_prod_bastion_xyz_label.tags
ingress {
from_port = 22
to_port = 22
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
}
resource "aws_instance" "eg_prod_bastion_xyz" {
instance_type = "t1.micro"
tags = module.eg_prod_bastion_xyz_label.tags
vpc_security_group_ids = [aws_security_group.eg_prod_bastion_xyz.id]
}
```
include:
- docs/targets.md
- docs/terraform.md
contributors: []