Stages now is a dictionary where each key corresponds
to the architecture and the value is the old stages array.
Thus we'll have number of build farm jobs equals to the
number of architectures.
If an arch is present in the pipeline but missing in previous
stages an error is raised.
Stages now is a dictionary where each key corresponds
to the architecture and the value is the old stages array.
Thus we'll have number of build farm jobs equals to the
number of architectures.
If an arch is present in the pipeline but missing in previous
stages an error is raised.
The PO export views pass IDs to `POExportRequestSet.addRequest`
(probably for performance), so it needs to preserve the ability to
accept either database model objects or IDs.
This exposed one test that was passing a `POTemplate` in the `pofiles`
argument, apparently by accident.
There are currently several cron jobs on loganberry that export email
and SSH key data for the members of several teams, using
`scripts/list-team-members`; this information is used as part of various
integrations such as lists.ubuntu.com posting privileges, the ability
for Ubuntu members to upload files to people.ubuntu.com using SFTP, and
so on. However, doing this with ad-hoc cron jobs on a Launchpad machine
isn't ideal; it would be better if it were possible to get this
information over the API, and then IS would only need a
suitably-privileged bot account.
As far as I can see, the only API gap here is that we can only extract
the raw key text for an SSH key, and not the "full" key text that's
decorated with the key type and comment in a format suitable for adding
to an OpenSSH `authorized_keys` file. That transformation isn't quite
trivial, so export a method that does it on the webservice.
