aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQuentin <quentin@deuxfleurs.fr>2020-11-22 12:59:52 +0100
committerQuentin <quentin@deuxfleurs.fr>2020-11-22 12:59:52 +0100
commit9f41d95dcf39d21b051fe73f707271cccde5fc39 (patch)
tree05fea0ab8e5e083eaebf8556094ce06eafd1d4e6
parent33f769c747eacecddfe32774931aeacbf2fe29c0 (diff)
downloadinfrastructure-9f41d95dcf39d21b051fe73f707271cccde5fc39.tar.gz
infrastructure-9f41d95dcf39d21b051fe73f707271cccde5fc39.zip
New line
-rw-r--r--op_guide/update_matrix.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/op_guide/update_matrix.md b/op_guide/update_matrix.md
index c679936..232c0a2 100644
--- a/op_guide/update_matrix.md
+++ b/op_guide/update_matrix.md
@@ -79,7 +79,7 @@ Bear in mind that, once the deployment is done on Nomad, you may still need to w
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.