Allow Splunkbase or Private Apps in Versioning Checking
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Only ESCU is supported at this time for enforcing the new Versioning Checks.
We should consider if we want to support:
- Other apps on Splunkbase; and
- Private apps that are not on Splunkbase
See the following discussion in the PR which adds Versioning Enforcement: https://github.com/splunk/contentctl/pull/280/files#r1752846568
We will also need to check for different comments in the savedsearches.conf file based on the name of the app: https://github.com/splunk/contentctl/pull/280/files#r1752740324
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 the versioning-enforcement changes and discussion in PR #280, then inspect the savedsearches.conf comments referenced there. Determine the expected behavior for Splunkbase apps and private apps, including app-specific comments, and use the existing enforcement checks as the baseline for completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100