[public-api] Implement ProjectsService.CreateProject

[easyCZ]

Description

Related Issue(s)

• Depends on [gitpod-protocol] Add project APIs to Golang client #14624
• Depends on [public-api] Add extra prebuild settings to Project Settings #14645

How to test

1. Preview, sign in with Github and give perms to Read Repo
2. Obtain an Access Token by running the following in the console, after logging in

   await window._gp.gitpodService.server.generateNewGitpodToken({ type: 1, scopes: ["function:getGitpodTokenScopes",
   		"function:createTeam",
           "function:createProject",
   		"function:getTeamMembers",
   		"function:getGenericInvite",
   		"function:getTeams",
   		"function:getTeam",
   		"resource:default",]})

3. Setup the token as env variable BEARER_TOKEN="<token>" in your terminal
4. Create a team programmatically

   	curl \
       --header 'Content-Type: application/json' \
       --header "Authorization: Bearer $BEARER_TOKEN" \
       --data '{ "name": "<team_name>" }' \
       https://api.mp-papi-cr5eede70b3a.preview.gitpod-dev.com/gitpod.experimental.v1.TeamsService/CreateTeam

5. Take note of the Team ID in the response, use it in step 6
6. Create a Project in this team, choose one of your GitHub repos

   curl \
     --header 'Content-Type: application/json' \
     --header "Authorization: Bearer $BEARER_TOKEN" \
     --data '{ "name": "connect-go-prometheus", "slug": "connect-go-prometheus", "cloneUrl": "https://github.com/easyCZ/connect-go-prometheus.git", "teamId": "<team-id>", }' \
     https://api.mp-papi-cr5eede70b3a.preview.gitpod-dev.com/gitpod.experimental.v1.ProjectsService/CreateProject
   

7. Use the project from the dashboard

Release Notes

NONE

Documentation

Werft options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-mp-papi-create-project.2 because the annotations in the pull request description changed
(with .werft/ from main)

[easyCZ]

/werft run

👍 started the job as gitpod-build-mp-papi-create-project.5
(with .werft/ from main)

[geropl]

/werft run

👍 started the job as gitpod-build-mp-papi-create-project.11
(with .werft/ from main)

[easyCZ]

/werft run with-clean-slate-deployment=true

👍 started the job as gitpod-build-mp-papi-create-project.14
(with .werft/ from main)

[laushinka]

At step 6, when I did

curl \
  --header 'Content-Type: application/json' \
  --header "Authorization: Bearer $BEARER_TOKEN" \
  --data '{ "name": "testing-prebuild-gh", "slug": "testing-prebuild-gh", "cloneUrl": "https://github.com/laushinka/testing-prebuild-gh.git", "teamId": "ee4c2b7e-e7ff-498b-b576-d3ba92d3d01f", }' \
  https://api.mp-papi-cr5eede70b3a.preview.gitpod-dev.com/gitpod.experimental.v1.ProjectsService/CreateProject

I got {"code":"invalid_argument","message":"unmarshal into *v1.CreateProjectRequest: proto: (line 1:3): unknown field \"name\""}

Did I do something wrong in the curl?

Note: I entered the name and slug arbitrarily.

[easyCZ]

@laushinka
Thanks. I've copy-pasted the instructions wrong (sorry about that). The right command is:

curl \
  --header 'Content-Type: application/json' \
  --header "Authorization: Bearer $BEARER_TOKEN" \
  --data '{ "project": {"name": "testing-prebuild-gh", "slug": "testing-prebuild-gh", "cloneUrl": "https://github.com/laushinka/testing-prebuild-gh.git", "teamId": "ee4c2b7e-e7ff-498b-b576-d3ba92d3d01f"} }' \
  https://api.mp-papi-cr5eede70b3a.preview.gitpod-dev.com/gitpod.experimental.v1.ProjectsService/CreateProject

The payload has to be in the form:

{ project: {
    name:
    slug:
    cloneUrl:
  }
}

[laushinka]

@easyCZ Thanks! So my requests were responded with {"code":"internal","message":"Request createProject failed with message: GitHub API Error. Status: 404"}, but turns out the projects did get created. So it works but it responded with the wrong message?

[laushinka]

Approving with a hold for this question[1]

/hold

[easyCZ]

@laushinka Yeah, this relates to https://gitpod.slack.com/archives/C02EN94AEPL/p1668585656105419

[easyCZ]

It's possible you did not do step 1. to grant read perms to Github

1. Preview, sign in with Github and give perms to Read Repo

[laushinka]

1. Preview, sign in with Github and give perms to Read Repo

INDEED. Sorry, let me try again with a different repo.

[laushinka]

1. Preview, sign in with Github and give perms to Read Repo

INDEED. Sorry, let me try again with a different repo.

Like a charm.

/unhold