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

libbeat/processors/replace: fix zero string replacement validation #40751

Merged
merged 1 commit into from
Sep 12, 2024

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented Sep 11, 2024

Proposed commit message

The change in #40047 breaks the use of the replace processor to do s/<pattern>// replacement. So make the validation on absence, not zero state.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@efd6 efd6 added Filebeat Filebeat libbeat bugfix Team:Security-Service Integrations Security Service Integrations Team labels Sep 11, 2024
@efd6 efd6 self-assigned this Sep 11, 2024
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Sep 11, 2024
Copy link
Contributor

mergify bot commented Sep 11, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @efd6? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

Copy link
Contributor

mergify bot commented Sep 11, 2024

backport-v8.x has been added to help with the transition to the new branch 8.x.

Copy link
Contributor

mergify bot commented Sep 11, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 11, 2024
@v1v v1v removed the backport-v8.x label Sep 11, 2024
@efd6
Copy link
Contributor Author

efd6 commented Sep 11, 2024

/test

@efd6 efd6 marked this pull request as ready for review September 11, 2024 22:32
@efd6 efd6 requested a review from a team as a code owner September 11, 2024 22:32
@efd6 efd6 requested review from belimawr and rdner September 11, 2024 22:32
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6 efd6 merged commit a45a3ac into elastic:main Sep 12, 2024
125 checks passed
@@ -162,6 +162,7 @@ https://github.com/elastic/beats/compare/v8.8.1\...main[Check the HEAD diff]
- Fix credential handling when workload identity is being used in GCS input. {issue}39977[39977] {pull}40663[40663]
- Fix publication of group data from the Okta entity analytics provider. {pull}40681[40681]
- Ensure netflow custom field configuration is applied. {issue}40735[40735] {pull}40730[40730]
- Fix replace processor handling of zero string replacement validation. {pull}[]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I missed this.

mergify bot pushed a commit that referenced this pull request Sep 12, 2024
…40751)

The change in #40047 breaks the use of the replace processor to do
s/<pattern>// replacement. So make the validation on absence, not zero state.

(cherry picked from commit a45a3ac)
@efd6 efd6 mentioned this pull request Sep 12, 2024
6 tasks
efd6 added a commit that referenced this pull request Sep 13, 2024
…placement validation (#40801)

* libbeat/processors/replace: fix zero string replacement validation (#40751)

The change in #40047 breaks the use of the replace processor to do
s/<pattern>// replacement. So make the validation on absence, not zero state.

(cherry picked from commit a45a3ac)

* add missing pr number

---------

Co-authored-by: Dan Kortschak <[email protected]>
@efd6 efd6 added the backport-8.15 Automated backport to the 8.15 branch with mergify label Sep 20, 2024
mergify bot pushed a commit that referenced this pull request Sep 20, 2024
…40751)

The change in #40047 breaks the use of the replace processor to do
s/<pattern>// replacement. So make the validation on absence, not zero state.

(cherry picked from commit a45a3ac)
efd6 added a commit that referenced this pull request Sep 20, 2024
…eplacement validation (#40917)

* libbeat/processors/replace: fix zero string replacement validation (#40751)

The change in #40047 breaks the use of the replace processor to do
s/<pattern>// replacement. So make the validation on absence, not zero state.

(cherry picked from commit a45a3ac)

* add missing pr number

---------

Co-authored-by: Dan Kortschak <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify backport-8.15 Automated backport to the 8.15 branch with mergify bugfix Filebeat Filebeat libbeat Team:Security-Service Integrations Security Service Integrations Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants