I am starting to spec out the design for how we will be using extractors to generate compatibility artifacts. Since compatibility is subjective for a particular community or experiment, the high level idea is that the user provides a specification that says "map these extractor metadata attributes into the compatibility structure that I care about." That might look like this:
This is WIP because likely I'll write the (complete) create command to output an artifact (json blob) that is validated by our compspec.json. High level, in a CI workflow we would build the container image, run this create command against it (with our yaml specification) and then generate the artifact to push to the registry. The artifact is then paired with the image and used with the compspec tool on the image selection step.
I am starting to spec out the design for how we will be using extractors to generate compatibility artifacts. Since compatibility is subjective for a particular community or experiment, the high level idea is that the user provides a specification that says "map these extractor metadata attributes into the compatibility structure that I care about." That might look like this:
This is WIP because likely I'll write the (complete) create command to output an artifact (json blob) that is validated by our compspec.json. High level, in a CI workflow we would build the container image, run this create command against it (with our yaml specification) and then generate the artifact to push to the registry. The artifact is then paired with the image and used with the compspec tool on the image selection step.