Bump amazon-ssm-agent to 3.1.1208.0#1800
Bump amazon-ssm-agent to 3.1.1208.0#1800jkroepke wants to merge 1 commit intoflatcar-archive:mainfrom
Conversation
|
Hold this until aws/amazon-ssm-agent#439 is merged and released. |
|
@jkroepke: Thanks for the PR! If it takes too much time to get the patch upstream, then we could carry it. But then we would also need to disable self-updates from the ebuild (if there is such a thing). And you are right about dropping go 1.12, which is a nice thing. |
Can you explain it? What did you mean with self-updates in context of this overlay/ebuild? The ebuild way already outdated, such a self-update here would be great. Since the binaries are immutable (read-only usr) on Flatcar, SSM is unable to perform a self-update on a running instance. |
I mean - sometimes the software has the functionality of auto-updating itself. Not sure if this is a thing with SSM. That's why I mentioned disabling it, because there could be a situation that SSM auto-updates itself to a version without the Flatcar support patch.
SSM is installed to the OEM partition ( |
Ah, I see. I did not expect this. I though the SSM is part of the immutable /usr and I the upstream PR was blocking the self-update feature. Thanks for the hint, I modified the PR. |
Bump amazon-ssm-agent to 3.1.1208.0
Bump amazon-ssm-agent to 3.1.1208.0
How to use
To validate this PR, run ebuild.
In case integration tests are required, a flatcar image containing this ebuild needs to be run on a EC2 instance.
Testing done
changelog/directory (user-facing change, bug fix, security fix, update)It looks like https://github.com/flatcar-linux/coreos-overlay/blob/main/dev-lang/go/go-1.12.17-r1.ebuild can also drop after merge.
Upstream is using go 1.17, too. aws/amazon-ssm-agent@8d1f6de