Alexandre Brandizzi d1e3fb03ce fix(deploy): let EB health converge before failing the version gate ... Elastic Beanstalk reports Ready as soon as a rollout finishes, before enhanced health has converged. Both verification gates decided on the first Ready poll, so a release whose version had activated correctly was failed on a health value that had not settled yet — and then rolled back. The failure message compounded it: run 34293894914 printed 'Environment became Ready without activating expected version a0fdd199...' when the active version was exactly a0fdd199... The discriminator was health, not version, which sends whoever reads the log after the wrong problem. Separate the two conditions, keep polling while the correct version is active but health has not settled, and report the last observed state on timeout. An environment that stays unhealthy for the full window still fails; this does not widen what counts as a good deploy.		2026-09-08 21:31:55 -03:00
..
architecture-quality.yml	chore(deps): bump actions/checkout from 4 to 7 (#51)	2026-08-04 09:56:24 -03:00
ci.yml	chore(terraform): remove tf-poc rehearsal (SH-300) (#95)	2026-09-03 10:40:32 -04:00
dependency-review.yml	feat(deploy): move dev application CD through Terraform (#102)	2026-09-03 14:12:06 +00:00
deploy.yml	fix(deploy): let EB health converge before failing the version gate	2026-09-08 21:31:55 -03:00
labeler.yml	Repo hygiene: PR labeler + README badges (INFRA-56/57) (#5)	2026-06-11 14:14:27 -04:00