Closes #320

Background

There is still a bit of human overhead when opening Model Configs PRs based on new Prerelease builds.

In this PR, we allow for a new command for Model Deployment Repositories, one of the form:

!update-configs [profile=PROFILE]
# !update-configs  # This is the same as !update-configs profile=default
# !update-configs profile=qa-only

This command will open PRs in a linked model configs repository based on a given profile. A profile is a set of configuration branches to create PRs from, defined in an MDRs config/auto-configs-pr.json file. This file is sourced from the MDR branch, not the default one, meaning users can make modifications in the prerelease PR as they see fit.

This file looks something like:

{
  "$schema": "https://raw.githubusercontent.com/ACCESS-NRI/schema/main/au.org.access-nri/model/deployment/config/auto-configs-pr/1-0-0.json",
  "profiles": {

    "default": {
      "configs_repo": "ACCESS-NRI/access-test-configs",
      "configs": {
        "dev-01deg_jra55_iaf": {
          "checks": {
            "repro": true
          }
        },
        "dev-01deg_jra55_ryf": {
          "checks": {
            "repro": false
          }
        }
      }
    },

    "qa-only": {
      "configs_repo": "ACCESS-NRI/access-test-configs",
      "configs": {
        "dev-01deg_jra55_iaf": {
          "checks": {
            "repro": false
          }
        },
        "dev-01deg_jra55_ryf": {
          "checks": {
            "repro": false
          }
        }
      }
    }
  }
}

and specifies a profile name, a configs repository to source configs from, and a list of configs to generate PRs from. Furthermore, it will run the given checks on the new PR - for example, !test repro.

The PR

• Custom-action-ify the code for getting the number of deployments a MDR PR has had
• Reference the above new action in ci.yml
• Add a new workflow, ci-command-configs.yml, that handles the new !update-configs command

Testing

Testing of the syntax and outputs of the command was done in ACCESS-NRI/ACCESS-TEST#56

Unit Tests were done via pytest

Known Limitations

• If !update-configs is run twice on the same prerelease build, it will throw an error about a PR already existing for that configuration branch. In future, we will add commits to the existing PR instead.
• If the commenter has write permissions on the MDR, they will be able to do !update-configs and by proxy open auto PRs into the linked configs repository. More testing needs to be done with this.

MDR Requirements for Merging

• MDRs wanting to make use of this feature must have a secrets.CONFIGS_REPO_TOKEN that is passed into the entrypoint secrets.configs-repo-token. This token must have pull-requests:write, contents:write for all configs repositories defined in config/auto-configs-pr.json. Speaking of...
• MDRs want to make use of this feature must also have a config/auto-configs-pr.json file in their MDR (either in the PR they want to use the command, or in the default branch. This contains configuration information for the command.