docs.yml

site/content/en/main/best-practices/_index.md

@@ -53,7 +53,7 @@ It is suggested to lint and format your modules using `npx pepr format`.
 
 ## Monitoring
 
-Pepr can monitor Mutations and Validations from Admission Controller the through the `npx pepr monitor [module-uuid]` command. This command will display neatly formatted log showing approved and rejected Validations as well as the Mutations.  If `[module-uuid]` is not supplied, then it uses all Pepr admission controller logs as the data source.
+Pepr can monitor Mutations and Validations from Admission Controller the through the `npx pepr monitor [module-uuid]` command. This command will display neatly formatted log showing approved and rejected Validations as well as the Mutations.  If `[module-uuid]` is not supplied, then it uses all Pepr admission controller logs as the data source. If you are unsure of what modules are currently deployed, issue `npx pepr uuid` to display the modules and their descriptions.
 
 ```plaintext
 ✅  MUTATE     pepr-demo/pepr-demo (50c5d836-335e-4aa5-8b56-adecb72d4b17)

site/content/en/main/user-guide/pepr-cli.md

@@ -67,6 +67,16 @@ npx pepr monitor [options] [module-uuid]
 
 ---
 
+## `npx pepr uuid`
+
+Module UUID(s) currently deployed in the cluster with their descriptions.
+
+**Options:**
+
+- `[uuid]` - Specific module UUID
+
+---
+
 ## `npx pepr build`
 
 Create a [zarf.yaml](https://zarf.dev) and K8s manifest for the current module. This includes everything needed to deploy Pepr and the current module into production environments.
@@ -80,3 +90,4 @@ Create a [zarf.yaml](https://zarf.dev) and K8s manifest for the current module.
 - `-o, --output-dir [output directory]` - Define where to place build output
 - `--timeout [timeout]` - How long the API server should wait for a webhook to respond before treating the call as a failure
 - `--rbac-mode [admin|scoped]` - Rbac Mode: admin, scoped (default: admin) (choices: "admin", "scoped", default: "admin")
+