Hi,

a while ago I started to used Drydock. Helped with @thoughtpolice from haskell, the workflow was something like this.

1. Create a keypair in Phabricator using the Passphrase application. Let Phabricator manage the private key and generate its own keypair.
2. Create a blueprint in the Drydock application. Give it whatever name, and make sure it uses Preallocated Hosts as the setting.
3. Create a drydock resource manually using ./bin/drydock in the server running Phabricator - an example from haskell history is ./bin/drydock create-resource --name redacted --blueprint 1 --attributes platform=linux,host=redacted_ip,port=22,credential=2,path=/srv/leases.
4. Create some harbormaster rules, and have it do things like 'allocate a build machine' and then 'run commands' on build machine. That's pretty much it - Phabricator will correctly SSH into the machine with the keypair and do the right thing.

Now that I updated Phabricator the concept of Preallocated Hosts disappeared and the ./bin/drydock command didn't accept the create-resource subcommand, I'm a little bit lost. While it is prototype, I will appreciate if you find some time some hints to migrate to the new version. No need for an end user doc, just some little hints.

The workflow I tried is :

1. create an almanac network (Internet)
2. create an almanac device (build1) with the Internet almanac networks and a credential
3. trusted credential using .bin/almanac trust-key --id 1
4. create an almanac service (buildx) and bind the service to the interface
5. locked the service to activate it (shall I do this ??)
6. created an almanac host blueprint (build host)
7. try to find a command to manually create a resource (without success) so I guess it is made automagically now

I think it can help other users too (like haskell guys) even if I must be the only fool to upgrade while drydock is reworked (haskell choose to wait a bit since the dust settled). I would kindly appreciate some help.