mirror of
https://github.com/ansible/awx.git
synced 2026-03-15 16:07:30 -02:30
Update changelog and README text
This commit is contained in:
@@ -2,6 +2,10 @@
|
|||||||
|
|
||||||
This is a list of high-level changes for each release of AWX. A full list of commits can be found at `https://github.com/ansible/awx/releases/tag/<version>`.
|
This is a list of high-level changes for each release of AWX. A full list of commits can be found at `https://github.com/ansible/awx/releases/tag/<version>`.
|
||||||
|
|
||||||
|
## 12.0.0 (TBD)
|
||||||
|
- Removed support for HipChat notifications ([EoL announcement](https://www.atlassian.com/partnerships/slack/faq#faq-98b17ca3-247f-423b-9a78-70a91681eff0))
|
||||||
|
|
||||||
|
|
||||||
## 11.2.0 (Apr 29, 2020)
|
## 11.2.0 (Apr 29, 2020)
|
||||||
|
|
||||||
- Inventory updates now use collection-based plugins by default (in Ansible 2.9+):
|
- Inventory updates now use collection-based plugins by default (in Ansible 2.9+):
|
||||||
|
|||||||
@@ -81,7 +81,7 @@ The following notes are changes that may require changes to playbooks:
|
|||||||
- `tower_job_template` no longer supports the deprecated `extra_vars_path` parameter, please use `extra_vars` with the lookup plugin to replace this functionality.
|
- `tower_job_template` no longer supports the deprecated `extra_vars_path` parameter, please use `extra_vars` with the lookup plugin to replace this functionality.
|
||||||
- The `notification_configuration` parameter of `tower_notification` has changed from a string to a dict. Please use the `lookup` plugin to read an existing file into a dict.
|
- The `notification_configuration` parameter of `tower_notification` has changed from a string to a dict. Please use the `lookup` plugin to read an existing file into a dict.
|
||||||
- `tower_credential` no longer supports passing a file name to ssh_key_data.
|
- `tower_credential` no longer supports passing a file name to ssh_key_data.
|
||||||
- The HipChat notification type has been removed and can no longer be created using the `tower_notification` module.
|
- The HipChat `notification_type` has been removed and can no longer be created using the `tower_notification` module.
|
||||||
|
|
||||||
## Running Unit Tests
|
## Running Unit Tests
|
||||||
|
|
||||||
|
|||||||
@@ -82,8 +82,6 @@ The currently-defined Notification Types are:
|
|||||||
|
|
||||||
Each of these have their own configuration and behavioral semantics and testing them may need to be approached in different ways. The following sections will give as much detail as possible.
|
Each of these have their own configuration and behavioral semantics and testing them may need to be approached in different ways. The following sections will give as much detail as possible.
|
||||||
|
|
||||||
> **Note:** The HipChat notification type will be unavailable as of Tower 4.0
|
|
||||||
|
|
||||||
## Email
|
## Email
|
||||||
|
|
||||||
The email notification type supports a wide variety of SMTP servers and has support for SSL/TLS connections and timeouts.
|
The email notification type supports a wide variety of SMTP servers and has support for SSL/TLS connections and timeouts.
|
||||||
|
|||||||
Reference in New Issue
Block a user