content_test.yml is gone, can not set new docker ports
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
if a local splunkd or a local proxy is running on your machine or other things that might be listening to your local ports 8000,8088,8089 etc. ..running contentctl test does not work as it can't bind to those ports. Need a way to pass in alternate ports or a way to configure this. IE: Bring the content_test.tml back.
https://github.com/splunk/contentctl/blob/main/contentctl/objects/config.py#L394
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
Start with contentctl/objects/config.py around line 394 and trace how contentctl test obtains its Docker port settings. Confirm how the missing content_test.yml or referenced content_test.tml was used, then make alternate ports configurable and verify that tests can run while ports 8000, 8088, or 8089 are already occupied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100