As explained in this part of the API spec, I issued a REPLACE
request.
The request went through and I received a 200 OK
HTTP status code.
- Either ALL the changes succeed and a 2xx response code is returned,
- or NONE of the changes are committed and a 4xx or 5xx code is returned.
According to above quote taken from the specification, my request was valid and was ultimately completely executed.
However, this is not the case. The Rancher Helm App in question remains absolutely untouched. Nothing happens.
Even if something is “wrong” with the request, it should not output a 200 OK
HTTP status code.
I can report this confusing bug as a Github issue, but since the actual problem goes beyond that, I am posting my problem here, first.
The Rancher Helm App that is supposed to be replaced, is retrieved, 2 values in the answers
object are modified (the modified Rancher Helm App is confirmed to be sent to the server correctly, all this has been already debugged) and then it is sent to the server through a REPLACE
request, as defined in the API specification.
Rancher API v3 is used to submit the operation and everything seems to “work”, except it does not, after all.
I cannot use a Rancher API client, because all available clients are outdated, except one, but the one not outdated cannot handle Rancher Helm Apps. It barely can handle anything.
I cannot post the request content here.
How can I make the REPLACE
operation work?