|
1 | 1 | # Helper module to bind tags to Google Cloud Platform resources |
2 | 2 |
|
3 | | -A simple module used to retrieve tags data from a GCP project and to assign tags |
4 | | -(binding) to passed resources. The module will create the bindings if they don't |
5 | | -exist, but it will fail to create the bindings if they are already present. |
| 3 | +A simple module used to retrieve tags data from a GCP project and to assign tags |
| 4 | +(binding) to passed resources. The module will create the bindings if they don't |
| 5 | +exist, but it will fail to create the bindings if they are already present. |
6 | 6 |
|
7 | | -Actually the **module supports tagging of storage buckets** and **CloudSQL instances**. |
| 7 | +Actually the **module supports tagging of**: |
| 8 | + |
| 9 | +- **Cloud Storage buckets** |
| 10 | +- **CloudSQL instances** |
| 11 | +- **Artifact Registry repositories** |
8 | 12 |
|
9 | 13 | **IMPORTANT**: when tagging multi-regional buckets, check the location in the |
10 | 14 | Google cloud console (for example it can be `eu`). When tagging clodSQL instances, |
11 | 15 | you must specify the region as the location, not the zone (for example `europe-west1` |
12 | 16 | and not `europe-west1-b`). |
13 | 17 |
|
14 | | -You can pass the tags to the module in a user-friendly and easy to read format, |
| 18 | +**IMPORTANT**: all the CloudSQL roles have to be granted at the project level as lowest-level. |
| 19 | +This means that you can tag resources only for convinience, but you can not use them in the IAM |
| 20 | +conditions. |
| 21 | + |
| 22 | +You can pass the tags to the module in a user-friendly and easy to read format, |
15 | 23 | <TAG_KEY_SHORTNAME>/<TAG_VALUE_SHORTNAME>, so that it will be easy to understand, |
16 | 24 | for example, you can write tasgs to be applied to resources like: |
17 | 25 |
|
18 | 26 | `["dev-team/viewer", "ops-team/admin"]` |
19 | 27 |
|
20 | | -You can also use the module to retrieve information about tags availables in your |
| 28 | +You can also use the module to retrieve information about tags availables in your |
21 | 29 | project, populanting the variable `tags_to_be_discovered` with a full tag structure, |
22 | | -where the tag key is the map key, and the tag values are the values of each map key. |
| 30 | +where the tag key is the map key, and the tag values are the values of each map key. |
23 | 31 | For example: |
24 | 32 |
|
25 | 33 | ```terraform |
|
0 commit comments