[SOLVED] Unable to push function from API KEY with CLI

When trying to push functions from Gitlab CI (with an API KEY and using the CLI), i saw that i was unable to push functions.

Is it something that you stopped supporing or is it a bug ?

Looking at the code, it seams like the push function uses the ConsoleService for checking proxies rules :

• https://github.com/appwrite/sdk-for-cli/blob/22.3.0/lib/commands/push.ts#L827
• https://github.com/appwrite/sdk-for-cli/blob/master/lib/commands/init.ts#L388
• https://github.com/appwrite/sdk-for-cli/blob/master/lib/sdks.ts#L89
  which means the SDK for console have requireAuth to true and so require either an access token OR a cookie.

As a fix, maybe :

• when pushing functions/site to add an option for the proxy part (like a --with-proxies)
• just skip that proxy part if it's an API KEY
• or since i saw in the console, that the API keys have proxy scopes, to fix it and don't use the ConsoleService

as a current workaround i'm using the login with totp :

it's just annoying cuz every publish i get an email warning me about a new sessions xdd

taking a look

https://github.com/appwrite/sdk-generator/pull/1651

saw it was merged and deployed, i'm testing

sadly still not working

it's more like the push command constructor have the console that needs session and is used in places where it should be key only

using this console client : https://github.com/appwrite/sdk-generator/blob/main/templates/cli/lib/commands/push.ts#L782

this is the actual release - https://github.com/appwrite/sdk-for-cli/pull/337

oh ok ok, iirc i saw it in the 22.5.0 release note but might be wrong

Also, it's now working

noice

putting it as solved

[SOLVED] Unable to push function from API KEY with CLI

also when pushing, the Deployment page URL use project-688228a50003cf2546fa tho the console use regions so it should be project-default-688228a50003cf2546fa instead

since i don't use that URL i don't really care, but for others that could be nice to fix it

ur using self hosted?

yes (that's why it's using default and not a real region)

yep yep makes sense

noted

i swear it used to be just project-${projectId} for self hosted, there is logic for it

ig it changed with 1.9.5?

no it was already the case since the cloud regions so something like 1.8.0.

i also remember needing a console patch because the console didn't support region when the API did

for example, the "/v1/account/prefs" return this, so with the region