-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[main] Sync bundled packages with Package Storage #149245
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @terrancedejesus 🙂
@kpollich - Does this PR auto-create anytime there is an updated EPR package that is referenced in the fleet_packages.json file on main for Kibana? I ask because I am currently updated the prebuilt security rules release process and noticed that my PR may have some redundancy that yours is already doing automatically? Reference: #149164 Another question is the logic it does to update the fleet packages reference. Multiple Prebuilt security rule packages, both prerelease and production, will be pushed to EPR during OOB updates and Elastic stack minor releases (~8 packages at least) to be expected going back to -3 and older Kibana versions. Therefore it would probably be best to only allow this to happen for the increased semantic versions into main. For example, main has v8.7.1 and a v8.7.2-beta.1 or v8.7.2 package is available in EPR. |
Yes, this is an automated PR filed from a Buildkite job (linked in the description). Any time a package is published, we compare with
There is some logic that automates this same PR to the appropriate |
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Automated by https://internal-ci.elastic.co/job/package_storage/job/sync-bundled-packages-job/job/main/1469/