-
Notifications
You must be signed in to change notification settings - Fork 175
Add docker image name template and renamed fips cloud specs #8429
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
Conversation
This pull request does not have a backport label. Could you fix it @pchila? 🙏
|
💛 Build succeeded, but was flaky
Failed CI Steps
History
cc @pchila |
|
Packaging test run https://buildkite.com/elastic/elastic-agent-package/builds/6402 |
Serverless test failure https://buildkite.com/elastic/elastic-agent/builds/22134#019759e7-a7f7-4525-9ea9-5de520a7a4bb/109-484 should be fixed by #8396 TestAPM failed because it looks like APM server wasn't accepting data |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
code changes LGTM, waiting for the CI to be green 🙂
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.
ok I checked the artifacts and I can see that we produce a cloud-oriented one with -fips
at the end. Could you please create a follow-up issue to remove the one with the -fips
in the middle when the one with the proper name makes it in the unified release? 🙂 LGTM
Created #8442 to track the cleanup work for this |
* Add docker image name template and renamed fips cloud specs * Add debug log for saving docker images (cherry picked from commit 79dec1c) # Conflicts: # dev-tools/mage/dockerbuilder.go # dev-tools/mage/pkgtypes.go
* Add docker image name template and renamed fips cloud specs * Add debug log for saving docker images
…ts-oblt-cli * feature/serverless-its-oblt-cli: (51 commits) as agreed let's move the group to the kb.integration pipeline Update .github/workflows/serverless-project.yml ci: invoke serverless integration tests package from BK github-actions: create a serverless project daily [tests] split up serverless and resource leaks integration tests (#8396) chore: Update to elastic/beats@dfdc12e33de0 (#8446) Lock upgrade marker (#8254) build(deps): bump github.com/elastic/elastic-agent-system-metrics from 0.11.12 to 0.11.13 (#8420) Add docker image name template and renamed fips cloud specs (#8429) buildkite(scripts): refactor common scripts (#8365) Use require.Eventually to try and address flakiness (#8421) Fix pre-command to support extended testing (#8418) [Automation] Bump Golang version to 1.24.4 (#8384) chore: Update to elastic/beats@aed2a8b768bd (#8423) [main][Automation] Update versions (#8425) Add Pipeline to deploy custom agent image for FIPS testing (#8035) ci: automatically update OTel components (#8288) [Automation] Bump VM Image version to 1749258065 (#8390) fix: increase context timeout to accommodate for slower machines in Test_checkForUnprivilegedVault (#8374) otel: add cumulativetodeltaprocessor to EDOT collector (#8372) ...
What does this PR do?
This PR adds FIPS artifacts
elastic-agent-cloud-fips*
alongside the existingelastic-agent-fips-cloud*
to ease scripting around fips/non-fips capable image variants.Introduced a new optional packaging spec setting
docker_image_name_template
where a go template can be specified to control the rendered name of the docker image.Why is it important?
Simplify scripting around fips/non-fips capable docjer image names.
Checklist
[ ] 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 testDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself