[alexadereyko]

Brief

Let staging-check find stagings by the annotations of their packages, a revision among them, and return references to the packages found.

Overview

Stagings are no longer tagged by commit, so a staging is asked for by what it was built from. A request has the form of a staging-pull entry; its annotations are globs over the annotations of the packages, which carry the revision of their build and of their dependencies:

[
  {
    "artifact": "core-linux-x86_64",
    "packages": [
      {
        "path": "ghcr.io/openDAQ/$CHANNEL/staging/opendaq",
        "annotations": {
          "org.opencontainers.image.revision": "$CORE_REF",
          "com.opendaq.custom.platform": "linux",
          "com.opendaq.settings.arch": "x86_64"
        },
        "optional": false
      }
    ]
  }
]

Every index of the package is looked at; the answer is the matching packages of the newest index that has any. A request nothing answers is an error, or a warning when it is optional. artifact may be left out.

The resolved output is the request with every package replaced by references to the packages found:

[
  {
    "artifact": "core-linux-x86_64",
    "packages": [
      { "path": "ghcr.io/opendaq/dev/staging/opendaq@sha256:<digest>" }
    ]
  }
]

test-staging resolves what it published by revision, by the core a module was built against and for several packages at once, and checks that a missing staging fails.

Caller migration

The input changed: a request is a staging-pull entry, and a staging is named by annotations instead of a tag. check-core-staging.yml in the module repositories moves to the new form.