Install NGINX Controller dependencies (#28)

Author: alessfg

.ansible-lint

@@ -6,22 +6,27 @@ labels: ''
 assignees: ''
 ---
 ### Describe the bug
+
 A clear and concise description of what the bug is.
 
 ### To reproduce
+
 Steps to reproduce the behavior:
+
 1. Deploy NGINX Controller Install role using playbook.yml
 2. View output/logs/configuration on '...'
 3. See error
 
 ### Expected behavior
+
 A clear and concise description of what you expected to happen.
 
-### Your environment:
--   Version of the NGINX Controller Install role or specific commit
--   Version of Ansible
--   Version of Jinja2 (if you are using any templating capability)
--   Target deployment platform
+### Your environment
+
+- Version of the NGINX Controller Install role or specific commit
+- Version of Ansible
+- Target deployment platform
 
 ### Additional context
+
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -6,13 +6,17 @@ labels: ''
 assignees: ''
 ---
 ### Is your feature request related to a problem? Please describe
+
 A clear and concise description of what the problem is. Ex. I'm always frustrated when ...
 
 ### Describe the solution you'd like
+
 A clear and concise description of what you want to happen.
 
 ### Describe alternatives you've considered
+
 A clear and concise description of any alternative solutions or features you've considered.
 
 ### Additional context
+
 Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,10 +1,12 @@
 ### Proposed changes
+
 Describe the use case and detail of the change. If this PR addresses an issue on GitHub, make sure to include a link to that issue using one of the [supported keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) here in this description (not in the title of the PR).
 
 ### Checklist
+
 Before creating a PR, run through this checklist and mark each as complete.
 
--   [ ] I have read the [CONTRIBUTING](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/CONTRIBUTING.md) document
--   [ ] I have added Molecule tests that prove my fix is effective or that my feature works
--   [ ] I have checked that any relevant Molecule tests pass after adding my changes
--   [ ] I have updated any relevant documentation (`defaults/main/*.yml`, `README.md` and `CHANGELOG.md`)
+- [ ] I have read the [CONTRIBUTING](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/CONTRIBUTING.md) document
+- [ ] I have added Molecule tests that prove my fix is effective or that my feature works
+- [ ] I have checked that any relevant Molecule tests pass after adding my changes
+- [ ] I have updated any relevant documentation (`defaults/main/*.yml`, `README.md` and `CHANGELOG.md`)

.github/pull_request_template.md

@@ -88,12 +88,12 @@ template: |
 
   ## Install & Upgrade
 
-  *   To install the Ansible NGINX Controller Install role on a fresh environment, run `ansible-galaxy install nginxinc.nginx_controller_install`.
-  *   To upgrade the Ansible NGINX Controller Install role to the latest release, run `ansible-galaxy install -f nginxinc.nginx_controller_install`.
-  *   To install or upgrade to this specific Ansible NGINX Controller Install role release ($RESOLVED_VERSION), run `ansible-galaxy install -f nginxinc.nginx_controller_install,v$RESOLVED_VERSION`.
+  * To install the Ansible NGINX Controller Install role on a fresh environment, run `ansible-galaxy install nginxinc.nginx_controller_install`.
+  * To upgrade the Ansible NGINX Controller Install role to the latest release, run `ansible-galaxy install -f nginxinc.nginx_controller_install`.
+  * To install or upgrade to this specific Ansible NGINX Controller Install role release ($RESOLVED_VERSION), run `ansible-galaxy install -f nginxinc.nginx_controller_install,v$RESOLVED_VERSION`.
 
   ## Resources
 
-  *   Functional configuration examples (check `converge.yml` under each `molecule` scenario) -- [github.com/nginxinc/ansible-role-nginx-controller-install/tree/$RESOLVED_VERSION/molecule](https://github.com/nginxinc/ansible-role-nginx-controller-install/tree/$RESOLVED_VERSION/molecule).
-  *   Ansible Galaxy repository -- [galaxy.ansible.com/nginxinc/nginx_controller_install](https://galaxy.ansible.com/nginxinc/nginx_controller_install).
-  *   NGINX: Better with Ansible demo -- [github.com/alessfg/nginx-ansible-demo](https://github.com/alessfg/nginx-ansible-demo).
+  * Functional configuration examples (check `converge.yml` under each `molecule` scenario) -- [github.com/nginxinc/ansible_role_nginx_controller_install/tree/$RESOLVED_VERSION/molecule](https://github.com/nginxinc/ansible_role_nginx_controller_install/tree/$RESOLVED_VERSION/molecule).
+  * Ansible Galaxy repository -- [galaxy.ansible.com/nginxinc/nginx_controller_install](https://galaxy.ansible.com/nginxinc/nginx_controller_install).
+  * NGINX: Better with Ansible demo -- [github.com/alessfg/nginx-ansible-demo](https://github.com/alessfg/nginx-ansible-demo).

.github/release-drafter.yml

@@ -38,5 +38,5 @@ jobs:
       - name: Run Molecule tests
         run: molecule test -s ${{ matrix.scenario }}
         env:
-          PY_COLORS: "1"
-          ANSIBLE_FORCE_COLOR: "1"
+          PY_COLORS: 1
+          ANSIBLE_FORCE_COLOR: 1

.github/workflows/molecule.yml

@@ -2,7 +2,11 @@
 
 ## 0.1.0 (Unreleased)
 
+FEATURES:
+
+Install NGINX Controller dependencies.
+
 ENHANCEMENTS:
 
-*   Implement GitHub Actions CI/CD workflow for repo.
-*   Add Molecule tests for role.
+* Implement GitHub Actions CI/CD workflow for repo.
+* Add Molecule tests for role.

CHANGELOG.md

@@ -68,9 +68,9 @@ members of the project's leadership.
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
 
 [homepage]: https://www.contributor-covenant.org
 
 For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+<https://www.contributor-covenant.org/faq>

CODE_OF_CONDUCT.md

@@ -11,29 +11,30 @@ The following is a set of guidelines for contributing to the NGINX Controller In
 [Contributing](#contributing)
 
 [Code Guidelines](#code-guidelines)
-*   [Git Guidelines](#git-guidelines)
-*   [Ansible Guidelines](#ansible-guidelines)
 
-[Code of Conduct](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/CODE_OF_CONDUCT.md)
+* [Git Guidelines](#git-guidelines)
+* [Ansible Guidelines](#ansible-guidelines)
+
+[Code of Conduct](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/CODE_OF_CONDUCT.md)
 
 ## Ask a Question
 
 Don't know how something works? Curious if the role can achieve your desired functionality? Please open an Issue on GitHub with the label `question`.
 
 ## Getting Started
 
-Follow our [Installation Guide](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/README.md#Installation) to install Ansible and Molecule and get ready to use the NGINX Controller Install Ansible role.
+Follow our [Installation Guide](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/README.md#Installation) to install Ansible and Molecule and get ready to use the NGINX Controller Install Ansible role.
 
 ### Project Structure
 
-*   The NGINX Controller Install Ansible role is written in `yaml` and supports NGINX Controller.
-*   The project follows the standard [Ansible role directory structure](https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse_roles.html)
-    *   The main code is found in [`tasks/`](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/tasks/).
-    *   Variables can be found in [`defaults/main/`](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/defaults/main/).
-    *   "Constant" variables can be found in [`vars/main.yml`](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/vars/main.yml).
-    *   Configuration templates for NGINX can be found in [`templates/`](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/templates/).
-    *   [Molecule](https://molecule.readthedocs.io/) tests can be found in [`molecule/`](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/molecule/).
-    *   CI/CD is done via GitHub actions using the workflow files found in [`.github/workflows/`](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/.github/workflows/).
+* The NGINX Controller Install Ansible role is written in `yaml` and supports NGINX Controller.
+* The project follows the standard [Ansible role directory structure](https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse_roles.html)
+  * The main code is found in [`tasks/`](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/tasks/).
+  * Variables can be found in [`defaults/main/`](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/defaults/main/).
+  * "Constant" variables can be found in [`vars/main.yml`](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/vars/main.yml).
+  * Configuration templates for NGINX can be found in [`templates/`](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/templates/).
+  * [Molecule](https://molecule.readthedocs.io/) tests can be found in [`molecule/`](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/molecule/).
+  * CI/CD is done via GitHub actions using the workflow files found in [`.github/workflows/`](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/.github/workflows/).
 
 ## Contributing
 
@@ -47,27 +48,27 @@ To suggest an enhancement, please create an issue on GitHub with the label `enha
 
 ### Open a Pull Request
 
-*   Fork the repo, create a branch, implement your changes, add any relevant Molecule tests, submit a PR when your changes are **tested** (using Molecule) and ready for review.
-*   Fill in [our pull request template](https://github.com/nginxinc/ansible-role-nginx-controller-install/blob/main/.github/pull_request_template.md).
+* Fork the repo, create a branch, implement your changes, add any relevant Molecule tests, submit a PR when your changes are **tested** (using Molecule) and ready for review.
+* Fill in [our pull request template](https://github.com/nginxinc/ansible_role_nginx_controller_install/blob/main/.github/pull_request_template.md).
 
 Note: if you’d like to implement a new feature, please consider creating a feature request issue first to start a discussion about the feature.
 
 ## Code Guidelines
 
 ### Ansible Guidelines
 
-*   Run `molecule lint` over your code to automatically resolve a lot of `yaml` and Ansible style issues.
-*   Run `molecule test` on your code before you submit a PR to catch any potential issues. If you are testing a specific molecule scenario, run `molecule test -s <scenario>`.
-*   Follow these guides on some good practices for Ansible:
-    *   <https://www.ansible.com/blog/ansible-best-practices-essentials>
-    *   <https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html>
+* Run `molecule lint` over your code to automatically resolve a lot of `yaml` and Ansible style issues.
+* Run `molecule test` on your code before you submit a PR to catch any potential issues. If you are testing a specific molecule scenario, run `molecule test -s <scenario>`.
+* Follow these guides on some good practices for Ansible:
+  * <https://www.ansible.com/blog/ansible-best-practices-essentials>
+  * <https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html>
 
 ### Git Guidelines
 
-*   Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR
-*   Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/> and summarised in the next few points
-    *   In the subject line, use the present tense ("Add feature" not "Added feature")
-    *   In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...")
-    *   Limit the subject line to 72 characters or less
-    *   Reference issues and pull requests liberally after the subject line
-    *   Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in your text editor to write a good message instead of `git commit -am`)
+* Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR
+* Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/> and summarised in the next few points
+  * In the subject line, use the present tense ("Add feature" not "Added feature")
+  * In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+  * Limit the subject line to 72 characters or less
+  * Reference issues and pull requests liberally after the subject line
+  * Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in your text editor to write a good message instead of `git commit -am`)