Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Splunkbase or Private Apps in Versioning Checking #283

Open
pyth0n1c opened this issue Sep 10, 2024 · 0 comments
Open

Allow Splunkbase or Private Apps in Versioning Checking #283

pyth0n1c opened this issue Sep 10, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@pyth0n1c
Copy link
Contributor

pyth0n1c commented Sep 10, 2024

Only ESCU is supported at this time for enforcing the new Versioning Checks.
We should consider if we want to support:

  1. Other apps on Splunkbase; and
  2. 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

@pyth0n1c pyth0n1c added the enhancement New feature or request label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant