exoscale.compute.api.http — exoscale 0.2.11

HTTP support for the Exoscale Compute API

default-client clj

default-endpoint clj

Default HTTP endpoint for the Exoscale API

default-http-opts clj

Default HTTP options passed to the underlying HTTP library (aleph).

default-max-polls clj

Default number of times to poll before timing out

default-page-size clj

Number of records to fetch by default

default-poll-interval clj

Default timeout for async requests

extract-response clj

(extract-response resp opcode)

From a response get the result data

find-payload clj

(find-payload resp opcode)

job-loop!! clj

(job-loop!! config)

job-request!! clj

(job-request!! config opcode params)

json-request!! clj

(json-request!! config opcode params)

list-command? clj

list-request!! clj

(list-request!! config opcode {:keys [page pagesize] :or {page 1} :as params})

Perform a paging request. Elements are fetched by chunks of 500. If both page and pagesize are provided then we return a single page only, Otherwise fetch all results page by page.

This functionality is dependent on the api call supporting pagination, listZones and listSecurityGroups are examples of this.

Custom Exoscale commands that are not present in Cloudstack such as listApiKeys return the full list and do not support pagination.

opts->http-request-opts clj

(opts->http-request-opts {:as _opts :keys [request-timeout]})

Converts legacy request opts to jdk11 client opts

parse-body clj

(parse-body response)

raw-request!! clj

(raw-request!!
  {:keys [endpoint http-opts client method] :or {method :post} :as _config}
  payload)

Send an HTTP request

request!! clj

(request!! config opcode params)

Send a request to the API and figure out the best course of action from there.

Specifically:

• For a list request, fetch and page results
• For an async job request, wait for the job result

text-request!! clj

(text-request!! config opcode params)

validate-job!! clj

(validate-job!! {{:keys [errortext errorcode] :as jobresult} :jobresult
                 :as response}
                config
                opcode
                params)

• return jobresult if job was successful
• throw ex-info in case of failure (body is a string to mimic behavior of other query exceptions)

wait-or-return-job!! clj

(wait-or-return-job!! config remaining)

with-decoded-error-body clj

(with-decoded-error-body d)

Catches potential deferred error and rethrow with decoded ex-data.body if there is one, otherwise just rethrow