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
Currently, some of the third-party integrations Docker Compose projects use hard-coded values for the services versions. To ease their maintenance, these versions must be controlled via the .env file.
On the other hand, we need to implement a version control strategy for the integrations. We will use the latest version possible for each of the services (OpenSearch, Splunk, Elastic, ...). As it's possible that the courtesy dashboards break on recent versions, we need to keep a compatibility matrix for them, describing the version of the dashboard and the supported product versions.
Tasks
Centralize services versioning.
Upgrade services to the latest version available and check that the integrations work.
The text was updated successfully, but these errors were encountered:
Description
Currently, some of the third-party integrations Docker Compose projects use hard-coded values for the services versions. To ease their maintenance, these versions must be controlled via the
.env
file.On the other hand, we need to implement a version control strategy for the integrations. We will use the latest version possible for each of the services (OpenSearch, Splunk, Elastic, ...). As it's possible that the courtesy dashboards break on recent versions, we need to keep a compatibility matrix for them, describing the version of the dashboard and the supported product versions.
Tasks
The text was updated successfully, but these errors were encountered: