Conversation
b6fa5ed to
f36a269
Compare
LucDeCaf
left a comment
There was a problem hiding this comment.
This looks good to me :) Just some minor comments.
|
I understand that |
641e9cf to
980b6a0
Compare
I've opted to rename the variable to |
|
Closing this PR. The changes assume sync-config.yaml and service.yaml are shared across targets, which only covers a narrow use case. The better approach is to keep each environment in its own directory, which the CLI already supports. |
What
This PR adds named targets to
cli.yaml, so one project directory can point at several Cloud instances, for example staging and production.powersync link cloud --target=<name> --instance-id=<id>stores a link undertargets.<name>. The top-level fields stay the default.--create --target=<name>creates the instance and links it in one step.--target=<name>orPOWERSYNC_TARGET.--instance-idstill overrides both.powersync fetch instanceslists the targets of each linked directory.Backwards compatible
A
cli.yamlwithout atargetskey works exactly as before. Older CLI versions ignore the key andPOWERSYNC_TARGETand use the top-level fields.AI disclosure
I used Claude to research the codebase and implement the change. I reviewed and tested it myself.