From 0192871f381b59936598647e314e862f14bfc0b5 Mon Sep 17 00:00:00 2001 From: Ruben Bosch <8641284+Rubueno@users.noreply.github.com> Date: Fri, 1 Mar 2024 11:14:53 +0100 Subject: [PATCH] Fix typos and remove trailing whitespaces (#29) Co-authored-by: Ruben Bosch --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 54c58c2..ff157ff 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ It uses S3 or HTTP file transmission instead of Git to manage distribution (easy `ansible-pull` assumes that you are checking out an Ansible repository from git. This wasn't an option for us at the scale that we needed, so we turned to HTTP file distribution. -On top of scaling, we've integrated monitoring (via Prometheus) to retain the centralized view of all of our Ansible +On top of scaling, we've integrated monitoring (via Prometheus) to retain the centralized view of all of our Ansible runs and a simple REST API to enable/disable the puller and trigger a run to give more fine-grained control of rollouts. # How to use it @@ -53,7 +53,7 @@ And the config file: Setting `ansible-inventory` to `["inventories/production", "inventories/staging"]` and `playbook` to `site.yml` would mean that the puller would search for the correct host in `production` and `staging`, provided that the hosts were -a part of `site.yml`'s run. Use the `debug` option to get more insight to the process while it is running. +a part of `site.yml`'s run. Use the `debug` option to get more insight to the process while it is running. ## Configuration and Metrics @@ -90,7 +90,7 @@ It currently produces the number of tasks that are ok, skipped, changed, failed, | `ansible_puller_debug` | Whether or not debug mode is enabled | | `ansible_puller_disabled` | Whether or not the puller is disabled | | `ansible_puller_last_success` | Last timestamp of a successful run | -| `ansible_puller_last_exit_code` | Last ansible run exit code" | +| `ansible_puller_last_exit_code` | Last ansible run exit code | | `ansible_puller_play_summary` | Ansible metrics: changed, failures, ok, skipped, unreachable | | `ansible_puller_run_time_seconds` | How long Ansible took to run to completion | | `ansible_puller_running` | Whether or not the puller is currently running |