In our future configuration file we should add the concept of a 'profile' that can be used to match for many of the other features that we want. For example, we should be able to define a profile for a compose (based on all of the different qualities of a compose that is no longer running) and match on that profile.

For example if I want to create a profile for cloud composes in f29 that are FINISHED_INCOMPLETE. I should be able to do that and then match on it for other things like applying tags or CCing specific people in the ticket. Here is an example:

profile f29-cloud-incomplete
    type: *
    version: 29
    name: Fedora-Cloud
    status: FINISHED_INCOMPLETE
cc:
    - dustymabe: f29-cloud-incomplete

We can grab most of the info from the compose info json:

{
    "header": {
        "type": "productmd.composeinfo",
        "version": "1.2"
    },
    "payload": {
        "compose": {
            "date": "20190627",
            "final": false,
            "id": "Fedora-Cloud-30-20190627.0",
            "label": "RC-20190627.0",
            "respin": 0,
            "type": "production"
        },
        "release": {
            "internal": false,
            "name": "Fedora-Cloud",
            "short": "Fedora-Cloud",
            "type": "ga",
            "version": "30"
        },
        "variants": {}
    }
}

This is a gross simplification, but I think it is very important that we create this profiles concept and plumb it through to the other features we are proposing.