7d6223ccd4
gateway: add get org members api/action
2019-05-14 12:58:29 +02:00
8f959c4500
cmd: add org member add/remove commands
2019-05-14 11:25:12 +02:00
aeda922a7d
*: rename deleteOrgMember to removeOrgMember
2019-05-14 11:20:09 +02:00
c5cdf01332
*: add organizations visibility
2019-05-14 10:56:17 +02:00
c41de71694
gateway api: return linked account id
2019-05-13 23:12:48 +02:00
a4744ab7f4
gateway: return right error when remotesource login fails
...
If the remote source username/password based login fails return the right error
code: 401 (unauthorized) on wrong username/password or a 500 on other errors.
2019-05-13 14:23:41 +02:00
4a8d86ae76
gateway: implement projectgroup delete
2019-05-13 00:24:16 +02:00
5dfe7f8ce9
gateway api: return projectgroup visibility
2019-05-12 23:24:48 +02:00
d2d1a5fb65
gateway api: return project visibility
2019-05-12 23:23:30 +02:00
83f6ebe95f
gateway: implement updateProject
...
Update project currently handles updating project name and visibility. In future
we'll add additional update logic.
2019-05-12 23:22:18 +02:00
4c35c88b32
fix auth
2019-05-12 23:19:56 +02:00
8e70c6b1b9
gateway: use authOptionalHandle with logHandler
...
or it'll fail when fetching logs on user runs since the logged in userid is not
set in the context
2019-05-12 00:28:50 +02:00
55b4a94281
gateway api: remove unused exposedURL variable
2019-05-12 00:28:11 +02:00
0c94386149
gateway: add badges endpoint
...
Currently we generate badges only for projects branches. In future this could be
extended to also generate badges for tags and PRs
2019-05-10 11:08:24 +02:00
c523bcba4e
gateway: add delete remote source handler
2019-05-10 00:03:03 +02:00
b0fe7e4115
*: implement delete organization member
2019-05-09 17:05:13 +02:00
d0309db97f
types: add RemoteUserAvatarURL to User
2019-05-09 16:49:02 +02:00
b37eddbe8b
gateway: remove omitempty json struct tag from UserResponse
2019-05-09 16:48:28 +02:00
620bae68df
*: implement add/update org member
2019-05-09 16:47:22 +02:00
8069063e0d
gateway: add project update repo linked account api
...
Change the project repo linked account to the one of the current user
2019-05-09 15:36:47 +02:00
a43be4a6be
gateway: update CreateProject api
...
remove currentuserid since we can get it directly in the action
2019-05-09 15:34:58 +02:00
92de7591da
gitsources: implement gitea oauth2 auth
...
As from https://github.com/go-gitea/gitea/pull/5378 gitea is an oauth2 provider.
2019-05-09 14:14:13 +02:00
43341f2cba
*: rename GitServer to Gitserver
2019-05-08 15:23:13 +02:00
1e34dca95d
runservice: split and simplify scheduler and executor naming
...
Also if they are logically part of the runservice the names runserviceExecutor
and runserviceScheduler are long and quite confusing for an external user
Simplify them separating both the code parts and updating the names:
runserviceScheduler -> runservice
runserviceExecutor -> executor
2019-05-07 23:56:10 +02:00
44d5b0f25a
*: rename ConfigStore to Configstore
2019-05-07 23:42:42 +02:00
e4e7de4ad2
runservice/gateway: return run on run action
2019-05-07 23:23:58 +02:00
83273489e0
jwt: unify token generation functions
2019-05-07 18:30:20 +02:00
649c42f75b
gitsources: create secret and webhook secret
...
Use the webhook secret on webhook creation and check it and webhook receive
2019-05-07 18:29:31 +02:00
4154be3370
*: set sshhostkey and skip check on remote source
2019-05-07 15:59:08 +02:00
afae185e11
*: rework run approval and annotations
...
* runservice: use generic task annotations instead of approval annotations
* runservice: add method to set task annotations
* gateway: when an user call the run task approval action, it will set in the
task annotations the approval users ids. The task won't be approved.
* scheduler: when the number of approvers meets the required minimum number
(currently 1) call the runservice to approve the task
In this way we could easily implement some approval features like requiring a
minimum number of approvers (saved in the task annotations) before marking the
run as approved in the runservice.
2019-05-06 15:19:29 +02:00
a04dd62e91
gateway: initial authorization
2019-05-03 23:19:23 +02:00
081ac8a44f
gateway: move webhook genGroup to common as GenRunGroup
2019-05-05 23:58:40 +02:00
6ef5649b21
gateway: set user admin value in context
2019-05-05 17:30:38 +02:00
6dfb789e77
gateway: project(group) create: rename parentID to parentRef
2019-05-05 17:19:23 +02:00
05ae46a72d
gateway: move run logic from api to actions
2019-05-06 00:00:45 +02:00
6b5bd40417
gateway: move remaining remotesource logic from api to actions
2019-05-05 14:54:16 +02:00
42184d0b5b
gateway: move remaining user logic from api to actions
2019-05-05 14:45:19 +02:00
96918e9bad
gateway: move remaining org logic from api to actions
2019-05-05 14:36:14 +02:00
c889c2c1c2
gateway: move remaining project(group) logic from api to actions
2019-05-05 14:27:22 +02:00
64044df94d
gateway: move secret logic from api to actions
2019-05-05 14:11:29 +02:00
f73f0ba434
gateway: move variable logic from api to actions
2019-05-04 15:16:49 +02:00
3f7e554f04
gateway: rename command(handler) to action(handler)
...
Since we're going to migrate all actions (also queries that now are implemented
in the api handlers) there
2019-05-03 23:48:49 +02:00
5a50a2681d
util/errors: add ErrForbidden
2019-05-03 23:18:51 +02:00
041e8867f8
*: add creatorUserID and cretedAt to organization
2019-05-03 14:24:18 +02:00
60feff5cef
configstore: add more validations
...
All the validation must be done inside the configstore since it's the source of
truth.
The gateway could also do some validation to avoid bad requests to the
configstore when needed or when the logic resides outside the configstore (like
project setup or user registration)
2019-05-03 12:41:49 +02:00
1f09eea949
project: add remote repository config type
...
RemoteRepositoryConfigType defines how a remote repository is configured and
managed. Currently only "remotesource" is supported.
In future other config types (like a fully manual config) could be supported.
2019-05-03 12:21:44 +02:00
ea02eed2d9
* api: accept both ids or names in the same endpoint
...
Simplify api to accept both ids or names in the same endpoint
2019-05-03 11:07:53 +02:00
6943c10dc9
types: add RemoteSourceID to Project
...
In future we may support specifying a remote source for a project without a
linked account and thus use a user provided token (saved in the project) or
other ways to define a remote repo (like standard git repos over ssh).
2019-05-03 09:55:37 +02:00
b9db3137ad
gateway api: return user linked accounts
2019-05-03 09:54:47 +02:00
ab7e4b8a4b
gateway: add user remote repos API
2019-05-03 00:11:11 +02:00
68e6bd5bdf
configstore: add project/projectgroup visibility
2019-04-30 17:09:26 +02:00
b1c9892378
configstore: report project/projectgroup path
...
and also parent path
2019-04-30 17:09:26 +02:00
984efb539e
configstore: use augmented types for vars/secrets dynamic values
2019-04-30 16:28:01 +02:00
1820e7c477
types: rename user UserName field to Name
2019-04-30 12:56:43 +02:00
1e1152cb1a
gateway: set agolaid query parameter in webhook url
2019-04-30 12:13:51 +02:00
fefa2819c9
gateway: use agola ID in gitsource tokenname
2019-04-30 12:13:12 +02:00
cbd971619b
gateway: refresh oauth2 token when needed
...
refresh the oauth2 access token when needed and update the related linked
account.
2019-04-29 15:42:10 +02:00
95e73e66a0
oauth2: correctly populate token expiry data
...
* Populate the field when needed
* Convert it to a time instead of a duration
2019-04-29 14:57:07 +02:00
41e333d7ec
*: rename "lts" to "ost"
...
`lts` was choosen to reflect a "long term storage" but currently it's just an
object storage implementation. So use this term and "ost" as its abbreviation
(to not clash with "os").
2019-04-27 15:16:48 +02:00
4c30a5af1c
runservice: handle jsonnet and json config files
...
Handle config files with name `config.jsonnet`, `config.json` and
`config.yml` and take the first from the repository in this order
For a jsonnet file execute it and use the generated output as the config
2019-04-16 15:00:37 +02:00
6066221136
runservice: rename config pipeline(s) to run(s)
...
No need for different names. We are always talking about a run. In the config
it's the run definition, in the service is the run execution.
2019-04-15 23:42:10 +02:00
8bde2f2bc0
runservice: implement caching
...
Add `save_cache` and `restore_cache steps`
2019-04-13 14:58:56 +02:00
3928851c10
runservice: rename Run.RunTasks to Run.Tasks
2019-04-12 17:45:38 +02:00
5165984030
runservice: convert RunConfigTask.Depends to a map
2019-04-12 17:04:07 +02:00
ca1d837ecd
webhook: use hook provided ssh url for cloning
...
Additionally don't save a CloneURL field inside the project type.
If in future some git source doesn't provide a clone url we could just calculate
it from project.RepoPath or call the remote api to retrieve it.
2019-04-11 16:49:07 +02:00
782750e51e
project: save remote repository id
2019-04-11 17:11:17 +02:00
da27348a1d
runservice: implement run setup errors
...
Add the ability to define a run with a setuperror phase.
When the run setup has errors client could submit a run with a list of setup
errors. In such case the run will be created in the setuperror phase.
Setup errors are currently generated by the webhook receiver and the run service
when it checks the run config for possible issues.
2019-04-09 16:51:37 +02:00
671b89d391
runservice: merge RunConfig and RunData
...
* Use just RunConfig
* Use StaticEnvironment vs Environment in RunConfig to distinguish between env
that won't change at run recreation from env that could change at every
recreation
* The RunCreate api will just receive the runtasks instead of a runconfig (more
right)
2019-04-09 18:11:00 +02:00
3642be6f21
*/api: Use helpers for error handling
...
* client: always parse the json error message field and return its contents
* Use ErrBadRequest and ErrNotFound in every handler and command
* Gateway: by default pass underlying service error (configstore, runservice) to
client keeping the status code and message. In future, if some errors must be
masked, we should change the specific parts that need special handling.
2019-04-09 14:53:00 +02:00
7d787c5f77
*: implement task approval
2019-04-08 17:29:57 +02:00
81537f882f
gateway: fix runs url to plural
2019-04-08 16:11:19 +02:00
04f3905ea1
client: fix content type header case
2019-04-08 12:28:15 +02:00
03b5a53510
gateway/command: use ErrBadRequest when needed
2019-04-08 12:08:31 +02:00
56d903d4db
gateway api: improve response handling
...
* Always return a json message also on error. For internal errors return a
generic "internal server error" message to not leak the real internal error to
clients
* Return 201 Created on resource creation
* Return 204 No Content on resource deletion and other action with no json
output
2019-04-08 11:35:45 +02:00
763d77d899
gateway: rename projectid to projectref
2019-04-08 09:04:55 +02:00
f3781c9087
*: fix rest methods
...
* use POST instead of PUT for resource creation
* use PUT instead of POST for resource special actions
2019-04-08 08:54:45 +02:00
595590e611
api: use httpError helper everywhere
2019-04-05 16:33:00 +02:00
fe5bc2fa31
gw repos: use config provided gitServerURL
2019-04-05 16:23:54 +02:00
ac28731d11
gateway: only admin or the same logged user can create an user token
2019-04-05 15:56:06 +02:00
c4310be7de
Implement user token delete
2019-04-05 15:01:57 +02:00
3a41e66f5b
cmd: implement variable delete
2019-04-05 11:11:27 +02:00
2e335effe9
cmd: implement secret delete
2019-04-05 11:00:45 +02:00
42becb0505
update secret create
2019-04-05 10:32:32 +02:00
25eb200625
gw api: fix matching secret logic
2019-04-05 10:26:35 +02:00
58a77ad221
gateway: handle skipped webhook
2019-04-03 17:05:50 +02:00
84879bf591
gateway: limit requests to a predefined max size
2019-04-03 16:59:17 +02:00
4cf72748b4
gitsources: update api
...
* Generalize to use repopath instead of (owner, reponame)
2019-04-03 15:01:21 +02:00
a2cd92c70b
webhook: use provided userID
2019-04-03 15:11:50 +02:00
2d68be8a30
gw api: fix project and remotesource to return the right response
2019-04-03 15:08:33 +02:00
bb21520133
gw api client: add GetCurrentUser
2019-04-03 15:06:02 +02:00
9d559d49d7
webhook: correctly handle git host and port
...
* split host and port from the git url
* also set the port in the generated ssh config
2019-04-03 12:27:09 +02:00
3d39553189
project create: user project path
...
Use project path for project creation and get the project clone url directly
from the remote source
2019-04-03 11:07:54 +02:00
6736f5aebc
gw api: require at least one group on runs query api
2019-04-03 08:52:29 +02:00
f0e7ce4a96
cmd: implement project/projectgroup variable create
2019-04-02 11:07:39 +02:00
eb8cd9cc52
gateway: add user registration
...
Adds two handler:
* Authorize handler used to ask remote source authorization
* Register handler used to do user and related linked account creation
2019-03-29 17:53:15 +01:00
704da47afc
configstore: createuser also create linked account when requested
...
Useful to future user registration to create user and linked account in a unique
atomic call.
2019-03-29 17:50:51 +01:00
3e3a7a0ea5
gateway: move user la and login validation to command layer
2019-03-29 14:33:41 +01:00
3c5eb71ba8
runservice: make and check that group paths are absolute
2019-03-29 12:09:32 +01:00
48ab496beb
*: add api to query last run per group
2019-03-29 12:00:18 +01:00
1e41e3ad33
gateway/api: report if the run can be restarted
2019-03-29 09:22:34 +01:00
Simone Gotti