notationlabs / notationlabs/notation
Pass runtime config to resource provider
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 54
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Currently, the config that can be defined in runtime modules is not being passed through when the resource is provisioned.
- The config types should include all lambda configuration properties appropriate to expose.
- These properties should map to the lambda schema defined in packages/aws/src/lambda.fn/config.ts.
- The esbuild plugin should be changed so that it doesn't pass the config as a spread parameter
- The config should be picked up in packages/aws/src/lambda/lambda.ts and passed into the resource
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.
Research direction
Start by comparing the config types in packages/aws/src/lambda.fn/config.ts with the Lambda schema in packages/aws.iac/src/resources/lambda/lambda.ts. Trace how packages/esbuild-plugins/src/plugins/function-infra-plugin.ts passes configuration and how packages/aws/src/lambda/lambda.ts provisions the resource; done means exposed runtime properties are mapped through without spreading the config parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, nodejs, typescript
- Domain
- backend, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100