You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where the resource status is null, the mock server will apply that change from the diff. A kubernetes server does not seem to do that and instead expects a patch to be issued specifically against the status subresourse.
The text was updated successfully, but these errors were encountered:
shawkins
changed the title
Mock server patch modifies status
Mock server is not aware of status subresource handling
May 8, 2021
Create, replace, and edit/patch will modify the subresource status.
For example if you do something like:
client.customResources(MyResource.class).inNamespace(namespace).withName(name).patch(resource);
Where the resource status is null, the mock server will apply that change from the diff. A kubernetes server does not seem to do that and instead expects a patch to be issued specifically against the status subresourse.
The text was updated successfully, but these errors were encountered: