This will be branch-relative. If you are ont he `devel` branch then it
will pull that tag, it will try to pull the branch you are on and can be
overridden with the COMPOSE_TAG environment variable
* Switch base tower devel image from u14.04 to c7
* Switch container image to build python dependencies into itself
instead of forcing it to be built on startup
* Upgrade venv pip to 8.1.2
* Neuter queue.py which was heavily tied to redis and was basically
orphaned code
* Alter local_settings to override default cache settings and use
memcached
* Alter local settings to refer to qpid instead of redis for celery
broker
* Purge redis python dependencies and add qpid and memcached
* Update docker-compose to purge redis and add qpid and memcached
* release_3.0.2: (126 commits)
Disable permissions tab in Credential > Edit form if Credential is private (#3288)
Tweaked the popover text for job and skip tags on JT add/edit
Workaround a cascade setnull polymorphic issue
flake8
Fixed old test expectations
Made it so the credential organization field can't be changed
Skip some unit tests
Fixed org auditor visibility of team credentials
Fix sosreport
fix credential kind options for list
interpret any code below 300 as success
bail when status code is over 300
Make CloudForms inventory_script work
Use no_log when handling passwords
Prevent ignored task from being displayed as failing.
making ec2 cred optional on group->edit
making ec2 credential optional for ec2 inventory
Revert "Fix to ensure org auditors can see team credentials"
Fixed team credential list to work with corrected permissions
Making the username and password fields optional
...
* disable permissions tab in credential > edit view if credential is private, resolves#3265
* add tooltip indicating why permissions tab is disabled if cred is private
This makes it so the credential organizaiton field can't be changed
through the API (unless the user is a super user). This brings us into
alignment with the original intent.
These tests broke because we added some additional checks that utilize
the database within the role assignment code, and because of issue
parsing or forming requets between the unit framework and the django
request code I'd guess (for some reason it looks like the `pk` field
isn't getting parsed out and handed in to the kwargs of a post method..
didn't dig into it though.)
And by fix, I mean prevent us from getting into the situation that was
causing the asymetric visiblity by brining us into alignment with the
original intention and spec for how credentials were supposed behave.
#3081
This reverts commit 5dcb0e57d80a3bb0553ca8194890a938257a6e93.
New clarification on what the actual desired behavior of this whole
system means this commit is trash, fixing in a much better way.
Sometimes the job host summaries can land a little later after the job
has finished so sometimes events are still filtering in when the
notifications are triggered
