Pacific Power exclusion endpoint

[s-egge]

Added an endpoint to retrieve all Pacific Power Meters in the pacific_power_exclusion table of the database.

See also:
#313
OSU-Sustainability-Office/automated-jobs#47

Testing

• Run backend locally (sam local start-api from backend directory)
• Visit http://http://localhost:3000/ppexclude
• There are only two meters in the database for now, one to be excluded and one to be included
  

TODO

• Update PacificPower scraper in automated-jobs repo to retrieve exclusion list and use it to decide whether or not to upload data for each meter
  • If a meter is not on the exclusion list, that means it's a new meter, update scraper to add meter with exclude field of new
• Add endpoint for adding a new meter to the database with new in exclude field
• Cloudwatch alert for any new meters added
• Add all existing Pacific Power meters to the table (I am holding off on this for now to make sure we want the current table/naming structure)

[s-egge]

Changes

See this PR in automated jobs to test the endpoint. The new endpoint adds new meters to the table with a status of new, the provided pacific_power_meter_id, and today's date for date_added.

I altered the database structure to have status instead of exclude as the field name, and it now has the following options for values:

• exclude
• include
• new

[solderq35]

Looks good to me, most of my feedback was on the automated-jobs side. Tested the upload functionality with an early breakpoint.

upload-test-breakpoint-518.txt

As you can see by the RESPONSE... logs at the bottom of attached log file above, 2 uploads were made to pacific_power_exclusion table, as expected (2 new meters).

[solderq35]

Follow-up task (future PR): OSU-Sustainability-Office/automated-jobs#51