In the case of attaching an already attached volume, how do I get the http status code? about oci-go-sdk

[jasonyin]

The API return two structs, one is response, the other one is err. Would the err works for you?

func (client ComputeClient) AttachVolume(ctx context.Context, request AttachVolumeRequest) (response AttachVolumeResponse, err error)

[MadalinaPatrichi]

The status code of the request is not easily extracted from the error. This used to be available in the response, but it seems like there was an API change. Is this documented anywhere to explain why this has happened and what is the recommended way of extracting the status code in the case of an error. Is this a bug or a feature?

[eginez]

@MadalinaPatrichi. You have a couple of options

• All API respond with an struct and an error type. The error could be an ServiceError in that case you can access the http status code from the type via the GetHTTPStatusCode(). There are other methods in the ServiceError interface you can use. Additionally if the response is not nil, all xxxResponse structs contain the RawResponse field of type http.Response where you can inspect all the details of an http response.
• When the response is nil, then the error is not of type ServiceError and usually means that an error happened before we could execute the network call, errors in the network, marshalling errors, etc fall under that category. Those errors obviously won't have a status code.

You can see some examples of error handling here: https://github.com/oracle/oci-go-sdk/blob/master/example/example_core_test.go#L369

By the sounds of it, it seems like the error you are getting might be client related, and for the record the API to deal with these issues has not changed. Out of curiosity what is the value of your err.String()

[jasonyin]

@MadalinaPatrichi , please let us know if you are still having the issue or not, otherwise, we are going to close it, thanks!

[jasonyin]

@MadalinaPatrichi I am closing this issue, please let us know if you still have questions, thanks!