-
Notifications
You must be signed in to change notification settings - Fork 25
/
config.yaml.original
53 lines (43 loc) · 2.02 KB
/
config.yaml.original
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
# Copy this to make your config.yaml. The default values as-is should work out-of-the-box.
# (You can also make config-test.yaml; See README.md for details.)
# Keys:
# projects: A list of project IDs. Only resources in these projects will get labeled.
# But if the value is empty, *all* projects in the organization will get labeled.
projects: []
# plugins: Only these plugins are enabled.
# For example, add some of these to the list:
# bigquery, buckets, disks, cloudsql, instances, snapshots, subscriptions, topics
# But if the value is empty, *all* plugins are enabled.
plugins: []
# iris_prefix plus underscore is prefixed to the key of each label that is added.
# If empty string is used (the default), then no prefix and no underscore is addded.
iris_prefix: iris
# specific_prefixes gives a prefix per resource type, instead of iris_prefix.
# The default is that there is no override.
# About the meaning of null (missing) values vs empty-string:
# - A null (missing) value, as in the Buckets example below,
# will not replace the general iris_prefix.
# - Empty string as "", as in the Bigquery example below, overrides
# the iris_prefix, so that you get labels with no prefix.
# For an example, see the comment below.
specific_prefixes: {}
# Example:
# specific_prefixes:
# Buckets:
# Bigquery: ""
# Cloudsql: sql
# Disks: gcedisk
# Instances: gce
# Snapshots:
# Subscriptions:
# Topics:
# If from_project is True, then for each resource we are labeling, copy the labels from its project onto it.
# The default is False.
from_project: True
# If label_all_on_cron is False (the default), then to save money,
# only resources of certain types get labeled on cron: those whose plugins either
# - return True on relabel_on_cron() (like Disks)
# - or return False in is_labeled_on_creation() (like Cloud SQL)
# If label_all_on_cron is True, then all resource types will be labeled on every Cloud Scheduler cycle.
# This is useful when you first launch Iris3 for labeling existing resources.
label_all_on_cron: False