At least some installs have been using Drydock in production for a while. This could be made easier -- and this task still has the best guide for it -- but I think nothing actionable here remains.

File a bug report please.

It didn't work for me.

Drydock and Almanac are now available in the cluster. Here's a rough guide to configuring them -- I'll turn this into something formal once things work a little more smoothly.

Quick update here ahead of deployment tomorrow:

This is detailed in T10463, but the API changes seem to have deployed with only a few minor rough patches, so we're currently on track to deploy everything else next Saturday (March 5).

New APIs are going out tomorrow morning (Saturday, February 27). I expect to unprototype Almanac shortly after that, provided things go relatively smoothly, so it will become available the following week (Saturday, March 5).

In T10449#161931, @dtf wrote:

Shouldn't restricted repositories short-names be rendered as [ Restricted Repository]? Sorry for this off-topic.

In T10449#161836, @epriestley wrote:

I also have a small patch against rCORE, but it's pretty minor and I can't really test it fully until the rest of this stuff makes it into production.

As a note to myself, I also need to adjust config for instances after pushing this, since empty values are now explicit. This only affects a handful of instances and they're easy to identify, so I may just do it manually rather than trying to write a migration.

I also have a small patch against rCORE, but it's pretty minor and I can't really test it fully until the rest of this stuff makes it into production.

Er, almanac.service.search, rather.

D15345 adds these capabilities:

Quoting for the main page :

Quick summary here: