- Newest
- Most votes
- Most comments
Hello,
Leader-only container commands are only executed during environment creation and deployments, while other commands and server customization operations are performed every time an instance is provisioned or updated. This same behavior is seen for platform hooks. During updates that cause instance replacements such as managed updates, the leader_only:true flag is not set and this is the expected default behavior.
Currently, the workaround is to perform a new deployment after the instance replacements/managed update so that a new leader is elected.
There is an existing feature request for this functionality and I have added a comment on your behalf. There is a similar feature request on our GitHub roadmap and I encourage you to engage the service team on the roadmap page as well.
While I am unable to comment on if/when this feature may get released, I request you to keep an eye on our What's New and Blog pages for any new feature announcements.
Relevant content
- asked 25 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 6 months ago