-
Notifications
You must be signed in to change notification settings - Fork 41
fix: support selecting the platform in docker-compose #751
fix: support selecting the platform in docker-compose #751
Conversation
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures
|
@@ -95,6 +95,7 @@ func (sats *StandAloneTestSuite) aStandaloneAgentIsDeployed(image string) error | |||
|
|||
profileEnv["elasticAgentContainerName"] = containerName | |||
profileEnv["elasticAgentConfigFile"] = sats.AgentConfigFilePath | |||
profileEnv["elasticAgentPlatform"] = "linux/amd64" |
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.
This value will be eventually dynamic for ARM/AMD
@@ -359,6 +359,7 @@ func (mts *MetricbeatTestSuite) runMetricbeatService() error { | |||
} | |||
|
|||
env["metricbeatDockerNamespace"] = e2e.GetDockerNamespaceEnvVar() | |||
env["metricbeatPlatform"] = "linux/amd64" |
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.
This value will be eventually dynamic for ARM/AMD
@@ -221,6 +221,9 @@ func sanitizeComposeFile(composeFilePath string, targetFilePath string) error { | |||
return err | |||
} | |||
|
|||
// sets version to 2.4 for testing purpose |
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.
Not testing anymore?
// sets version to 2.4 for testing purpose |
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.
Well, I mean testing the execution of the tests. I added there to explain why we are setting that version there. Maybe it's not clear enough and it could be deleted
The failed test could be considered flaky. Merging |
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
* fix: support selecting the platform in docker-compose * fix: wrong interpolation format * fix: use a docker-compose version for platform * chore: bump all compose files to 2.4 * chore: sanitise Beats compose files to enforce 2.4 compose version
What does this PR do?
It adds the
platform
element to the docker-compose files for metricbeat and the elastic-agent, so that we will be able to target AMD64 or ARM64 (last one in the near future). This change forced us to upgrade compose files versions from 2.3 to 2.4, which is the version whereplatform
attribute appeared.Because of that, all files in the execution must use the same version, so we are updating all compose files in consequence. And that means that when synchronising the Integrations from Beats, we must enforce the 2.4 version too.
Why is it important?
We want to make sure we consume the proper platform. After Beats creating ARM images, we need to make sure we consume the proper platform.
Checklist
make notice
in the proper directory)Author's Checklist
How to test this PR locally
Related issues