aboutsummaryrefslogtreecommitdiff
path: root/op_guide
diff options
context:
space:
mode:
authorQuentin <quentin@deuxfleurs.fr>2020-11-22 13:00:42 +0100
committerQuentin <quentin@deuxfleurs.fr>2020-11-22 13:00:42 +0100
commitf544c202be50ec8cbbd0e7cbfbada63f881081da (patch)
tree52de174344e5585a091e87b312cd8eed667a6460 /op_guide
parent804078b3f4597b319307e4d7f5b1b203d85f45b3 (diff)
downloadinfrastructure-f544c202be50ec8cbbd0e7cbfbada63f881081da.tar.gz
infrastructure-f544c202be50ec8cbbd0e7cbfbada63f881081da.zip
Another try?
Diffstat (limited to 'op_guide')
-rw-r--r--op_guide/update_matrix.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/op_guide/update_matrix.md b/op_guide/update_matrix.md
index 4c451cb..27c12e0 100644
--- a/op_guide/update_matrix.md
+++ b/op_guide/update_matrix.md
@@ -80,8 +80,7 @@ If everythings worked as intended, you can commit and push your deployment file.
If something went wrong, you must rollback your deployment.
- 1. First, find a working deployment with [nomad job history](https://www.nomadproject.io/docs/commands/job/history)
-
+ 1. First, find a working deployment with [nomad job history](https://www.nomadproject.io/docs/commands/job/history)
2. Revert to this deployment with [nomad job revert](https://www.nomadproject.io/docs/commands/job/revert)
Now, if the deployment failed, you should probably investigate what went wrong offline.