diff options
| author | Quentin <quentin@deuxfleurs.fr> | 2020-11-22 13:00:15 +0100 |
|---|---|---|
| committer | Quentin <quentin@deuxfleurs.fr> | 2020-11-22 13:00:15 +0100 |
| commit | 804078b3f4597b319307e4d7f5b1b203d85f45b3 (patch) | |
| tree | 7bbdd8caf6c46f060af1123d4b9e867d2b2b41dc | |
| parent | 9f41d95dcf39d21b051fe73f707271cccde5fc39 (diff) | |
| download | infrastructure-804078b3f4597b319307e4d7f5b1b203d85f45b3.tar.gz infrastructure-804078b3f4597b319307e4d7f5b1b203d85f45b3.zip | |
Try to fix lists
| -rw-r--r-- | op_guide/update_matrix.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/op_guide/update_matrix.md b/op_guide/update_matrix.md index 232c0a2..4c451cb 100644 --- a/op_guide/update_matrix.md +++ b/op_guide/update_matrix.md @@ -79,7 +79,9 @@ 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) + 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. |