updating test imports, again
relocate base and make tests a module
added pytest config for awx/lib/site-packages
restrucuting more test imports
more test refactoring
refactoring commands tests
Calling `.after` on a dateutil.rrule object that has an UNTIL clause
performs very poorly if the interval is low and the start time is a long
time ago. This patch replaces two test cases where we were using a
minute interval with a fixed start time of (currently) 2 years ago,
which resulted in aproximately 40s of execution time to simply evaluate
`.after(now())`. Replacing these two tests with tests that start from
"yesterday" while keeping the same INTERVAL and UNTIL settings
eliminates this unnecessary slowdown while maintaining the spirit of the
original tests.
* remove complicated redis config assembly
* backup and restore discover credentials rather than requiring
* backup strategy no longer drops the db. This allows awx user to
restore without creatdb persmission.
* removed mongo from backup/restore
* added password change support for redis, pg, munin
* added update_password command and respective tests
* tests for munin, pg, redis password change
* unit tests for munin, redis password change
* tests for postgres host (ip and socket) change
* tests for postgres backup/restore on remote db
* Move auth backends into sso app.
* Add support for mapping social auth users into organizations and teams.
* Return social auth backends in a consistent order in the API.
* Remove custom SAML attribute mapping and use options provided by PSA.
* Add pipeline function to raise an exception if no user has been found or created; added comments on how to disable new user creation.
* Add comments for defining a custom social auth pipeline function.
* Initialize object attribute to None so a later if check that depends
on that attributes succeeds. The attribute is related to unifying the
command line args to the *_instance command set.
* Added regression test case
Slight tweak to the rbac for projects related to the user who created
them. IF a user created a project but it is orphaned/not associated
with an organization then they will be able to see/change it. If,
however, it is created and associated with an organization and then they
are removed as an org admin they will no longer have access to it.
Now, simply being the creator of a project does not convey any access
for users. You must be in a project/team that has access to it and you
must be an org admin for an org that has the project to be able to make
changes to it
