We currently have several roles where the opensearch, opensearch-dashboards, logstash-oss, and logstash-plugins packages are installed.
In order to support a greater range of OpenSearch cluster versions, particularly under Kubernetes, we are planning to implement T407123: Mirror OpenSearch repos from upstream.
This will bring about a change to the contents of the thirdparty/opensearch2repository behaves.
Specifically, our current version of this repository only has one version of each of these packages.
For example, here is the current state of thirdparty/opensearch2 for the bookworm-wikimedia distribution.
btullis@apt1002:~$ sudo -i reprepro -C thirdparty/opensearch2 list bookworm-wikimedia bookworm-wikimedia|thirdparty/opensearch2|amd64: elasticsearch-curator 5.8.5-1~wmf5+deb12u1 bookworm-wikimedia|thirdparty/opensearch2|amd64: logstash-oss 1:7.16.3-1 bookworm-wikimedia|thirdparty/opensearch2|amd64: logstash-plugins 7.16.3-1 bookworm-wikimedia|thirdparty/opensearch2|amd64: opensearch 2.7.0 bookworm-wikimedia|thirdparty/opensearch2|amd64: opensearch-dashboards 2.7.0 bookworm-wikimedia|thirdparty/opensearch2|i386: logstash-plugins 7.16.3-1
However, as shown during our investigation in T403301#11197942, the upstream repositories contain many versions of each of these packages.
Therefore, in order to prevent unwanted package upgrades after syning the repositories, we need to pin the versions of opensearch and logstash related packages before syncing the upstream opensearch2 repositories.
Note that elasticsearch-curator will also need to be moved to its own apt component, since this is not present in the upstream opensearch repositories.