You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the detection rules release process, I noticed Elastic Package repository had documentation on Package Storage v2 and the differences between v1 and v2.
At the moment, we have two dependencies on Package Storage v1 that we may need to revisit and make adjustments according to Package Storage v2 since they are planning to deprecate v1.
detection rules releasing for OOB integrations package
related integrations post-build for rules and it's backend dependencies such as integrations manifest which pulls from Package Storage v1
The text was updated successfully, but these errors were encountered:
Seems like the v2 CDN allows you to specify the package and return all of it's versions. This will be useful for building the integrations manifest by looking at our current in-use integrations for rules (already done) then adjusting the URL to pull from with all=true in the URI, we can then find the path for each version and then adjust the URL to get the manifest of that package.
terrancedejesus
changed the title
[Bug] Revisit Package Storage and Elastic Package Dependencies
[Enhancement] Review "integrations-pr" CLI Command for Enhancements and Package Storage v2
Jan 26, 2023
Overview
During the detection rules release process, I noticed Elastic Package repository had documentation on Package Storage v2 and the differences between v1 and v2.
Reference: https://github.com/elastic/elastic-package/blob/main/docs/howto/use_package_storage_v2.md
At the moment, we have two dependencies on Package Storage v1 that we may need to revisit and make adjustments according to Package Storage v2 since they are planning to deprecate v1.
The text was updated successfully, but these errors were encountered: