operator is a golang build that today, bootstraps its brew build by fetching zips of upstream sources:

• asset-devworkspace-operator.zip
• asset-header-rewrite-traefik-plugin.zip

https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-operator/get-sources.sh#L53-L66

These zips are then unpacked and simply copied into the target image:

https://github.com/redhat-developer/devspaces-images/blob/devspaces-3-rhel-8/devspaces-operator/Dockerfile#L57-L58

So... we would switch to adding a fetch-artifacts-url.yaml file to the mid and downstream repos, per the docs? if not, a fallback method might be to commit the contents of the zips directly into the midstream GH repo, and sync it downstream to pkgs.devel repos.

https://osbs.readthedocs.io/en/latest/users.html#fetch-artifacts-url-yaml

Could also use cachito w/o a package manager to simply fetch sources from the two GH projects (and a commit SHA) so that the sources are available in the downstream repo at build time.

Maybe we can just fetch the single combined.yaml from https://github.com/devfile/devworkspace-operator/blob/main/deploy/deployment/openshift/combined.yaml and the handful of small files from https://api.github.com/repos/che-incubator/header-rewrite-traefik-plugin and commit those to the midstream GH repo for devspace-operator ?