You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-4
Original file line number
Diff line number
Diff line change
@@ -25,9 +25,9 @@ Note that Iris is designed to serve the organization. It is not designed around
25
25
26
26
Iris does not *add* information, only *copy* values that already exist. For example, it can label a VM instance with its zone; but it cannot add a "business unit" label because it does not know a resource's business unit. For that, you should label all resources when creating them, e.g., in your Terraform scripts. (Indeed, iris can be made extraneous in this way.)
27
27
28
-
## Existing resources are not all labeled (by default)
28
+
## Labeling resources that existing resources when you deploy Iris
29
29
30
-
If you want to label lots of virtual machines,PubSub topics etc. that *already exist* when you install Iris, see section "[Labeling existing resources](#labeling-existing-resources)" below.
30
+
If you want to label lots of virtual machines,PubSub topics etc. that *already exist* when you deploy Iris, see section "[Labeling existing resources](#labeling-existing-resources)" below.
31
31
32
32
# Open source
33
33
@@ -51,8 +51,7 @@ You can also disable the scheduled labeling. See Deployment below or run `./dep
51
51
## Labeling existing resources
52
52
53
53
* When you first use Iris, you may want to label all existing resources. Iris does not do this by default.
54
-
* To do this, deploy Iris with `label_all_on_cron: True` and wait for the next scheduled run, or manually trigger a run through Cloud Scheduler.
55
-
* Thenּ, you may want to then **redeploy** Iris with `label_all_on_cron: False`, to avoid the resource consumption of relabeling all resources with the same label every day forever.
54
+
* To do this, publish a PubSub message (the content doesn't matter) to `iris_label_all_topic`, for example with `gcloud pubsub topics publish iris_label_all_topic --message=labelall --project $PROJECT_ID` (substituting the project ID where Iris is deployed.) Of course, you will need to have permissions to publish that message.
Copy file name to clipboardExpand all lines: TODO.md
-2
Original file line number
Diff line number
Diff line change
@@ -4,8 +4,6 @@
4
4
5
5
* P2 Memory consumption: Even an empty AppEngine app (not Iris, just a Hello World with 3 lines of code in total) crashes on out-of-memory for the smalled AppEngine instance. Google has confirmed this. See if there is a workaround. This will save money.
6
6
7
-
8
-
9
7
* P3 Label immediately after an event in certain cases, as opposed to using a daily cron as is now done.
0 commit comments