From d595a74099318236fd469e664ea3f9687b190023 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Sat, 14 Oct 2023 10:27:28 +0200 Subject: [PATCH] fix: list indentation --- docs/federation/resolutions/in-progress/013.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/federation/resolutions/in-progress/013.md b/docs/federation/resolutions/in-progress/013.md index e9f6c6d..67d1224 100644 --- a/docs/federation/resolutions/in-progress/013.md +++ b/docs/federation/resolutions/in-progress/013.md @@ -44,7 +44,7 @@ There is also a new command `abra app sync ` which triggers a synchronis When `abra app deploy/upgrade/rollback/sync` is run, here's what we do: -1) `git pull` on the sync repository +* `git pull` on the sync repository * if there are changes, pull them in & log them * if there is a merge conflict, bail out and ask operator to resolve them @@ -54,11 +54,11 @@ The way to avoid merge conflicts will be to never move the `OPERATOR_SYNC_VERSIO The initial implementation asks operators to initialise their own Git repositories. -2) Read the `OPERATOR_SYNC_VERSION` env var as the version to deploy / upgrade from / rollback from +* Read the `OPERATOR_SYNC_VERSION` env var as the version to deploy / upgrade from / rollback from * upgrade: if deployed version does not match `OPERATOR_SYNC_VERSION`, warn before overview * rollback: same as above! -3) Run the deployment +* Run the deployment * if successful, record a new `OPERATOR_SYNC_VERSION`, commit & push the changes * if unsuccessful, do not record a `OPERATOR_SYNC_VERSION` and ask operator to resolve