You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We advise users to run or update to the most recent release of the Ansible NGINX Core collection. Older versions of this collection may not have all enhancements and/or bug fixes applied to them.
8
+
9
+
### Supported Versions
10
+
11
+
This codebase mainly consists of an Ansible collection. Ansible applies security fixes to the most recent three releases. Please find more information in [the Ansible docs](https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#release-status).
12
+
13
+
## Reporting a Vulnerability
14
+
15
+
### Ansible
16
+
17
+
If you find a security vulnerability that affects Ansible directly, we encourage you to report it according to the [Ansible guidelines](https://docs.ansible.com/ansible/devel/community/reporting_bugs_and_features.html#reporting-a-bug).
18
+
19
+
### Codebase
20
+
21
+
If you find a security vulnerability that affects the codebase, we encourage you to report it to the F5 Security Incident Response Team (F5 SIRT):
22
+
23
+
- If you’re an F5 customer with an active support contract, please contact [F5 Technical Support](https://www.f5.com/services/support).
24
+
- If you aren’t an F5 customer, please report any potential or current instances of security vulnerabilities to the F5 SIRT at <[email protected]>.
25
+
26
+
For more information visit [https://www.f5.com/services/support/report-a-vulnerability](https://www.f5.com/services/support/report-a-vulnerability)
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-12Lines changed: 20 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -1,36 +1,44 @@
1
1
# CHANGELOG
2
2
3
+
## 0.8.0 (January 29, 2023)
4
+
5
+
Update `nginx` role to `0.24.0`, `nginx_config` role to `0.6.0`, and `nginx_app_protect` role to `0.9.0`. Check each role's respective CHANGELOG to see what's changed since the latest NGINX collection release:
Update `nginx` role to `0.23.2`, `nginx_config` role to `0.5.2`, and `nginx_app_protect` role to `0.8.1`. Check each role's respective CHANGELOG to see what's changed since the latest NGINX collection release:
Update `nginx` role to `0.23.1`, `nginx_config` role to `0.5.1`, and `nginx_app_protect` role to `0.8.0`. Check each role's respective CHANGELOG to see what's changed since the latest NGINX collection release:
Update `nginx` role to `0.23.0`, `nginx_config` role to `0.5.0`, and `nginx_app_protect` role to `0.7.1`. Check each role's respective CHANGELOG to see what's changed since the latest NGINX collection release:
Update `nginx` role to `0.21.3`, `nginx_config` role to `0.4.2`, and `nginx_app_protect` role to `0.7.0`. Check each role's respective CHANGELOG to see what's changed since the latest NGINX collection release:
* The NGINX Ansible collection is written in `yaml` and supports NGINX Open Source, NGINX Plus and NGINX App Protect.
31
-
* The project follows the standard [Ansible collection directory structure](https://docs.ansible.com/ansible/latest/dev_guide/developing_collections.html):
32
-
* The main code is found in [`roles/`](https://github.com/nginxinc/ansible-collection-nginx/blob/main/roles/) directory (do note that all roles are Git submodules).
33
-
* Sample playbooks and instructions can be found in the [`playbooks/`](https://github.com/nginxinc/ansible-collection-nginx/blob/main/playbooks/) directory.
30
+
- The NGINX Ansible collection is written in `yaml` and supports NGINX Open Source, NGINX Plus and NGINX App Protect.
31
+
- The project follows the standard [Ansible collection directory structure](https://docs.ansible.com/ansible/latest/dev_guide/developing_collections.html):
32
+
- The main code is found in [`roles/`](https://github.com/nginxinc/ansible-collection-nginx/blob/main/roles/) directory (do note that all roles are Git submodules).
33
+
- Sample playbooks and instructions can be found in the [`playbooks/`](https://github.com/nginxinc/ansible-collection-nginx/blob/main/playbooks/) directory.
34
34
35
35
## Contributing
36
36
@@ -44,27 +44,27 @@ To suggest an enhancement, please create an issue on GitHub with the label `enha
44
44
45
45
### Open a Pull Request
46
46
47
-
* Fork the repo, create a branch, implement your changes, submit a PR when your changes are **tested** and ready for review.
48
-
* Fill in [our pull request template](https://github.com/nginxinc/ansible-collection-nginx/blob/main/.github/PULL_REQUEST_TEMPLATE.md).
47
+
- Fork the repo, create a branch, implement your changes, submit a PR when your changes are **tested** and ready for review.
48
+
- Fill in [our pull request template](https://github.com/nginxinc/ansible-collection-nginx/blob/main/.github/PULL_REQUEST_TEMPLATE.md).
49
49
50
50
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.
51
51
52
52
## Code Guidelines
53
53
54
54
### Ansible Guidelines
55
55
56
-
* Run `molecule lint` in each role directory to automatically resolve a lot of `yaml` and Ansible style issues.
57
-
* Run `molecule test --all` in each role directory to catch any other issues.
58
-
* Follow these guides on some good practices for Ansible:
* Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR
65
-
* Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/> and summarized in the next few points:
66
-
* In the subject line, use the present tense ("Add feature" not "Added feature").
67
-
* In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
68
-
* Limit the subject line to 72 characters or less.
69
-
* Reference issues and pull requests liberally after the subject line.
70
-
* 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`).
64
+
- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR
65
+
- Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/> and summarized in the next few points:
66
+
- In the subject line, use the present tense ("Add feature" not "Added feature").
67
+
- In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
68
+
- Limit the subject line to 72 characters or less.
69
+
- Reference issues and pull requests liberally after the subject line.
70
+
- 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`).
0 commit comments