Skip to content

[8.x](backport #7486) Skip FIPS components when packaging elastic-agent from a Manifest#7546

Merged
jlind23 merged 1 commit into8.xfrom
mergify/bp/8.x/pr-7486
Mar 25, 2025
Merged

[8.x](backport #7486) Skip FIPS components when packaging elastic-agent from a Manifest#7546
jlind23 merged 1 commit into8.xfrom
mergify/bp/8.x/pr-7486

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Mar 25, 2025

What does this PR do?

ChecksumsWithManifest function assumes that all (actually only one) packages matching a component binary name prefix and the target platform are downloaded and available but since -fips packages are available in manifests this is no longer true (see endpoint-security-fips-9.1.0-SNAPSHOT-linux-x86_64.tar.gz and endpoint-security-9.1.0-SNAPSHOT-linux-x86_64.tar.gz which are both present in recent manifest versions).

This is a short term hack to avoid breaking elastic-agent packaging now that -fips package variants are available by skipping them.

Why is it important?

To be able to generate elastic-agent packages again

Checklist

  • [ ] I have read and understood the pull request guidelines of this project.
  • [ ] 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/fragments using the changelog tool
  • [ ] I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

This is an automatic backport of pull request #7486 done by [Mergify](https://mergify.com).

)

ChecksumsWithManifest function assumes that all (actually only one)
packages matching a component binary name prefix and the target platform
are downloaded and available but since -fips packages are available in
manifests this is no longer true (see
endpoint-security-fips-9.1.0-SNAPSHOT-linux-x86_64.tar.gz and
endpoint-security-9.1.0-SNAPSHOT-linux-x86_64.tar.gz which are both present
in recent manifest versions).

This is a short term hack to avoid breaking elastic-agent packaging now that
-fips package variants are available.

(cherry picked from commit ab1a614)
@mergify mergify bot requested a review from a team as a code owner March 25, 2025 15:34
@mergify mergify bot added the backport label Mar 25, 2025
@mergify mergify bot requested review from kaanyalti and ycombinator and removed request for a team March 25, 2025 15:34
@mergify mergify bot assigned pchila Mar 25, 2025
@github-actions github-actions bot added bug Something isn't working Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team skip-changelog labels Mar 25, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

@jlind23 jlind23 enabled auto-merge (squash) March 25, 2025 15:36
@elastic-sonarqube
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@jlind23 jlind23 merged commit b1c867e into 8.x Mar 25, 2025
14 checks passed
@jlind23 jlind23 deleted the mergify/bp/8.x/pr-7486 branch March 25, 2025 17:54
@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

cc @pchila

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport bug Something isn't working skip-changelog Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants