Open m-mohr opened 1 week ago
This route needs to be implemented as noted in the ticket I just created #16 and along with that I think #17 would also wrap up nicely the typically expected routes to be implemented for the data proxy.
Better error handling and messaging is also something that still needs to be done, I've started some work on this in a branch I've been working on here. This work is related to the major refactor I mentioned in the ticket #1. I haven't had much time recently to continue working on that so work has pretty much stalled out on that front. Happy for someone to take over that branch since I don't foresee me getting that finished in the near term, maybe @navdeepg2021?
This route needs to be implemented as noted in the ticket I just created #16 and along with that I think #17 would also wrap up nicely the typically expected routes to be implemented for the data proxy.
Better error handling and messaging is also something that still needs to be done, I've started some work on this in a branch I've been working on here. This work is related to the major refactor I mentioned in the ticket #1. I haven't had much time recently to continue working on that so work has pretty much stalled out on that front. Happy for someone to take over that branch since I don't foresee me getting that finished in the near term, maybe @navdeepg2021?
I think it will be great to add some comments on what's not done right. I do see a single TODO in code for mapping APIerrors to Http errors! Was there anything else which can be documented for anybody to address?
Description of Bug: The command
aws s3 ls
gives a weird errorSteps to Reproduce:
aws s3 ls
Expected Behavior: It should work or provide a more meaningful error, why it doesn't work.
Actual Behavior: see above
Screenshots: -
Additional Context: -