Major Description
One of the issues we're hitting in the use of Curator is a number of QE requests for versions of projects that are not being built by our build (examples : Quarkus project version being used, EAP project version being used, versions of base images, etc). These are things that are special cases and that I do not think should be directly wired into curator.
A lot of these things are versions that we could slurp out of the dev or PNC build with a perl one liner or sed or something like that, and if we had a mechanism of getting them to curator, wouldn't be a big deal to include. I don't think they make sense to include as part of curator itself though.
Is there some way we can define a build parameter naming convention coming from the UMB message of the dev builds or from the UMB message of PNC where Curator could pick up build parameters, and include them in the list / UMB message, without having any special knowledge about them? Like we define a CURATOR_EAP_VERSION and have that map to a "eap" version? I'm not sure if it makes sense to include it in the artifacts list or maybe make a separate section for parameters?
