Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mock server is not aware of status subresource handling #3088

Closed
shawkins opened this issue May 7, 2021 · 0 comments · Fixed by #3092
Closed

Mock server is not aware of status subresource handling #3088

shawkins opened this issue May 7, 2021 · 0 comments · Fixed by #3092
Milestone

Comments

@shawkins
Copy link
Contributor

shawkins commented May 7, 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.

@shawkins shawkins changed the title Mock server patch modifies status Mock server is not aware of status subresource handling May 8, 2021
@manusa manusa added this to the 5.4.0 milestone May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants