Andras Bacsai 1683f77f2e fix(api): enable consistent container naming for a custom internal name ...

Since 50268139b the API returned 422 for custom_internal_name without
is_consistent_container_name_enabled. v4.3.23 accepted it, so clients
such as `coolify app update --custom-internal-name` broke.

- A custom_internal_name sent without the flag turns the flag on, the
  same rule as the migration for existing applications
- Keep the 422 only when the request sends the flag as false

2026-10-05 22:37:07 +02:00

522 KiB

Raw Permalink Blame History