1043341 - Enable creating repositories as an API endpoint (returning credentials)

Status: RESOLVED WONTFIX

(Tree Management :: Treeherder: API, defect, P5)

Description

[Ed Morley [:emorley]]

Migrated from:
https://github.com/mozilla/treeherder-service/issues/142

lightsofapollo commented on 15 May:
{
To capture some of what was discussed today in a bug:

    There needs to be a way to automate the process of adding treeherder "repositories" this is a very common periodic operation that happens across multiple tbpl visible projects (particularly for b2g). Getting the credentials for the newly created project should also be automated (returned).

The solution we discussed in the abstract looks like this:

    expose a new type of credential which allows creation of repositories
    return credentials for that new repository (the existing code path for today)

Related but not critical items that we discussed:

    How third party (someone other then who created X repository) can gain access to post to a particular repo in a self-service or automated way (no direct human intervention from the treeherder team)

    Leveraging @jonasfj 's in progress work for scoped authentications via hawk instead of the current oauth scheme (i.e. having each repo be a "role" or resource which multiple authorized clients can update).

@jeads @camd
}


lightsofapollo commented on 16 May:
{
@jonasfj Just remembering our conversations about why I was not using treeherder-taskcluster automatic integration... Ideally that would include the ability to create repos and manage them as they branch... That would make it really useful over the explicit control I have right now in the github integration...
}


jonasfj commented on 16 May:
{
@lightsofapollo,
Are you talking about letting taskcluster-treeherder dynamically create branches on treeherder when a message for a non-existing branch is received.

Note, IMO taskcluster-treeherder is a short term project. I think treeherder people will want to take ownership of taskcluster-treeherder, perhaps write it in python, and consume taskcluster events directly. This would give them better flexibility, and we'll likely not change the events once things settle down (I believe we have a little bit more state to add before that happens).
}

Comment 1

[Ed Morley [:emorley]]

I don't think we want to do this.

Now that credentials are per-user the effort of adding a new repo is less.
If we were to make any change IMO it would be to move away from in-repo fixtures to an admin-panel approach for managing repos etc.