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

contentctl 5 - Step 4 - ESCU 5.0 #334

Merged
merged 169 commits into from
Jan 18, 2025
Merged

contentctl 5 - Step 4 - ESCU 5.0 #334

merged 169 commits into from
Jan 18, 2025

Conversation

pyth0n1c
Copy link
Contributor

@pyth0n1c pyth0n1c commented Dec 4, 2024

contentctl 5 will contain a number of changes.
Instead of targeting PRs at main, they will be targeted at this branch

@josehelps josehelps changed the title contentctl 5 contentctl 5 - Step 5 - ESCU 5.0 Jan 15, 2025
@josehelps josehelps changed the title contentctl 5 - Step 5 - ESCU 5.0 contentctl 5 - Step 4 - ESCU 5.0 Jan 16, 2025
cmcginley-splunk and others added 22 commits January 15, 2025 16:32
…red code w/ comments for cleanup before merge
Improve lookup regex - Step 1 - ESCU 5.0
prevent false positively flagging a
field named hellolookup=something
as a lookup.
Also, enforces lookup validation
in the search field of baselines.
Migrate integration testing to RBA paradigm - Step 2
DRAFT: new RBA Object - Step 3 - ESCU 5.0
First crack at default config for `ruff` - Step 3.5 - ESCU 5.0
…ected. This occurred in a rare instance where a search was looking for using of the literal 'lookup *'
at once instead of one at a
time. this reverts the behavior
to what it used to be like.
also, fix the filename
written out in transforms.j2
for a file-backed lookup
such that it contains the datetime
stamp of the modifications.
finally, ruff reformatted
the conf_writer.py file,
so lots of formatting changes.
contentctl 5 being an alpha.
change the version in
pyproject to
5.0.0-alpha
@pyth0n1c pyth0n1c removed the Draft label Jan 18, 2025
@pyth0n1c pyth0n1c merged commit c75f3cd into main Jan 18, 2025
12 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants