there is not much code in the core of the upstream (implemented in golang) so I need to look closer to figure out how to best implement this. I think ideally we would want some kind of class to generate the correct data structure, although I am not sure this will fit nicely into something like Django where
we would need to use database models and serialization instead.
What I'm doing now is working on Django endpoints to match the spec, then I can test via these tests and even possibly provide the same tests in the library here.
Questions
The following questions are related to translating the reggie client to python-reggie here for the distribution spec.
GetAbsoluteLocation can return nil/None,while Get RelativeLocation returns an empty string. Is this intentional? My thinking is that it would be logical for them to be consistent.
For response.Errors it seems to be important that Errors is defined and not empty. Is it okay if Errors is not defined? Wouldn't a response without errors not pass along this attribute? I'd like to return an empty list either way, and the only real check is if the json parses. And even in that case, couldn't a response come back from a registry without any content to parse?
is HEAD a valid request for a distribution registry?
For the original implementation, it seems to be allowed to create a client with a bad address but for my version I validate this right away so I'm not able to do that full test.
there is not much code in the core of the upstream (implemented in golang) so I need to look closer to figure out how to best implement this. I think ideally we would want some kind of class to generate the correct data structure, although I am not sure this will fit nicely into something like Django where we would need to use database models and serialization instead.
What I'm doing now is working on Django endpoints to match the spec, then I can test via these tests and even possibly provide the same tests in the library here.
Questions
The following questions are related to translating the reggie client to python-reggie here for the distribution spec.
Signed-off-by: vsoch vsochat@stanford.edu