Skip to content

fix: preserve omitted settings on application update - #63

Open
Gourav224 wants to merge 1 commit into
Dokploy:mainfrom
Gourav224:fix/application-update-merge
Open

Gourav224 wants to merge 1 commit into
Dokploy:mainfrom
Gourav224:fix/application-update-merge

Conversation

@Gourav224

Copy link
Copy Markdown

application.update clears fields missing from the payload, so dokploy application update --name X reset sourceType, buildType, triggerType and autoDeploy. The CLI now fetches the current application and merges the provided flags over it before posting (client-side option 1 from #51). It's applied to application.update only, via a generator map, and includes a unit test. It relies on application.one, so it needs #52 for GETs to work.

Fixes #51

🤖 Generated with Claude Code

application.update clears fields missing from the payload, so changing one
flag reset sourceType, buildType, autoDeploy, etc. Fetch the current
application and merge the provided flags over it before posting.

Fixes Dokploy#51

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: dokploy application update nullifies omitted settings (sourceType, buildType, triggerType, autoDeploy, ...)

1 participant