Do the Work Where It Belongs, Once

Send load-balancer registration to the load balancer and announce once per release.

A advanced Ansible challenge worth 20 points. Solve it hands-on in a real Ansible environment in your browser - no local setup, no fake shells.

The Challenge

Scenario: Ticket OPS-4477 - after a deploy the load balancer has no backends, but every web server has grown its own private backends.conf. The release announcement is also posted once per node instead of once per release.

Make lb01 end with exactly two backend lines, leave the web servers without a backends file, and produce exactly one announcement per release (two after a second run with -e app_release=r2). Then run check.