The CI pipeline already creates it's own inputs.root-sbd default (essentially inputs.model-name), as it is required for editing the modulefile name to be in pr format for Prereleases.
The CD pipeline also requires this, but we hadn't added it. Details on the underlying cause are in the linked issue.
In this PR:
Made cd.yml set a dynamic inputs.root-sbd default based on inputs.model
Made all inputs.root-sbd required
[x] We will also have to delete and manually upload the meta-db entries that did not contain the correct model name. Currently, that seems to be all deployed models last month.
[x] Will also need to link a ACCESS-NRI/access-esm1.5 PR that adds the (now required) inputs.root-sbd argument.
@utkarshgupta95 would you be able to list the entries for the build provenance DB? I suspect that there will be a bunch of mom5 models in there as a model rather than as a component.
This issue stems from this line: https://github.com/ACCESS-NRI/build-cd/blob/d7c57427766587787f130fe84ad455cde1752fcc/.github/workflows/deploy-2-start.yml#L33 We cannot set dynamic defaults like this, only a basic string default.
The CI pipeline already creates it's own
inputs.root-sbd
default (essentiallyinputs.model-name
), as it is required for editing the modulefile name to be inpr
format for Prereleases. The CD pipeline also requires this, but we hadn't added it. Details on the underlying cause are in the linked issue.In this PR:
cd.yml
set a dynamicinputs.root-sbd
default based oninputs.model
Made all
inputs.root-sbd
requiredmeta-db
entries that did not contain the correctmodel
name. Currently, that seems to be all deployed models last month.ACCESS-NRI/access-esm1.5
PR that adds the (now required)inputs.root-sbd
argument.Closes #102