-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Contrib to v0.103.0 #1247
Conversation
b402a86
to
29ab202
Compare
This PR was marked stale due to lack of activity. |
69ff0c6
to
adf4ac1
Compare
adf4ac1
to
8d7cf3a
Compare
branch named with v102 but eventually bumped to v103. Is it just us trying to pulling in whatever is the latest? (just curious if it's fully intended, not against it at all) |
Initially it we were migrating to v102 but due to parity issue between v102.1 and v102.0 we have decided to bump to v103. I renamed the PR but did not recreate the branch |
ba5852d
to
4e42bbe
Compare
e722595
to
e24a216
Compare
Description of the issue
Contrib was last updated 2 months ago. Contrib repository PR can be found here. Please do not merge before that PR.
Description of changes
Upgrade contrib to v0.103.0 stable version. To do that I had do:
component.UnmarshalConfig
was deprecated so I had to migrate it toconfmap.Unmarshal
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Ran integration test here: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/10063006520
More recent integration test here:https://github.com/aws/amazon-cloudwatch-agent/actions/runs/10101543388
Latest agent logs:
after my changes:
Requirements
Before commit the code, please do the following steps.
make fmt
andmake fmt-sh
make lint