Motivation
As discussed in https://github.com/CCI-MOC/invoicing-private-data/issues/92, invoicing-private-data now has a few highly structured YAML files with pydantic models to validate them. We should move those models to this repo to avoid duplicating validation logic, which is the case now in loader.py, such as with loading the nonbillable project list. This will also enforce separation between private business data and open source code.
This task is low priority, and I'll likely assign it to the new intern.
CC @knikolla @naved001
Completion Criteria
The pydantic models are defined and used in this repo. invoicing-private-data should then install invoicing to validate its YAML files
Description
Completion dates
Desired - TBD
Required - TBD
Motivation
As discussed in https://github.com/CCI-MOC/invoicing-private-data/issues/92,
invoicing-private-datanow has a few highly structured YAML files with pydantic models to validate them. We should move those models to this repo to avoid duplicating validation logic, which is the case now inloader.py, such as with loading the nonbillable project list. This will also enforce separation between private business data and open source code.This task is low priority, and I'll likely assign it to the new intern.
CC @knikolla @naved001
Completion Criteria
The pydantic models are defined and used in this repo.
invoicing-private-datashould then installinvoicingto validate its YAML filesDescription
invoicingmergedinvoicing-private-datamerged (Depends on first task)Completion dates
Desired - TBD
Required - TBD