ec2-fleet-2.7.0

What's Changed

🚀 What’s New?

• Track and log all termination reasons for plugin initiated instance terminations.
• For the case when maxTotalUses is specified, remaining uses will be tracked separately instead of using maxTotalUses for it, maxTotalUses is now read-only.
• Add logs in post job action to expose results of tasks. Previously, tasks terminated with problems were not exposed.

🐛 Bug Fixes

• Fix maxtotaluses decrement logic (stopped decrementing limited uses all the way to -1, as -1 has a special meaning i.e. unlimited)
• #363 Skip termination of scheduled instances until next update cycle when busy.
• #322 Fix lost state on configuration change by persisting data, and rebuilding the state in periodic checks.

✅ PRs

• Fix 322 and 363 by @pdk27 in #376
• Fix unnecessary decrement of maxTotalUses and add clarity to logs around terminations triggered by plugin by @pdk27 in #375

📓 Others

• Minor refactoring / renaming
• Add new integration tests

🤝 Thanks to the contributors for reporting issues and sharing helpful information:

@wosiu, @qibint, @mwos-sl, @fdaca, @xocasdashdash, @igtsekov, @avikivity, @HDatPaddle, @naorc123, @ikaakkola, @kintarowins, @mtn-boblloyd, @pd-andrew-ferguson, @kherpel, @blackliner, @calumgilchristmodulr, @benipeled, @aluczakSumo, @limasilet, @iurisman, @fazdamoa

Full Changelog: ec2-fleet-2.6.0...ec2-fleet-2.7.0