Pull windmill to main is always failing

[pa-bru]

I want to implement this workflow but I noticed pull-workspace.yaml fails mainly during the pull changes step.

here is a screenshot of the error

[rubenfiszel]

nestdotland/nest.land#336 nest land seems to be down. I will see how we can fix our dependencies

[rubenfiszel]

I purged the CLi from this faulty registry and updated the example to use 1.104.0. Thanks for the report

[pa-bru]

Thank you @rubenfiszel for the reactivity! I still encounter an issue but maybe I do something wrong.
For now my repo has nothing in it. everything (scripts, flows, etc) are in the remote workspace. And I'm using a self hosted windmill application.

it fails here: https://github.com/windmill-labs/windmill/blob/main/cli/pull.ts#LL33C2-L33C2

Do you have any idea? I tried to export the workspace as a zip in the app and it worked well.

[rubenfiszel]

I think what's happening here is that for some reason, the CLI pulls something but it's not a zip. Could you confirm that fetching
base_url/api/w/<workspace_id>/workspaces/tarball?archive_type=zip and passing your token as bearer token returns a zip ? Otherwise, what does it say ?

[pa-bru]

You are right. I just tested the request and it returns html. Our windmill app is hosted on cloudflare and we have to signin with google workspace...

[rubenfiszel]

Since windmill supports Google SSO directly, you could expose it publicly under the google sso

[pa-bru]

Do you refer to this feature?
I also saw the google cloud github action so I wonder what I should use

[rubenfiszel]

Yes I was referring to configuring oauth so that google sso was a login provider. A possibility is also to self-host the github runner behind your cloudflare tunnet so that it can talk to windmill directly.