Skip to content

fix(auditbeat system/package): handle empty package.v1 bucket#44296

Merged
andrewkroh merged 1 commit intoelastic:mainfrom
andrewkroh:auditbeat/fix/system-package-schema-migrations
May 9, 2025
Merged

fix(auditbeat system/package): handle empty package.v1 bucket#44296
andrewkroh merged 1 commit intoelastic:mainfrom
andrewkroh:auditbeat/fix/system-package-schema-migrations

Conversation

@andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented May 9, 2025

Proposed commit message

Ensure the schema migration logic properly handles cases where the package.v1 bucket exists but is empty, avoiding assumptions about the presence of the state_timestamp key.

Fixes #44294

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

@andrewkroh andrewkroh added Auditbeat bugfix backport-active-all Automated backport with mergify to all the active branches labels May 9, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 9, 2025
@andrewkroh andrewkroh added the Team:Security-Linux Platform Linux Platform Team in Security Solution label May 9, 2025
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 9, 2025
Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes elastic#44294
@andrewkroh andrewkroh force-pushed the auditbeat/fix/system-package-schema-migrations branch from 0482c98 to 4b36510 Compare May 9, 2025 15:00
@andrewkroh andrewkroh marked this pull request as ready for review May 9, 2025 15:25
@andrewkroh andrewkroh requested a review from a team as a code owner May 9, 2025 15:25
@elasticmachine
Copy link
Contributor

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

@andrewkroh andrewkroh merged commit d7332ab into elastic:main May 9, 2025
29 of 32 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented May 9, 2025

@Mergifyio backport 8.17 8.18 8.19 9.0

@mergify
Copy link
Contributor

mergify bot commented May 9, 2025

mergify bot pushed a commit that referenced this pull request May 9, 2025
Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)
mergify bot pushed a commit that referenced this pull request May 9, 2025
Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)
mergify bot pushed a commit that referenced this pull request May 9, 2025
Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)
mergify bot pushed a commit that referenced this pull request May 9, 2025
Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)
andrewkroh added a commit that referenced this pull request May 9, 2025
#44301)

Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
andrewkroh added a commit that referenced this pull request May 9, 2025
…ackage.v1 bucket (#44299)

Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
andrewkroh added a commit that referenced this pull request May 9, 2025
…ackage.v1 bucket (#44300)

Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
andrewkroh added a commit that referenced this pull request May 9, 2025
…ckage.v1 bucket (#44302)

Ensure the schema migration logic properly handles cases where the package.v1
bucket exists but is empty, avoiding assumptions about the presence of the
state_timestamp key.

Fixes #44294

(cherry picked from commit d7332ab)

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auditbeat backport-active-all Automated backport with mergify to all the active branches bugfix Team:Security-Linux Platform Linux Platform Team in Security Solution

3 participants