forked from coop-cloud/docs.coopcloud.tech
fix: list indentation
This commit is contained in:
parent
3f2ab68ada
commit
d595a74099
|
@ -44,7 +44,7 @@ There is also a new command `abra app sync <domain>` 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
|
||||
|
||||
|
|
Loading…
Reference in New Issue