-
Notifications
You must be signed in to change notification settings - Fork 241
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
Move Lambdacomponents to aws-otel-lambda #1884
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM let's make sure that any changes to the lambda release process is captured as well
|
@Aneurysm9 was suggesting to add a deprecation warning first before removing altogether. |
Here are instructions for deprecating https://go.dev/ref/mod#go-mod-file-module-deprecation |
This PR is stale because it has been open 30 days with no activity. |
Closed in favor of #1981 |
Description:
This PR is in pair with aws-observability/aws-otel-lambda#481 which moves over the lambdacomponents module from aws-otel-collector to aws-otel-lambda
Testing:
Built the collector layer locally.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.