PATCH option for resource azapi_update_resource

[randy-coburn-zeam]

I know after dumpster diving in closed issues that azapi_resource_action is available.

However it seems documented pretty obscurely when you also have azapi_update_resource available. The example doesn't represent the same features that you would use update_resource for.

The name of the resource is important since when you first arrive you see update and think thats what I want. Then spend an a few hours battling why it doesn't work and tries to change everything. resource_action doesn't really sign "I change things" when you first read it.

That is how I interpreted whats going on in docs.

Is it possible that azapi_update_resource could just have a http_method option that is defaulted to "PUT" but at least allows the user to change it to match what the documentation requires.

[ms-henglu]

Hi @randy-coburn-zeam ,

Thank you for taking time to report this issue.

I'll work on improving the documents and investigate the feasibility of supporting Patch method in the azapi_update_resource.

Would you please also share the user-case that you need to use Patch method to update an existing resource?

[randy-coburn-zeam]

In my case I was trying to update the open telemetry settings for a container app environment.

Using patch I can selectively update parts of the config. Using put I need to supply a complete config with my updated changes.

[ms-henglu]

Actually the azapi_update_resource will call GET request to retrieve the current status of the existing resource, then combine with the configuration defined in the body, finally removes the read-only fields and send the PUT request. If so, will it solve your problem?