[BUG] REST Status code for updating a workflow conflicts with RFC Guidance

[dbwiddis]

What is the bug?

We currently return 201 (Created) for updating a template. RFC 9110 requires (MUST) either 200 (OK) or 204 (No Content) in this case:

If the target resource does not have a current representation and the PUT successfully creates one, then the origin server MUST inform the user agent by sending a 201 (Created) response. If the target resource does have a current representation and that representation is successfully modified in accordance with the state of the enclosed representation, then the origin server MUST send either a 200 (OK) or a 204 (No Content) response to indicate successful completion of the request.

How can one reproduce the bug?

Update a workflow template.

What is the expected behavior?

Response code of 200 or 204.

Do you have any screenshots?

Do you have any additional context?

OpenSearch's UpdateResponse returns 201 (Created), so we are consistent with them, and they probably shouldn't change to remain compatible. So maybe we should just leave this as-is and close this issue.

[joshpalis]

Closing this issue to remain compatible with OpenSearch update API rest status