From 437811b904485eb57d1d29b905798def35225a31 Mon Sep 17 00:00:00 2001 From: Blaize M Kaye Date: Wed, 6 Mar 2024 14:03:15 +1300 Subject: [PATCH] Updates promote documentation to use lagoon-cli --- docs/concepts-advanced/workflows.md | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-) diff --git a/docs/concepts-advanced/workflows.md b/docs/concepts-advanced/workflows.md index 0313371fe2..4216cd55b4 100644 --- a/docs/concepts-advanced/workflows.md +++ b/docs/concepts-advanced/workflows.md @@ -75,20 +75,13 @@ In our example, we want to promote the Docker images from the `main` environment * First, we need a regular deployed environment with the name `main`. Make sure that the environment has deployed successfully. * Also, make sure that you don't have a branch called `production` in your Git repository. This could lead to weird confusions \(like people pushing into this branch, etc\). -* Now trigger a promotion deployment via this `curl` request: - -```bash title="Trigger a promotion deployment" - curl -X POST \ - https://rest.lagoon.amazeeio.cloud/promote \ - -H 'Content-Type: application/json' \ - -d '{ - "projectName":"myproject", - "sourceEnvironmentName": "main", - "branchName": "production" - }' +* Now trigger a promotion deployment using the [lagoon cli](https://github.com/uselagoon/lagoon-cli): + +```title="Trigger a promotion deployment" +lagoon deploy promote --project="myproject" --source="main" --destination="production" ``` -This tells Lagoon that you want to promote from the source `main` to the destination `production` \(yes, it really uses `branchName` as destination, which is a bit unfortunate, but it will be fixed soon\). +This tells Lagoon that you want to promote from the source `main` to the destination `production`. Lagoon will now do the following: