chore: cleaning up jenkins jobs

[phaneendra-reddy-g]

https://2u-internal.atlassian.net/browse/GSRE-2681

Summary:

• cleaning up the Jenkins job config as part of containerization post-migration.

---

Make sure that the following steps are done before merging:

• Have a Site Reliability Engineer review the PR if you don't own all of the services impacted.
• If you are adding any new default values that need to be overridden when this change goes live, update internal repos and add an entry to the top of the CHANGELOG.
• Performed the appropriate testing.

[Copilot]

🔵 Needs a closer look

The PR title/description describe Jenkins job config cleanup, but the changes shown remove lifecycle/retirement tooling instead, so the PR metadata/scope should be aligned before merge.

Pull request overview

This PR removes legacy AWS autoscaling lifecycle/host-retirement automation artifacts from the configuration repo, likely as part of post-migration cleanup of operational workflows.

Changes:

• Deletes the asg_lifcycle_watcher.py SQS/ASG lifecycle watcher utility.
• Removes the retire_host.yml Ansible playbook used for retirement workflows/log sync/minos verification.
• Removes the lifecycle_inventory.py dynamic Ansible inventory script based on ASG instance lifecycle state.

File summaries

File	Description
util/vpc-tools/asg_lifcycle_watcher.py	Removes the ASG lifecycle watcher script that processed SQS lifecycle events.
playbooks/retire_host.yml	Removes the Ansible playbook used for host retirement actions and verification steps.
playbooks/lifecycle_inventory.py	Removes the dynamic inventory generator that grouped instances by ASG lifecycle state.

Review details

Suppressed comments (1)

playbooks/retire_host.yml:1

• The PR title/description indicate a Jenkins job config cleanup, but this change deletes a host-retirement playbook (and related lifecycle tooling) rather than updating Jenkins job configuration. Please align the PR title/description with the actual change (decommissioning these retirement tools) or include the intended Jenkins job config changes so reviewers can validate the correct scope.

• Files reviewed: 3/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.