Open deer opened 7 months ago
Thanks for this! I'll try to comment on these points in order...
The --project
flag expects an ID currently. It used to expect a UID, but we dropped this (since most of the time its still hard-enough to remember) in favor of either the NETZO_PROJECT_ID
env var (reads also from the .env
) if any) or completely omitting it by simply doing netzo deploy
and selecting it from the interactive prompt (landed in https://github.com/netzo/netzo/releases/tag/0.4.33). As a side note, I believe Deno.args
requires an =
sign e.g. --project=PROJECT_ID
in case you missed it
😟 Hadn't tried to deploy since merging https://github.com/netzo/netzo/pull/95 and https://github.com/netzo/netzo/pull/109 but I suspect something there broke deployments. They worked totally fine before. Can't comment further on this, but this is pretty critical, I'll get to debugging this now.
Agreed, a test for netzo deploy
(like we now have for netzo init
) would be very welcome to ensure not only projects can be initialized, but also deployed.
I just tried creating a project and deploying it. Things could have gone better :(
I tried using the
UID
, but I got this:Once I switched to using the longer ID which is impossible to remember, this happened:
So it looks like deploying with a locally installed CLI isn't easy (is impossible?). I haven't tried running the deployment command directly from the CLI, i.e. something like
deno run -A netzo/cli.ts do_the_other_stuff_Here
, but I guess that would fail with a similar error.After encountering the same error after installing the CLI, I realized it was because I had initialized my project with the local CLI, so my
deno.json
is incorrect (or at least not compatible with thedeploy
command).After changing my
deno.json
and testing locally viadeno task start
, I see the following in my terminal:That doesn't look good... Even if it works (because I see
./lib/deps/$fresh
in the netzo project), it doesn't seem like the right thing to be doing.So now I'm ready to start deploying. Unfortunately I now receive:
So then I delete my entire project and re-initialize (this time it's using the pinned remote 0.4.37 CLI). I try again:
At this point I'm too tired to continue further, so I'll stop here. It seems like we quite urgently need a test that asserts that deploying is possible, in addition to issues for all the other problems I encountered here.