Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
|
|
||
| The command prints the target instance, runs the deploy validations, and then summarizes what would change: the `service.yaml` sections that differ from the deployed config, and a diff of the Sync Config. Nothing is deployed. | ||
|
|
||
| If the instance is not provisioned yet, the dry run skips Sync Config validation, because that check runs against a running instance. The summary reports that a real deploy would provision the instance first, then validate and deploy the Sync Config. |
There was a problem hiding this comment.
If the instance is not provisioned yet, the dry run skips Sync Config validation, because that check runs against a running instance.
This seems useful to document so users understand the dependency
The summary reports that a real deploy would provision the instance first, then validate and deploy the Sync Config.
This seems unnecessary to document - why document the report output here unless there's something advanced in the report output that we might want to explain more here?
|
I linked what looks like the corresponding divergence issue in the description so it closes with the PR #620 - however I have't confirmed if all the suggestions from the issue are valid and implemented in this PR, and I am also wondering if this #618 might also be worth documenting in this PR since both these features will probably be released at the same time? |
2 participants
Updates the CLI page for the dry run flag, from powersync-ja/powersync-cli#64.
--dry-runon the deploy commands: what the summary shows, and how to compare the fullservice.yamlwith the deployed config.Closes #620
AI disclosure
I used Claude to research the codebase and implement the change. I reviewed and tested it myself.