Generally, we have been updating edm-recipe datasets via the command line with library archive but a github action was set up to facilitate these uploads that wasn't widely used. When trying to upload the default dcp_mappluto dataset earlier, an assertionerror was thrown because of the way PLUTO datasets are versioned via data library (22v2 or 22v3 as supposed to other datasets which are versioned by the date i.e. 20221121. This PR adds a parameter to the workflow in which the user has to specify a version to upload to data library.
This PR addresses #267. One reviewer required ⭐ .
Generally, we have been updating
edm-recipedatasets via the command line withlibrary archivebut a github action was set up to facilitate these uploads that wasn't widely used. When trying to upload the defaultdcp_mapplutodataset earlier, anassertionerrorwas thrown because of the way PLUTO datasets are versioned via data library (22v2 or 22v3as supposed to other datasets which are versioned by the date i.e.20221121. This PR adds a parameter to the workflow in which the user has to specify a version to upload to data library.To test, I ran the workflow off this branch which can be viewed here: https://github.com/NYCPlanning/db-data-library/actions/runs/3517220403 To confirm this action successfully ran, I checked the edm-recipes space on data library to make sure dcp_mappluto was updated.
Note that a green check, doesn't necessarily mean a successful run as seen in this run of the workflow: https://github.com/NYCPlanning/db-data-library/actions/runs/3516153549