scm_revision on Started notification

[fkuep]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.

Feature type

Enhancement to Existing Feature

Feature Summary

When using a webhook notification with a custom "start message body" the job.scm_revision field is empty.

Select the relevant components

• UI
• API
• Docs
• Collection
• CLI
• Other

Steps to reproduce

set: "commit": "{{ job.scm_revision }}",
in the start message body and observe awx sending
commit: "",
in it´s webhook notification.

Current results

commit: "",

Sugested feature result

commit: "87c05830f0e045b55be00ff5e3649",

Additional information

@fosterseth
Would the feature mean that the notification would need to be delayed from pre-run to preparing playbook for the information to be available ?
https://youtu.be/RfQ_6gBHtBs?t=1963

Also - should this feature not be feasable - is there a handy postgres listen query that would give me the commit hash once it is ready ?

[fosterseth]

@fkuep sounds more like a bug. "job.scm_revision" should work according to the docs https://docs.ansible.com/automation-controller/latest/html/userguide/notification_parameters_supported.html

[fkuep]

Thanks for classifing it as bug.
the text in your link says:
scm_revision - (string) scm revision from the project used for this job, if available
Thats why I was not sure.

When I enable updating scm before running, I can see the play getting the lower job_id than the scm-update. Probably the event leading to the notification is to early.

I would like to post notifications to scm as build-status.

[fkuep]

Anything I can do to further progress?

[fkuep]

@fosterseth How would I approach to draw attention to this problem ?
Do You think I should give up ?

[dmzoneill]

@fkuep I've created the following patch

#14847

[fkuep]

Wow - Thanks @dmzoneill !!
Is there an easy way I could make a test install via the operator from your pull-request ?