Red Hat reposted this
Watching a security fix move from pull request to closed change record without a single manual handoff is something most teams assume requires months of integration work. This demo shows it happening in one automated flow. The scenario: a CVE is flagged in a Python dependency. A Lightwell-remediated artifact drops in. Developer raises a PR, CI validates the fix, and from that moment Ansible Automation Platform runs the entire delivery pipeline. Dev deployment. Integration tests. ServiceNow work notes updating at every milestone. An approval gate that shows the approver exactly what they're signing off on, which CVE it remediates, which CI build, which change record. Load balancer drain. Production deployment. Smoke test. And if the smoke test fails, automatic rollback to the pre-deployment snapshot. The change request closes with a complete audit trail. No manual incident write-up. No chasing people across Slack and ServiceNow to close tickets. A few things worth noting: The approval prompt isn't a generic approve/reject button. It surfaces the artifact version, the CVE identifier, the CI build link, and the SNOW change number. A governed decision, not a checkbox. The AI step at the end writes the close note as contextual prose, covering the application, version, remediation status, and snapshot reference. Same pattern on the failure path, where it writes the incident note and halts instead of closing. Automation orchestrator isn't replacing your CI/CD tools or your ITSM. It's coordinating the work around them, connecting the moment CI passes to the moment production is verified and the record is closed. One remediation. One governed, automated path to production. Full demo here: https://lnkd.in/eRtERP65 Curious whether your current process closes the change record automatically or if that's still a manual step at the end. #AnsibleAutomation #RedHat #CICD #ITAutomation #DevSecOps #ServiceNow