Release v4.1.0 #172
Merged
Release v4.1.0 #172
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
This ensures that detections show up as content in the Enterprise Security UI in Splunk
Updates the requirements on [setuptools](/~https://github.com/pypa/setuptools) to permit the latest version. - [Release notes](/~https://github.com/pypa/setuptools/releases) - [Changelog](/~https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v69.5.1...v70.0.0) --- updated-dependencies: - dependency-name: setuptools dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…l must occur somewhere in the search.
Add testing against 3.9 and 3.10 to the github actions test workflow.
WHY certain macros are excluded when we look for them.
verbose error printing to the terminal. This should make most operations easier to understand since the vast majority of errors are due to bad yml fields (or missing).
verbose logging is not enabled.
Add verbose error option
Cleaning up output order
…5.1-and-lt-71.0.0
Removing Bias Language and updating templates
repo to catch additonal errors with more content
…5.1-and-lt-71.0.0 Update setuptools requirement from ^69.5.1 to >=69.5.1,<71.0.0
Updates the requirements on [setuptools](/~https://github.com/pypa/setuptools) to permit the latest version. - [Release notes](/~https://github.com/pypa/setuptools/releases) - [Changelog](/~https://github.com/pypa/setuptools/blob/main/NEWS.rst) - [Commits](pypa/setuptools@v69.5.1...v70.0.0) --- updated-dependencies: - dependency-name: setuptools dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
add testing against security_content repo
direct interface to contentctl functions!
Ensure detections show up in the ES app
However, there are issues with the API availability/stability that we must overcome.
Now only the CVE id and the url, a new field, will be populated with the aniticpated values. We have retained the legacy fields to support future enrichment development.
Removing rest_deploy, apav_deploy
JSON objects in the API library.
…5.1-and-lt-71.0.0 Update setuptools requirement from ^69.5.1 to >=69.5.1,<71.0.0
function on security_content_object so that they can be printed out without cycle/recursion issues
casey on PR. Improve naming, address other PEP8 concerns, and move some logic from contentctl.main into contentctl.test_common_func
Add simple API for a more
Improve filter macro checking
Update deps in prep for 4.1
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.
Collect PRs to merge into main for release 4.1.0
This includes a number of updates:
contentctl buildcorrectly without errors. Since this content should all be "correct" this is a good test of the contentctl toolcontentctl newworkflow to fix errors and ensure that fields are written in the correct order.urlfield of the CVE. This is used to link directly to the relevant NIST page and supports faster site build time. It also avoids using the CVESearch tool (and the circl.lu API which is frequently down or has extremely slow, multi-minute response times).