dokploy

mirror of https://github.com/Dokploy/dokploy.git synced 2026-10-15 13:21:11 +00:00

Files

T

Guillaume Juge 28f71e727a fix(dns): report an OVH zone refresh failure for what it is

refreshZone runs after the record write has already succeeded, so a failure
there means the change exists at the provider but is not being served yet. It
was left unguarded at all six call sites, so the caller saw a bare transport
error and would reasonably read it as "nothing was applied" — while a type
change had already deleted the old record and created its replacement.

Rolling the write back would destroy correct state over a publish failure, and
re-deleting after an uncertain network error is how records get lost. The error
now says what actually happened and how it resolves: the next successful change
to the zone publishes it, or the user can refresh the zone from the OVH manager.

Guarding the helper covers upsertRecord and deleteRecord too, not just the type
change Greptile pointed at.

Reported by Greptile on #5258.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-04 20:23:43 +02:00

scripts

fix(server): update build paths

2024-10-26 15:48:30 -06:00

src

fix(dns): report an OVH zone refresh failure for what it is

2026-09-04 20:23:43 +02:00

auth-schema2.ts

feat(scim): implement SCIM 2.0 user provisioning support

2026-07-08 14:06:22 -06:00

auth-schema.ts

Refactor user schema and update database references: rename 'users_temp' to 'user' across the codebase, update related database queries, and enhance endpoint specifications for swarm settings in various database schemas.