splunk / splunk/splunk-example-ta
Use .venv for modinput tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 4
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 2
Description
Update https://github.com/splunk/splunk-example-ta/blob/main/tests/ucc_modinput_functional/README.md
Once ./scripts/run_locally.sh script is executed, use .venv created by it source .venv/bin/activate - just add one more command to the console section in https://github.com/splunk/splunk-example-ta/blob/1378a9a04905e8edff6bfd0a6dc7354791053c16/tests/ucc_modinput_functional/README.md?plain=1#L5
Contributor guide
No contributing guide indexed for this repository
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
Update tests/ucc_modinput_functional/README.md, specifically its console section. Read the instructions around ./scripts/run_locally.sh, then document sourcing the created .venv with source .venv/bin/activate; the README should show the additional command after running the script.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100