fix: reprovision deprovisioned instances in deploy#11
Merged
Conversation
Chriztiaan
approved these changes
Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #10
Summary
We should reprovision deprovisioned instances, even if the sync config has not changed.
Overview
The
powersync deploycommand tries to validate sync config. The validation of sync config requires a running PowerSync instance.If the instance has been deprovisioned, we should redeploy/reprovision it before validating the sync config.
The previous logic check only did a reprovision if the sync config had changed. This broke if the instance was deprovisioned, but the sync config had not changed. This would result in a failure for validating the sync config.
This updates the
deploycommand to reprovision, before validating, if the instance is deprovisioned.