From 2aac94a34a46cce0fbe3ac6226faa16d9b20e7d7 Mon Sep 17 00:00:00 2001 From: Aaron Crawfis Date: Mon, 4 Mar 2024 16:31:48 -0800 Subject: [PATCH] Fix command link Signed-off-by: Aaron Crawfis --- docs/content/tutorials/new-app/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/tutorials/new-app/index.md b/docs/content/tutorials/new-app/index.md index ef4103987..c5f26c471 100644 --- a/docs/content/tutorials/new-app/index.md +++ b/docs/content/tutorials/new-app/index.md @@ -88,10 +88,10 @@ Radius Applications are where all your app's resources and relationships come to - **`environment`** specifies the Radius Environment which the Applications "binds" to at deployment. This is what determines where containers should run (_Kubernetes_) and which namespace to deploy into (_prefixed with "default"_). In this case, the application will be deployed into the `default` Environment that was created by `rad init`. - **`compute`** specifies the hosting platform where running services in the Application will run. In this case, the services will be deployed into the `default-myapp` Kubernetes namespace within the same cluster where Radius is installed. -1. Let's take a look inside the Application to see what's deployed. Run [`rad app connections`]({{< ref rad_application_connections >}}) to print the Application's resources and relationships: +1. Let's take a look inside the Application to see what's deployed. Run [`rad app graph`]({{< ref rad_application_graph >}}) to print the Application's resources and relationships: ```bash - rad app connections + rad app graph ``` You'll see that nothing has been deployed yet and the app is empty: