Blueprints, authorizations and leases have their search engines and dao's made conduit friendly here so that clients can reason about leases which belong to them and which blueprints they are allowed to use.
We also give blueprints more rigid definitions of the attributes they expect when creating leases, and expose documentation for those attributes on the conduit console.
The general expected client flow is:
- use drydock.requestauthorization to gain access to blueprints
- use drydock.createlease to obtain a lease
- use drydock.destroylease when you're done with it