fix: exclude read-only fields from service update requests

[juztim]

Summary

Fixes 422 Unprocessable Content errors when updating coolify_service resources.

Problem

The Coolify API rejects PATCH requests to /services/{uuid} that include read-only fields:

• server_uuid
• project_uuid
• environment_name
• environment_uuid
• destination_uuid

The auto-generated UpdateServiceByUuidJSONRequestBody includes these fields as required (not omitempty), causing every update to fail with:

Received 422 Unprocessable Content updating service: uuid=xxx. Details: 
{"message":"Validation failed.","errors":{
  "destination_uuid":["This field is not allowed."],
  "environment_name":["This field is not allowed."],
  ...
}}

Solution

• Create a custom ServiceUpdateRequest struct with only mutable fields (name, description, docker_compose_raw, instant_deploy)
• Use UpdateServiceByUuidWithBody to send a custom JSON payload instead of the generated type

Testing

Tested against Coolify v4.x API - updates now succeed without 422 errors.

[SierraJC]

Thanks for the fix @juztim , looks good!

I try to keep upstream API related fixes in the tools/overlay.yml file (this modifies the api spec), which is the source of the auto-generated UpdateServiceByUuidJSONRequestBody object. So you could define the "correct" update body in there for consistency, while waiting for the upstream to be fixed. What do you think?

[juztim]

I moved the service update fix into tools/overlay.yml so the generated UpdateServiceByUuid request body no longer includes the read-only fields, and docker_compose_raw stays required. Regenerated the OpenAPI client + provider code, then switched the service update call back to UpdateServiceByUuidWithResponse using the generated type. Commit: 8c245e3.