(V1) Implement API endpoints to manage deployments protected by the API key

[baktun14]

For each of the following endpoint api-key protected endpoints, we want to abtract away all the blockchain logic of creating the proper transaction payload to sign a transaction. We have example code in both console and akashjs

These should be done individually

• Create certificate
  • POST /v1/certificates
  • returns base64 encoded certificate (token)
• Create deployment
  • POST /v1/deployments
    • Parse and validate SDL
    • Create transaction payload example
    • Sign transaction
  • Payload: technically we should only need the SDL

{
  sdl: string
}

• Get bids
  • GET /v1/bids/{dseq}
  • proxy the request to a rpc using the address of the user account associated with the api key
• Create lease
  • POST /v1/leases
    • Create lease payload example
    • Sign transaction
    • Send manifest
  • Payload:

{
 sdl: string,
 dseq: string,
 gseq: string,
 oseq: string,
 provider: string,
 token: string // (base64 cert)
}

• Deployment details
  • GET /v1/deployments/{dseq}
  • Formulate a response with data coming from db indexer or rpc node with the following example return payload

{
  deployment: DeploymentDetails,
  leases: LeaseDetails[],
  escrow: EscrowBalance
}

• Close Deployment
  • DELETE /v1/deployments/{dseq}

[ygrishajev]

I'd suggest a more unified interface like:

POST /v1/deployments
GET /v1/bids/{dseq}
POST /v1/leases

[baktun14]

@ygrishajev makes sense

[baktun14]

@jzsfkzm I will work on the /v1/certificates endpoint