-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Peru OEFA adapter #1085
Peru OEFA adapter #1085
Conversation
credentials need to be added to env as `SOURCE_NAME_CREDENTIALS`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you
- update this to use our request client
- add docstrings
- change the parameters const at the top to follow the same pattern as what we are doing in the rwanda adapter. Use the object as a map to make sure we are getting the right units.
And dont hesitate to reach out if any of that is unclear or you just have questions.
@caparker I added docstrings and will update the documentation. I was having a hard time getting the client to work with the custom errors we have, so I left |
Also some util methods and guides
* set `active:false` all eea-direct adapters and South Africa * Set `active:false` for Bosnia_Tuslanski and Montenegro --------- Co-authored-by: Gabriel Fosse <kraken+majesticio@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Peru OEFA fetch adapter. Added custom error if an incorrect user / or password is used, and some debug statements for empty responses. This is because all responses from the API return
status 200
even if the wrong credentials are used. Waiting on source to confirm the dates are accurate before deploying as the measurements are all ~12+ hours old.