Add appinspect rest support #64
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
support. Initial stub support for appinspect api
api usgae in python. Just need to check for final results and do final error handling
to disk, but we sstill need to fully parse them and fail on any warnings. There are also some contentctl issues we need to account for so that it does not throw failures.
and app.conf files to resolve appinspect issues.
sure directory has correct name and that build is always updated with current utc timestamp.
Check for non-ascii characters and extra spacing in string fields.
for ascii or newline encoding issue
usage in contentctl test. Re add notable/message parsing and validation
permanently until there is a new version.
|
Tested locally and the report look fine :)
|
patel-bhavin
approved these changes
Oct 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow contentctl build and contentctl test to directly run AppInspect via the REST API.
This eliminates the need for users to write their own shell script (or otherwise) to accomplish this vetting before deploying to their own Splunk Cloud Environment.