From 5fadbd6e2de3dc16074edb71a53cab29b33899d4 Mon Sep 17 00:00:00 2001 From: Mitchell Hentges Date: Wed, 25 Oct 2023 11:46:16 +0200 Subject: [PATCH] docs: backstage-deploy - clarify why Pulumi is needed, downgrade warning This will make it more clear why users need to install Pulumi. The "Ensure Docker is running" warning is downgraded to a tip because "warning" felt a little too aggressive :) Signed-off-by: Mitchell Hentges --- docs/deployment/backstage-deploy/aws.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/deployment/backstage-deploy/aws.md b/docs/deployment/backstage-deploy/aws.md index 957dc27437..818850a6f5 100644 --- a/docs/deployment/backstage-deploy/aws.md +++ b/docs/deployment/backstage-deploy/aws.md @@ -107,7 +107,9 @@ $ export AWS_SECRET_ACCESS_KEY=.... (second secret value) ## Configuring the Pulumi CLI -Second, install the [Pulumi CLI](https://www.pulumi.com/docs/get-started/install/). +Second, install the [Pulumi CLI](https://www.pulumi.com/docs/get-started/install/) - `backstage-deploy` uses it to +simplify the management of cloud resources (Pulumi allows us to simply specify the desired "target cloud state", and +Pulumi will intelligently create/modify/delete resources to reach that state. Nice!). Then we need to execute the following commands, to set Pulumi up: @@ -126,9 +128,9 @@ By using `pulumi login --local` we are making sure that Pulumi stores our state ## Deploying your instance on Lightsail -:::warning +:::tip -Make sure that [Docker](https://docs.docker.com/) is running before you start this section. +Make sure that [Docker](https://docs.docker.com/) is running on your machine before you start this section. :::