When user tries to edit a resource via YAML editor, while the resrouce is being updated by some other process, user needs to reload the resource manifest in the YAML editor and make those changes again. This behaviour could be a bit frustrating when the resource is being updated frequently and user can not save desired changes due to this behaviour.

As an example, the cluster logging operator frequently updates the status of the ClusterLogging CRs. Every time this happens, the web console reports that the item has changed and suggests a reload. If you are trying to make an edit to a CR where this is the case, the experience is maddening. You have to make your change fast enough that it happens before the CR updates under the covers.

kubectl/oc's edit behavior doesn't have this problem, as some reconciliation of the changes are done on the backend. However, the web interface will NOT let you save your changes because the displayed YAML no longer matches.

Acceptance Criteria

• Consistent behavior with CLI: edits will use PATCH instead of PUT to avoid 409 conflict errors
• Good unit test coverage for various scenarios since this is not something we will test manually often

Non-goals

This story will follow the behavior of the CLI where we simply call patch at the end. It does not include showing a diff to the user and letting them resolve conflicts.