serverless / serverless/serverless
Auto-instrumentation breaks if `--org` is set via CLI argument and not in yml
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 46.9k
- Forks
- 5.7k
- Avg merge
- 10h 7m
- Merged PRs (30d)
- 57
Description
Are you certain it's a bug?
- Yes, it looks like a bug
Is the issue caused by a plugin?
- It is not a plugin issue
Are you using the latest v3 release?
- Yes, I'm using the latest v3 release
Is there an existing issue for this?
- I have searched existing issues, it hasn't been reported yet
Issue description
Using sls deploy --org defeats the auto-instrumentation step, so deploying new functions does not auto-instrument them.
Setting it serverless.yml does not have this limitation
Service configuration (serverless.yml) content
n/a
Command name and used flags
n/a
Command output
n/a
Environment information
n/a
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
Read the CLI option handling for sls deploy --org and the auto-instrumentation deployment path; the issue names no source file or test. Reproduce with --org supplied only on the command line, compare with serverless.yml, and consider it done when new functions are auto-instrumented in the CLI-only case with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100