Implement HO golang client API ExtractArtifact(filename string)
#1323
Conversation
| path := "/v1/userartifacts/" + checksum + "_extracted" | ||
| res := &hoapi.StatArtifactResponse{} |
There was a problem hiding this comment.
Currently I'm starting implementation about HO golang client API for extracting user artifact, but I think it's better to have more support on StatArtifactResponse so that retriving an answer whether artifact is extracted or not.
type StatArtifactResponse struct{
Extracted boolean `json:"extracted"`
}
@jemoreira @ser-io To get agreement before implementation, is it good to proceed implementation without additional review regarding this issue on our previous design doc? Thanks!
There was a problem hiding this comment.
You can receive Extracted: false and then receive 409 in the following POST /:extract request, as the server state could change in between those calls.
You rather need to handle 409 response on POST /:extract and don't return error to the function caller when the server returns 409. By doing so, there's no need to have the new field Extracted boolean json:"extracted"`` just rely on the server response on POST /:extract request.
No description provided.