| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
Implement organisation and repository creation using the Gitea REST
API v1. Add a 'gitea-access-token' application setting for this.
Closes #9.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replace the current hardcoded Downstream Host parameters with
application settings.
In general, Downstream Host connectors will use some combination of
HTTP(S) and/or SSH, so these are added in lorry-controller-webapp.
Currently only the gerrit connector will use downstream-ssh-url
and only the gitlab connector will use downstream-http-url.
Turn *on* StrictHostKeyChecking for the gerrit connector when not
talking to localhost.
Closes #4.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GitLab groups can have a visibility of 'private' (only members),
'internal'/'limited' (only authenticated users), or 'public' (anyone).
GitLab subgroups and projects can have the same visibilities as
groups, but cannot be more visible than the containing group.
When mirroring public source code, it may be desirable to make the
entities we create more visible than the current default of 'private'.
Add an option to set any of the three levels of visibility supported
by GitLab, with the default unchanged. (The same levels are supported
by Gitea, though with one named differently.) Never change the
visibility of a group or repository that already exists.
Note that the GitLab connector previously tried to create all projects
as public, but this stopped working after the change to API v4.
In Gerrit and Gitano the access control model is lot more complex, and
generally only administrators can set visibility. Make their
connectors reject visibility other than 'private'.
Relates to #6, #9.
|
| |
|
|
|
|
|
|
|
| |
* Introduce hosts module and DownstreamHost abstract base class
* Define a subclass of this for each Downstream Host type
* Define a name-type map for these in the lorrycontroller package
* Use these classes to replace type-specific code elsewhere
Related to #5.
|
| |
|
|
|
|
|
| |
Make this application setting and its description consistent with
the new terminology.
Related to #3.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is intended to replace all uses of "Trove" that should really be
"Downstream Host" or "Upstream Host", except in the database schema
and the REST API (which will probably change later).
* ARCH: Update example code to reflect API name change
* yarns.webapp: Update test descriptions and uses of internal APIs
* units: Update and rename the ls-troves units (although they still
use the ls-troves endpoint for now)
Some references that really are specific to Trove integration are
retained.
Related to #3.
|
| | |
|
| |
|
|
|
| |
In this scenario, where the mirror would be in the local
filesystem, lorry will be the one initialising the repository.
|
| |
|
|
|
|
|
|
| |
Yoyo migration libraries were failing in some cases due to "database is
locked" errors. It was difficult to track down what parallel operations
were causing the problems, so I dediced it was better to run the
migrations once per execution instead of executing them everytime
we opened a connection with the database (for every request).
|
| | |
|
| |
|
|
| |
Change-Id: I74dc0265fb3c92259101317d655eb55ccb62c119
|
| |
|
|
|
|
| |
While we're here, seeing as Adam mentioned it.
Change-Id: I5ddb86c70d76a84cf12fbd4eb91f3802e490d745
|
| | |
|
| | |
|
| | |
|
| |
|
