suggestion (non-blocking): It might be worth just updating the model.final_model dbt seed to capture this list and its attributes. That seed only gets updated at the end of each year, so we could just basically down > up the compose stack to get the new endpoint, rather than modifying the code.
We should factor out the logic from api-res-avm that determines various attributes for each year of the model API and move it into the model.final_model seed.
Originally suggested by @dfsnow here
We should factor out the logic from
api-res-avm
that determines various attributes for each year of the model API and move it into themodel.final_model
seed.