Tags: arrfab/ara
Tags
1.4.0 This is the 1.4.0 stable release of ARA. Changes since 1.3.2: API --- - Added support for searching plays, tasks and hosts by name - Added support for searching playbooks by label - Fixed label representation to be consistent through different calls - Reversed the default sort order for playbooks, plays, tasks and results API server ---------- - Validate that settings.yaml (or ARA_SETTINGS) exists before launching (thank you @zswanson!) - Template the default settings file without objects generated by python-box Bundled reporting interface --------------------------- - Added a default robots.txt to prevent crawling - Added support for searching by label - Improved the display of labels in the playbook list - Added pagination support when browsing the playbook report list - Use relative links for pagination (thank you @flowerysong !) - Bumped included patternfly CSS from 2.21.5 to 2.56.3 ara_api Ansible role ------------ - Provide sensible PATH defaults when virtualenvs are not used - Added support for installing from Fedora packages - Only run SQL migrations once when necessary - Allow retries when attempting to run SQL migrations - Ensure settings.yaml permissions are 0640 - Added "ara_api_secure_logging" variable to control behavior of sensitive tasks with no_log - Properly default to IPv6 when no IPv4 is available - Default gunicorn worker count based on number of available CPU cores - Added support for deploying on EL8 Ansible plugins --------------- - New Ansible plugins: ara_playbook and ara_api - Improved consistency of stored task results (thank you @flowerysong!) - Fix bad logic when determining if labels should be updated - Added support for not saving files based on patterns (thank you @LaurentDumont!) - Added support for specifying default playbook labels Integration tests ----------------- - Refactored integration tests to simplify and improve coverage across different database 8000 backends, linux distributions and versions of Ansible Upgrade notes ------------- - 1.4 introduces a new SQL migration to ensure labels are unique. If upgrading from a previous version, you will need to run SQL migrations with ``ara-manage migrate``.
1.4.0rc2 This is the second release candidate for the 1.4.0 stable release of ARA. Changes since rc1: - Minor fixes and cleanups picked up by rpmlint when packaging 1.4.0rc1 Changes since 1.3.2: API --- - Added support for searching plays, tasks and hosts by name - Added support for searching playbooks by label - Fixed label representation to be consistent through different calls - Reversed the default sort order for playbooks, plays, tasks and results API server ---------- - Validate that settings.yaml (or ARA_SETTINGS) exists before launching (thank you @zswanson!) - Template the default settings file without objects generated by python-box Bundled reporting interface --------------------------- - Added a default robots.txt to prevent crawling - Added support for searching by label - Improved the display of labels in the playbook list - Added pagination support when browsing the playbook report list - Use relative links for pagination (thank you @flowerysong !) - Bumped included patternfly CSS from 2.21.5 to 2.56.3 ara_api Ansible role ------------ - Provide sensible PATH defaults when virtualenvs are not used - Added support for installing from Fedora packages - Only run SQL migrations once when necessary - Allow retries when attempting to run SQL migrations - Ensure settings.yaml permissions are 0640 - Added "ara_api_secure_logging" variable to control behavior of sensitive tasks with no_log - Properly default to IPv6 when no IPv4 is available - Default gunicorn worker count based on number of available CPU cores - Added support for deploying on EL8 Ansible plugins --------------- - New Ansible plugins: ara_playbook and ara_api - Improved consistency of stored task results (thank you @flowerysong!) - Fix bad logic when determining if labels should be updated - Added support for not saving files based on patterns (thank you @LaurentDumont!) - Added support for specifying default playbook labels Integration tests ----------------- - Refactored integration tests to simplify and improve coverage across different database backends, linux distributions and versions of Ansible Upgrade notes ------------- - 1.4 introduces a new SQL migration to ensure labels are unique. If upgrading from a previous version, you will need to run SQL migrations with ``ara-manage migrate``.
1.4.0rc1 This is the first release candidate for the 1.4.0 stable release of ARA. Changes since 1.3.2: API --- - Added support for searching plays, tasks and hosts by name - Added support for searching playbooks by label - Fixed label representation to be consistent through different calls - Reversed the default sort order for playbooks, plays, tasks and results API server ---------- - Validate that settings.yaml (or ARA_SETTINGS) exists before launching (thank you @zswanson!) - Template the default settings file without objects generated by python-box Bundled reporting interface --------------------------- - Added a default robots.txt to prevent crawling - Added support for searching by label - Improved the display of labels in the playbook list - Added pagination support when browsing the playbook report list - Use relative links for pagination (thank you @flowerysong !) - Bumped included patternfly CSS from 2.21.5 to 2.56.3 ara_api Ansible role ------------ - Provide sensible PATH defaults when virtualenvs are not used - Added support for installing from Fedora packages - Only run SQL migrations once when necessary - Allow retries when attempting to run SQL migrations - Ensure settings.yaml permissions are 0640 - Added "ara_api_secure_logging" variable to control behavior of sensitive tasks with no_log - Properly default to IPv6 when no IPv4 is available - Default gunicorn worker count based on number of available CPU cores - Added support for deploying on EL8 Ansible plugins --------------- - New Ansible plugins: ara_playbook and ara_api - Improved consistency of stored task results (thank you @flowerysong!) - Fix bad logic when determining if labels should be updated - Added support for not saving files based on patterns (thank you @LaurentDumont!) - Added support for specifying default playbook labels Integration tests ----------------- - Refactored integration tests to simplify and improve coverage across different database backends, linux distributions and versions of Ansible Upgrade notes ------------- - 1.4 introduces a new SQL migration to ensure labels are unique. If upgrading from a previous version, you will need to run SQL migrations with ``ara-manage migrate``.
0.16.7 0.16.7 is a maintenance release for ARA 0.x. Changes since 0.16.6: - Fix typo in ara.setup.env for ANSIBLE_ACTION_PLUGINS [1] - Pin pyfakefs to <4 in order to avoid breaking python2 usage [2] - Pin junit-xml to <=1.8 in order to avoid deprecation warnings in unit tests ARA 0.x end of life ------------------- The code base for ARA 0.x has not been actively maintained and developed since 2018 and will officially reach end of life June 4th, 2019, one year after the release of ARA 1.0. Unless critical bugs are found between this release and June 4th, 0.16.7 will be the last supported release of the 0.x branch. Please use the latest version of ARA to benefit from the new features and fixes. [1]: ansible-community#97 [2]: ansible-community#118
1.3.2 This is the 1.3.2 stable release of ARA. Changes since 1.3.1: - Fix compatibility with the new version of django-rest-framework, 3.11 [1] [1]: ansible-community#102
1.3.1 This is the 1.3.1 stable release of ARA. Changes since 1.3.0: - bugfix: the callback plugin now properly retrieves host facts for both setup and gather_fact tasks - bugfix: fixed a typo in ara.setup.env which set the ANSIBLE_ACTION_PLUGINS to the callback directory instead of the action module directory. - unit tests: use assertLogs instead of patch_logger since patch_logger was removed from django 3. - misc: bumped versions of Ansible used in integration tests
1.3.1rc2 This is the second release candidate for the 1.3.1 stable release of ARA. Changes since 1.3.0: - bugfix: the callback plugin now properly retrieves host facts for both setup and gather_fact tasks - bugfix: fixed a typo in ara.setup.env which set the ANSIBLE_ACTION_PLUGINS to the callback directory instead of the action module directory. - unit tests: use assertLogs instead of patch_logger since patch_logger was removed from django 3. - misc: bumped versions of Ansible used in integration tests
1.3.1rc1 This is the first release candidate for the 1.3.1 stable release of ARA. Changes since 1.3.0: - bugfix: the callback plugin now properly retrieves host facts for both setup and gather_fact tasks - unit tests: use assertLogs instead of patch_logger since patch_logger was removed from django 3. - misc: bumped versions of Ansible used in integration tests
1.3.0
This is the 1.3.0 stable release of ARA.
Changes since 1.2.0:
General
-------
- Removed hard requirement on python 3.6 due to the usage of f-strings.
ARA should also work on python 3.5 now.
Web user interface
------------------
- Added a tab at the top of the playbook list to search, sort and filter by date
- Search can be based on the playbook's name, path, or status
- Sort can be ascending or descending for start date, end date or duration
- Filter can show playbooks in the last 60 minutes, 24 hours, 7 days or 30 days
- Fixed a bad link to the task file in the detailed result view
API
---
- Added support for searching date fields for playbooks, plays, tasks and results [1]
For example:
/api/v1/playbooks?started_before=2019-10-01T09:57:36.489016
/api/v1/results?created_after=2019-10-01T09:57:36.489016
- The duration of items is now calculated and stored in the database model
instead of being calculated on demand by the API. This provides the ability to
easily sort objects based on their duration.
A SQL migration has been added as a result of this change.
- Added support for ordering objects by most fields [2]
For example:
/api/v1/playbooks?order=id (ascending, oldest first)
/api/v1/playbooks?order=-id (descending, most recent first)
The currently supported fields available for sorting are:
- created
- updated
- started (for playbooks, plays, tasks, results)
- ended (for playbooks plays, tasks, results)
- duration (for playbooks, plays, tasks, results)
- path (for files)
- key (for records)
- ok, skipped, changed, failed and unreachable (for hosts)
- Added support for searching playbooks by their full path or only part of it.
For example, a playbook with the path ``/home/user/ansible/playbook.yml``
can be found by searching for either ``user`` or the full path.
- Searching for playbook names now also supports partial search.
- Improved handling of non-ascii/binary output to prevent UnicodeEncodeError
exceptions [3]
- Standardized the search by status for playbooks, plays, tasks and results
- The built-in development server now checks if psycopg2 or mysqlclient are
installed before launching when using the postgresql or mysql database backend. [4]
API client
----------
- Added support for ignoring SSL verification [5]
Plugins
-------
- Added the ``ARA_API_INSECURE`` setting to the callback plugin to ignore SSL
verification.
CLI
---
- Added an ``ara-manage prune`` command to delete playbooks older than a specified
amount of days. [6]
Documentation
-------------
- Refreshed docs on installation
- First iteration of documentation for the ``ara-manage`` commands
- Docs now require the API server dependencies to be installed so CLI snippets
can be included automatically with sphinxcontrib-programoutput.
Upgrade notes
-------------
- 1.3.0 introduces a new SQL migration to move durations from the API to the
database model. If upgrading from a previous version, you will need to run
SQL migrations with ``ara-manage migrate``.
Referenced or fixed issues
--------------------------
[1]: ansible-community#30
[2]: ansible-community#68
[3]: ansible-community#48
[4]: ansible-community#63
[5]: ansible-community#90
[6]: ansible-community#31
1.3.0rc2
This is the second release candidate for the 1.3.0 stable release of ARA.
Changes since 1.2.0:
General
-------
- Removed hard requirement on python 3.6 due to the usage of f-strings.
ARA should also work on python 3.5 now.
Web user interface
------------------
- Added a tab at the top of the playbook list to search, sort and filter by date
- Search can be based on the playbook's name, path, or status
- Sort can be ascending or descending for start date, end date or duration
- Filter can show playbooks in the last 60 minutes, 24 hours, 7 days or 30 days
- Fixed a bad link to the task file in the detailed result view
API
---
- Added support for searching date fields for playbooks, plays, tasks and results [1]
For example:
/api/v1/playbooks?started_before=2019-10-01T09:57:36.489016
/api/v1/results??created_after=2019-10-01T09:57:36.489016
- The duration of items is now calculated and stored in the database model
instead of being calculated on demand by the API. This provides the ability to
easily sort objects based on their duration.
A SQL migration has been added as a result of this change.
- Added support for ordering objects by most fields [2]
For example:
/api/v1/playbooks?order=id (ascending, oldest first)
/api/v1/playbooks?order=-id (descending, most recent first)
The currently supported fields available for sorting are:
- created
- updated
- started (for playbooks, plays, tasks, results)
- ended (for playbooks plays, tasks, results)
- duration (for playbooks, plays, tasks, results)
- path (for files)
- key (for records)
- ok, skipped, changed, failed and unreachable (for hosts)
- Added support for searching playbooks by their full path or only part of it.
For example, a playbook with the path ``/home/user/ansible/playbook.yml``
can be found by searching for either ``user`` or the full path.
- Searching for playbook names now also supports partial search.
- Improved handling of non-ascii/binary output to prevent UnicodeEncodeError
exceptions [3]
- Standardized the search by status for playbooks, plays, tasks and results
- The built-in development server now checks if psycopg2 or mysqlclient are
installed before launching when using the postgresql or mysql database backend. [4]
API client
----------
- Added support for ignoring SSL verification [5]
Plugins
-------
- Added the ``ARA_API_INSECURE`` setting to the callback plugin to ignore SSL
verification.
CLI
---
- Added an ``ara-manage prune`` command to delete playbooks older than a specified
amount of days. [6]
Documentation
-------------
- Refreshed docs on installation
- First iteration of documentation for the ``ara-manage`` commands
- Docs now require the API server dependencies to be installed so CLI snippets
can be included automatically with sphinxcontrib-programoutput.
Upgrade notes
-------------
- 1.3.0 introduces a new SQL migration to move durations from the API to the
database model. If upgrading from a previous version, you will need to run
SQL migrations with ``ara-manage migrate``.
Referenced or fixed issues
--------------------------
[1]: ansible-community#30
[2]: ansible-community#68
[3]: ansible-community#48
[4]: ansible-community#63
[5]: ansible-community#90
[6]: ansible-community#31
PreviousNext