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

[fleet] Require elastic packages with minimum spec version 3.0 by default #204542

Closed
wants to merge 1 commit into from

Conversation

jsoriano
Copy link
Member

Summary

Introduce a minimum spec version by default, set to 3.0. This would be used starting on 9.0.

This is already the minimum spec version for packages in serverless, via the xpack.fleet.internal.registry.spec.min setting.

Restricting by default the use of old spec versions will help us stop supporting them at some point in the future.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Unit or functional tests were updated or added to match the most common scenarios
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

  • Users have custom packages using older versions of the spec. For these cases they could migrate their packages to 3.0, or use xpack.fleet.internal.registry.spec.min to allow older versions of the spec.
  • Some package maintained by elastic is not migrated. We would have time to migrate all required packages to 3.0. This would be needed in any case for their availability in serverless offerings.

@jsoriano jsoriano added release_note:breaking backport:skip This commit does not require backporting labels Dec 17, 2024
@jsoriano jsoriano self-assigned this Dec 17, 2024
@elasticmachine
Copy link
Contributor

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!

@@ -26,6 +26,7 @@ import { BULK_CREATE_MAX_ARTIFACTS_BYTES } from './services/artifacts/artifacts'
const DEFAULT_BUNDLED_PACKAGE_LOCATION = path.join(__dirname, '../target/bundled_packages');
const DEFAULT_GPG_KEY_PATH = path.join(__dirname, '../target/keys/GPG-KEY-elasticsearch');

const REGISTRY_SPEC_MIN_VERSION = '3.0';
Copy link
Member Author

Choose a reason for hiding this comment

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

Or we could use a 2.x version so it is a less breaking change.

@jsoriano
Copy link
Member Author

Change not needed anymore.

@jsoriano jsoriano closed this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting release_note:breaking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants