config.yaml

# config.yaml.original is a clean version that you can refer to after you have edited config.yaml.
# You can even set up a git pre-commit hook to replace config.yaml with this clean version to avoid commiting an edited version.

# Keys:

# projects: Only resources in these projects will get labeled.
# But if the value is empty, *all* projects in the organization are included.
projects: []

# plugins: Only these plugins are enabled.
# For example, add some of these to the list:
#     bigquery, buckets, bigtable, disks,  cloudsql, instances, snaphots, 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, then there is no prefix
iris_prefix: iris

# specific_prefixes gives a prefix per resource type, overriding iris_prefix.
# The comment below shows the resource types with some examples of key-value pairs.
# Empty vs empty-string:
#  - An empty value, as in the Buckets example below, is treated as "None"
#   and will not replace the general iris_prefix.
#  - Empty string, as in the Bigquery example below will override
#   the iris_prefix with empty-string so that you get labels with no prefix.
# Remember to remove the {} after "specific_prefixed:" below if you want to add some values.
specific_prefixes: {}
    #  Buckets:
    #  Bigquery: ""
    #  Bigtable: bt
    #  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.
from_project: True

# If label_all_on_cron is True, then all resource types will be labeled on every cron (Cloud Scheduler) cycle.
#   This is also good for labeling existing resources on first running Iris3.
#
# If label_all_on_cron is False, then to save money, then only resources of some types get labeled on cron:
#   Those whose plugins either
#    - return True on relabel_on_cron()
#   - or return False in is_labeled_on_creation()
#   At present that is Cloud SQL and Disks
label_all_on_cron: True

# Change this before first deployment for added security in communication between PubSub and the Iris App on App Engine.
# You could even re-generate a new token per deployment.
# Note that this approach is not very secure, though it  was once recommended by Google.
# However, so long as our GCP project is secure, this token protects against
# unwanted repetitions of the labeling command.
pubsub_verification_token: 2a343f4c1b76512039fe763412756c4fbb30c