It turns out base_name was deprecated in 3.9 [1] and was just removed in
3.11 released today.

This is squashed with an integration test fix which adds another error
case handling.

[1]: https://github.com/encode/django-rest-framework/commit/7095021db7a3e2a905979c17f5af8fce614edeb9

Change-Id: Icfbd94e40b9efd7c750cfa72a49bdbf930ad8fc6

2.9 has been released and 2.6 has since been EOL'd [1].

[1]: https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html

Change-Id: I401c3f31d51f38def067c027758259388252fa2c

patch_logger is removed in Django 3.0 [1] and so we need to use
assertLogs instead.

However, it doesn't seem like it is a drop in replacement as this
approach doesn't catch some of the logging that occurs when running the
command. Skip those tests for now.

[1]: https://docs.djangoproject.com/en/3.0/releases/3.0/#removed-private-python-2-compatibility-apis

Change-Id: If7be01533c998ebc0624169b7c8d0026dc6b6a75

When gather_facts is true, the task action is named "gather_facts"
instead of setup. Make sure we recover both.

Change-Id: I99498b3c0b126998e3f9832f23a748ef05f62ea2

Change-Id: Ia233a3636c330957acd1e45b76addc2832f99432
Related: https://github.com/ansible-community/ara/pull/97


Co-Authored-By: David Moreau-Simard <dmsimard@redhat.com>
Co-Authored-By: Samuel Hervé <sherve@korem.com>

We rely on pbr to retrieve the version to put it in the docs.

Change-Id: I59d10b9ef6f6d4e89b026111a80e4485af1f0fa6

Django released 3.0 and we're not quite ready yet to support it.
Pin it for now.

Change-Id: I305f29410baad20bd3f8913150289797f1ba98ef

We had already done this for the live interface in
5bd24472 but we need to do the
same thing for static generation.

Change-Id: I5486a869089d6db0740b7d66ea88625c35e53338
Related: https://github.com/ansible-community/ara/issues/48

Change-Id: I41aaf21e97610e7f407a52d6967ebb42f3a44633

Change-Id: Iba42a9a319bb3e987addeda6996d0df61d958108

Change-Id: I00bb6e0ef795bb20c5d27109a1c3de34d449b972

This will allow us to build the docs properly for hosting on
readthedocs.

Change-Id: I6770146239350c1b4e0bed880a3bc9c7239eaa79

When playbooks are not meant to be kept forever, users can easily keep
their database tidy with the "ara-manage prune" command in order to
delete playbooks that are older than N days.

Fixes: https://github.com/ansible-community/ara/issues/31
Change-Id: I341217fd0158eff70b6dce6b80832b0d7c29ac1c

Change-Id: I75105eb0eaf1cfc07b48b50d053bcde352c121f3
Related: https://github.com/ansible-community/ara/issues/76

This is an attempt to prevent encoding errors when posting results or
when rendering them in the API and built-in interface.

Setting UNICODE_JSON [1] to false allows the callback to post results'
content and allows the API browsing interface to render the result.

The built-in UI had a similar problem but isn't fixed by the
UNICODE_JSON because we are using a Response object so use
"surrogateescape" instead.

Related: https://github.com/ansible-community/ara/issues/48

[1]: https://www.django-rest-framework.org/api-guide/settings/#unicode_json

Change-Id: I48bcef440a1ee9c8574fdd24d5c05ef0f13ca666

This will check if the database driver library is installed before
attempting to run the server.

Fixes: https://github.com/ansible-community/ara/issues/63
Change-Id: I42a7eca4909a560aba95d725021f4db1f9682428

These are basic tests but they need to be tested to make sure they
keep working.

Change-Id: I57bd3931655ca70a07b703b204933a70692f1671

This is a small change that removes the hard requirement for python>=3.6.

We can reconsider it in the future but for now this makes it easier for
certain users to deploy for their environment.

This also fixes wrong indentation on the settings file comment.

Change-Id: Iab84818e5e50aa1e3a0951be154718be04fb53f5

Change-Id: I46687b82cd828a25a3897dce020dc39c096872f0
Related: https://github.com/ansible-community/ara/issues/48

This allows the playbook index to be filtered and ordered by doing
things like:
- ?name=playbookname
- ?path=/etc/ansible
- ?status=completed&status=failed
- ?order=id (oldest at the top)
- ?order=-id (most recent at the top)
- ?order=-duration (longest running playbook at the top)

Change-Id: I02a69f507106d434307ce99f4a153e5338377dda

This makes the search by status work the same way for playbooks, plays,
tasks and results.

Change-Id: I61d6942a6446a1f93255e9f52a29444d1b4bf479

This will allow to search for a playbook based on the full path, full
name or a part of either.

Change-Id: I2bbdcd69e6deda2b491f86256d04dc6c8c0b17b1

This change adds API support for ordering objects through various fields,
for example:
- /api/v1/playbooks?order=id (ascending, oldest first)
- /api/v1/playbooks?order=-id (descending, most recent first)

The supported sort orders as of this patch 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)

Resolves: https://github.com/ansible-community/ara/issues/68
Change-Id: I6e2ff227e26efad47e4740db3a0dc23ffae67d50

Before this change, the duration was not stored in the database and was
instead calculated by the API based on the start and end date of
playbooks.

This change moves the duration to the database so it is no longer
computed by the API. This will allow us to search, filter and sort by
duration.

Change-Id: I34e64da98f05ac3c8d0c5e18436d6b16e62ae787

The representation of a file's id when querying a playbook's detail
and a result's detail is different (for now).

Change-Id: Ib258c8e87fae4fbbf407dbdcdcaf4004a3f0e7b1

This add support for searching the created, updated, started and ended
fields for objects that support them.

For example:
- ?created_after=2019-10-01T09:57:36.489016-04:00
- ?started_before=2019-10-01T09:57:36.489016-04:00

Resolves: https://github.com/ansible-community/ara/issues/30
Change-Id: I09dc3382b646605283dfaaa531187c7eeb8da211

This is no-op, it only moves the filtering out to filters.py to
make it easier to manage.

Change-Id: I5a2f10d82075f6734f579a7c84f171b71f4e9de0

Resolves: https://github.com/ansible-community/ara/issues/90
Change-Id: If08342bfd1bb7d52c7b59e1dc00ee1873058f51c

Change-Id: I1ae8df2b6e1468396371b86a59b9737a31628cfd

Change-Id: I408a58b2632a9907bbc7461a42edeebb2647cbdc

- Prefer --user over virtualenv
- Move python requirements from faq to installation docs
- Mention Fedora and OpenSUSE packages

Change-Id: I5f27534500041630209ac0cf449b4f3ce25d7213

Change-Id: Ia37d4b6e2e2838857407e22d4905e9cf5464ec9d