newrelic / newrelic/serverless-newrelic-lambda-layers
Can the policy and secret created by NewRelicLicenseKeySecret stack be shared?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 61
- Forks
- 49
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 5
Description
Hi
We have multiple services deployed with their own serverless configs and the plugin added. If the first stack deploys the policy and the secret via NewRelicLicenseKeySecret stack. Can these resources be shared by the other services?
When I deploy the second service, I don't see the policy getting attached to the lambda's iamRole. Causing the following errors in the runtime.
Plugin version is 3.5.0 and Serverless framework version is 3.25.1
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
No file or test is named. Inspect how the NewRelicLicenseKeySecret stack creates resources and attaches its policy when a second Serverless service deploys; reproduce with the stated plugin and framework versions. Done means the shared policy is attached to each service's Lambda IAM role and the reported runtime errors no longer occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100