2 Commits

Include renames

Author	SHA1	Message	Date
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
Andras Bacsai	50268139be	fix(api): reject custom_internal_name without consistent container naming ... Container names use custom_internal_name only when consistent container naming is on. The API accepted the name and then ignored it. - Return 422 with a message that says to set is_consistent_container_name_enabled to true - Accept the name when the request or the application turns the setting on - Document the requirement in the OpenAPI spec	2026-10-05 21:23:55 +02:00