From c96c46bd212f50646cefa711837fd1e92d89b7c9 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 7 Oct 2024 22:38:46 +0000 Subject: [PATCH 1/2] [pre-commit.ci] pre-commit autoupdate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit updates: - [github.com/pre-commit/pre-commit-hooks.git: v2.2.3 → v5.0.0](https://github.com/pre-commit/pre-commit-hooks.git/compare/v2.2.3...v5.0.0) - [github.com/ansible/ansible-lint.git: v4.1.0 → v24.9.2](https://github.com/ansible/ansible-lint.git/compare/v4.1.0...v24.9.2) --- .pre-commit-config.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 49a2d36..446f25e 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -2,7 +2,7 @@ repos: - repo: https://github.com/pre-commit/pre-commit-hooks.git - rev: v2.2.3 + rev: v5.0.0 hooks: - id: end-of-file-fixer - id: trailing-whitespace @@ -15,7 +15,7 @@ repos: - id: check-added-large-files - repo: https://github.com/ansible/ansible-lint.git - rev: v4.1.0 + rev: v24.9.2 hooks: - id: ansible-lint files: \.(yaml|yml)$ From 279119cd732ef0b517804ba0e94664da322e2c51 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Mon, 7 Oct 2024 22:39:38 +0000 Subject: [PATCH 2/2] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index ccf4582..86a0bd9 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ -

+

This ansible role is used to setup MySQL node exporter with docker.

@@ -47,7 +47,7 @@ -We eat, drink, sleep and most importantly love **DevOps**. DevOps always promotes automation and standardisation. While setting up various environments like local, dev, testing, production, etc. it is critical to maintain the same environment across. This can easily be achieved using automating the environment setup & installation with the help of ansible-playbooks. +We eat, drink, sleep and most importantly love **DevOps**. DevOps always promotes automation and standardisation. While setting up various environments like local, dev, testing, production, etc. it is critical to maintain the same environment across. This can easily be achieved using automating the environment setup & installation with the help of ansible-playbooks. Smaller roles are created for each environment elements; which also include tasks & tests. These roles can then be grouped together in [ansible-playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) to achieve the desired yet consistent results. @@ -55,7 +55,7 @@ Smaller roles are created for each environment elements; which also include task ## Prerequisites -This module has a few dependencies: +This module has a few dependencies: - [Ansible2.8](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) - [Python](https://www.python.org/downloads) @@ -117,7 +117,7 @@ Following things includes in this role: -## Feedback +## Feedback If you come accross a bug or have any feedback, please log it in our [issue tracker](https://github.com/clouddrove/ansible-role-docker-mysql-node-exporter/issues), or feel free to drop us an email at [hello@clouddrove.com](mailto:hello@clouddrove.com). If you have found it worth your time, go ahead and give us a ★ on [our GitHub](https://github.com/clouddrove/ansible-role-docker-mysql-node-exporter)!