bump migration
fine tune validation of project allow_override
return highly custom error message
Restore branch after syncs to address bugs
encountered after changing scm_refspec
remove unused code to determine scm_revision
Check Ansible version before project update and
do not install collections if Ansible version too old
Add docs related to project branch override
New file specific to branch override and refspec
Complete docs on collections to reflect current
implementation and give a folder tree example
Update clustering docs related to project syncs
Fix bug where git depth was ignored during the
local clone from project folder to run folder
Fix bug where submodules were not copied
Addresses some cases where
collection requirements do not exist
collection requirements cannot be evaluated
Consolidate logic for roles and collection installs
Add validation around prompted scm_branch requiring
project allow_override field to be true
Updated related process isolation docs
Fix invalid comarision in serializer
from PR review, clarify pre-check logging, minor docs additions
Copy project folder each job run
change cwd to private_data_dir, from proj
do not add cwd to show_paths if it is
a subdirectory of private_data_dir, which
is already shown
Pass the job private_data_dir to the local
project sync, and also add that directory
to the project sync show paths
Add GitPython dep and use for job sync logic
use this to manage shallow clone from desired
commit, and to map branch to commit,
and to assess necessity of project sync
Start on some validation change, but not all
allow arbitrary playbooks with custom branch
* Two job templates that use the same smart inventory running at the
same time can easily race to recompute the smart inventory <-> host
mapping. In this case, bulk_create() can throw an error when racing.
* The per-smart-inventory advisory lock ensures that the state of the
system is consistent & that bulk_create() runs in isolation.
Do not set a next_run value for disabled schedules
Bail if no fields are changed
Do not update related template if its fields did not change
Change call pattern to schedule.update_computed_fields()
in doing so, fix bug where template does not pick up schedule
due to schedules next_run not being saved
Handle the case (also a bug) where template was not updated
when schedule was deleted
* Disabling an instance is used to stop and instance from being the
target of new jobs to run.
* The instance should still perform it's heartbeat so that it isn't
considered offline.
* If the instance was allowed to go offline on an openshift cluster it
would be deleted from the database.
Remove logic specific to job runs to create a "clouds" file
for openstack credential type
Move that logic into the collection of managed_by_tower
injector methods, so it will be used by all job types
Modify inventory openstack injector logic to use this
data as a base for its logic building the clouds file
Currently we only check the custom virtual environment path when
it's created. However, to tackle with the case when the venv might
have been changed/deleted afterward, we need to validate it at
run-time too.
Signed-off-by: Vismay Golwala <vgolwala@redhat.com>
* Instantiating the callback dispatch queue on each job event callback
is expensive. Instead, instantiate it only once. Note, we do not need to
instantiate the callback queue in the iso case so we do not.
this attempts to surface the underlying runner exception for tracebacks
like this one:
FileNotFoundError: [Errno 2] No such file or directory:
'/tmp/awx_41_93gtgv25/artifacts/41/status'
and then make use of them specifically to make safe the env vars
coming back from an isolated node. This will allow us to capture the
safed versions of custom credential values, but without potentially
clobbering normal env var values that vary between the controller and
the node.
