AWS .NET Mock Lambda Test Tool should set AWS_LAMBDA_FUNCTION_VERSION environment variable
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start by locating the AWS .NET Mock Lambda Test Tool and its environment setup path. Check how launch-time environment variables are assigned, then verify that AWS_LAMBDA_FUNCTION_VERSION is present when a function runs and that the OpenTelemetry AWS Lambda resource detector no longer needs a workaround.
Written by the indexing model from the issue text.
Description
Describe the feature
AWS .NET Mock Lambda Test Tool should set AWS_LAMBDA_FUNCTION_VERSION environment variable
Use Case
When instrumenting AWS Lambda functions with OpenTelemetry, this environment variable is used by the provided OpenTelemetry resource detector for AWS Lambda. If not set, the resource-detector throws an exception when configuring the TracerProviderBuilder. One needs to workaround, setting the environment variable e.g. within the launch options for the test tool.
Proposed Solution
AWS Lambda Test Tool should set AWS_LAMBDA_FUNCTION_VERSION environment variable
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
AWS .NET SDK and/or Package version used
Version shipped with AWS Toolkit for Visual Studio 2022 v 1.43.00
Targeted .NET Platform
.NET 6
Operating System and version
Windows 11
- Dominant language
- C#
- Stars
- 1.7k
- Forks
- 503
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 21
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-lambda-dotnet
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
aws/aws-lambda-dotnet#2571 · 1 comment ·
-
bug module/aspnetcore-support p2 queued
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws/aws-lambda-dotnet#1123 · 4 comments · 1 reaction ·
-
feature-request
Difficulty 4/5 3-5 days Newbie friendliness 68/100
aws/aws-lambda-dotnet#2572 · 1 comment ·
-
feature-request needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
aws/aws-lambda-dotnet#2551 · 1 comment ·
-
feature-request needs-review
Difficulty 5/5 Over a week Newbie friendliness 35/100
aws/aws-lambda-dotnet#2519 ·
All issues in aws/aws-lambda-dotnet
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·