From 72c9d79d3776134539ab434d265068d3f8a36eaf Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 21:25:32 +0000 Subject: [PATCH] docs: install moved plugins from the Milo catalog --- alb/observability.mdx | 2 +- datumctl/ai/assistant.mdx | 5 +++-- datumctl/discovering-resources.mdx | 2 +- datumctl/plugins/using-plugins.mdx | 7 +++++++ guides/alb-as-httpd.mdx | 2 +- operations/datum-assistant.mdx | 3 ++- 6 files changed, 15 insertions(+), 6 deletions(-) diff --git a/alb/observability.mdx b/alb/observability.mdx index f666869..426d70d 100644 --- a/alb/observability.mdx +++ b/alb/observability.mdx @@ -142,7 +142,7 @@ TIME METHOD STATUS PATH HOST ### Query access logs across load balancers -The `telemetry` plugin queries every log line in your project, including load balancer access logs, with a [LogQL](https://grafana.com/docs/loki/latest/query/) stream selector. To install it, run `datumctl plugin install telemetry`. For example, to see every request that any load balancer in the project answered with `403`: +The `telemetry` plugin queries every log line in your project, including load balancer access logs, with a [LogQL](https://grafana.com/docs/loki/latest/query/) stream selector. To install it, add the Milo catalog with `datumctl plugin index add milo-os milo-os/cli-plugins`, then run `datumctl plugin install milo-os/telemetry`. For example, to see every request that any load balancer in the project answered with `403`: ```bash datumctl telemetry logs '{response_code="403"}' --since 1h diff --git a/datumctl/ai/assistant.mdx b/datumctl/ai/assistant.mdx index 9c4dcaa..c156358 100644 --- a/datumctl/ai/assistant.mdx +++ b/datumctl/ai/assistant.mdx @@ -6,10 +6,11 @@ description: "Chat with Patch, the Datum Cloud assistant, from the terminal: ask Patch is the Datum Cloud assistant. Ask it about your resources in plain language, such as "why is my workload not available?" or "is my load balancer serving?", and it answers using the same permissions your account already has. There's no API key to bring and nothing to configure. -`datumctl assistant` is a [plugin](/datumctl/plugins/using-plugins), so it updates on its own schedule. To install it, run the following command: +`datumctl assistant` is a [plugin](/datumctl/plugins/using-plugins) from the Milo catalog, so it updates on its own schedule. To install it, add the catalog and install the plugin: ```bash -datumctl plugin install assistant +datumctl plugin index add milo-os milo-os/cli-plugins +datumctl plugin install milo-os/assistant ``` ## Start a conversation diff --git a/datumctl/discovering-resources.mdx b/datumctl/discovering-resources.mdx index 74a99be..e806c8e 100644 --- a/datumctl/discovering-resources.mdx +++ b/datumctl/discovering-resources.mdx @@ -161,7 +161,7 @@ Discovery feeds directly into authoring manifests for `datumctl apply` and ## Search across your resources -When you know roughly what you're looking for but not its kind or exact name, use the `search` plugin. It searches your resources by name and kind, and returns the best matches first. To install it, run `datumctl plugin install search`. +When you know roughly what you're looking for but not its kind or exact name, use the `search` plugin. It searches your resources by name and kind, and returns the best matches first. To install it, add the Milo catalog with `datumctl plugin index add milo-os milo-os/cli-plugins`, then run `datumctl plugin install milo-os/search`. ```text $ datumctl search api diff --git a/datumctl/plugins/using-plugins.mdx b/datumctl/plugins/using-plugins.mdx index 9bd1dfd..efe1024 100644 --- a/datumctl/plugins/using-plugins.mdx +++ b/datumctl/plugins/using-plugins.mdx @@ -186,6 +186,13 @@ Listings flag deprecated plugins too: - `datumctl plugin search` adds `[deprecated]` before the description and prints the warning for each deprecated result to stderr after the table. With `-o json`, each deprecated result carries a `deprecated` object instead. `-o json` and `-o name` print no warnings. - `datumctl plugin browse` adds `(deprecated)` after the plugin name and shows the warning in the plugin's details. +The `assistant`, `billing`, `ipam`, `search`, and `telemetry` plugins have moved from the **datum** catalog to the [Milo catalog](https://github.com/milo-os/cli-plugins), and their **datum** entries are deprecated. They keep installing from the **datum** catalog until Datum removes them. datumctl v0.25.0 and later shows the deprecation warning for them. To switch a plugin, add the Milo catalog and install the plugin from it: + +```bash +datumctl plugin index add milo-os milo-os/cli-plugins +datumctl plugin install milo-os/telemetry +``` + ## How plugins stay trustworthy datumctl treats a plugin as untrusted code and protects you in a few ways: diff --git a/guides/alb-as-httpd.mdx b/guides/alb-as-httpd.mdx index e21d0c6..0673d98 100644 --- a/guides/alb-as-httpd.mdx +++ b/guides/alb-as-httpd.mdx @@ -634,7 +634,7 @@ TIME METHOD STATUS PATH HOST DURATION `UPSTREAM` is the Instance's private address, which matches the `INTERNAL IP` column of `datumctl compute instances`. -For every Envoy field, including `response_flags`, query the logs with the `telemetry` plugin. To install it, run `datumctl plugin install telemetry`. A query is a [LogQL](https://grafana.com/docs/loki/latest/query/) stream selector, and without a hostname it matches every ALB in the project. To see the `504` responses for one ALB, match its hostname with the `authority` label: +For every Envoy field, including `response_flags`, query the logs with the `telemetry` plugin. To install it, add the Milo catalog with `datumctl plugin index add milo-os milo-os/cli-plugins`, then run `datumctl plugin install milo-os/telemetry`. A query is a [LogQL](https://grafana.com/docs/loki/latest/query/) stream selector, and without a hostname it matches every ALB in the project. To see the `504` responses for one ALB, match its hostname with the `authority` label: ```bash datumctl telemetry logs '{authority="tile-desire-9gpyk.datumproxy.net", response_code="504"}' --since 1h diff --git a/operations/datum-assistant.mdx b/operations/datum-assistant.mdx index cbced63..7767b2c 100644 --- a/operations/datum-assistant.mdx +++ b/operations/datum-assistant.mdx @@ -8,7 +8,8 @@ Patch uses diagnostic tools from the Datum services your project uses, so it can Patch is available in the terminal with `datumctl assistant`. Conversations are kept by Datum, so you can pick one up from any machine you're signed in on. ```bash -datumctl plugin install assistant +datumctl plugin index add milo-os milo-os/cli-plugins +datumctl plugin install milo-os/assistant datumctl assistant chat "Why is the api-backend workload not available?" ```