Add report log output at end of plugins command
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start at the implementation of the plugins command and trace how plugin files are discovered, imported, and logged. Define the report around discovered plugins, import failures with related errors, and configurable log output, including output produced during imports. Done means the command presents a clear end-of-command report and exposes the requested log-level behavior.
Written by the indexing model from the issue text.
Description
Currently the log output of the plugins command is a bit of a mess. There's no real good way of seeing the warnings that some files weren't importable and scannable for plugins. A nicely formatted report at the end of the command would be useful, containing
- all discovered plugins and their files
- all files that had an error while importing (and the related error)
It would also be useful to configure the loglevel and capture all the output created by simply importing code, similar to pytests' --log-cli-level
- Dominant language
- Python
- Stars
- 76
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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 localstack/plux
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
localstack/plux#36 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100