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
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
* api_release_3.0.1:
add code to HostAccess can_add so the browsable API will work
update unit tetsts
use get_object_or_400 to fetch Role
refactor to unit tests
restrict User.admin_role membership changes through RoleUsersList
fix test
do not allow membership changes to User.admin_role
RoleTeam and TeamRole sublist NotFound exception handling and test update
add system job templates to the unified JT list
Reorganize activity stream around org admin/auditors
Allow instant cancel for new jobs
orphan project protection in job delete access
pass context into Job and JobList serializer classes
pass context to unified job template subclasses
Allow auditors to see same /api/v1/config information as admins
Various fixes to get sat-6 integration working.
* inventory_import.py - the inventory script is called foreman.py
* tasks.py - be sure to call `add_section()` before using it
* defaults.py - Add various SATELLITE6_* enablement variables
Relates #3119
The UI will sometimes send an empty string instead of null, we already
handle this in our serializer and treat it as null, so this change
brings our access system in line with the expectation that those two
things should be equal.
Possibly related to #3077
Previously, posting these fields would cause us to check and see if the
user has not only admin access to the job template but use access on
anything used by the job template (because the fields wern't white
listed as being ok to modify without comprehensive use access). It's
convenient for the QA team to be allowed include these fields in PUT's,
and since they're ignored, this patch is fairly benign and shouldn't
alter any behavior.
#3076
