newrelic / newrelic/newrelic-lambda-cli
there is no way to specify NewRelicLicenseKeySecret policy name
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 52
- Forks
- 54
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 3
Description
Summary
Desired Behaviour
Possible Solution
Additional context
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
Begin by tracing how the CLI handles the NewRelicLicenseKeySecret policy during the AWS Lambda installation flow. The issue provides no target file, entry point, test, desired behavior, or acceptance criteria, so clarify the expected policy-name option before defining the implementation and coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cli, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100