Read an application's proposed setup contract
Read the setup Ankra proposed for this application before anything is deployed: the detected stack, whether a database was generated, and the deploy option contract of record. The contract and database each carry a three-valued status - a proposal Ankra could not read answers “unknown”, never an empty option list.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Response
Successful Response
The generated setup as recorded on the application: what Ankra detected, what it proposed, and what of it is negotiable. negotiable_options lists the option names a revision may change, so a caller never has to guess and a refusal is never the first thing the user learns.
The deploy option contract of record. options is populated only when status is "recorded"; on "absent" and "unknown" it is null and reason says which. An application whose contract Ankra cannot read is not an application without a contract, so the two must not be rendered the same way.
The database the proposal carries, read off the recorded manifests rather than off the detection that produced them. engine/operator/manifest_path are set only when status is "recorded".