Add config options for defining Leap API endpoint - Githubissues

dwavesystems / dwave-cloud-client

A minimal implementation of the REST interface used to communicate with D-Wave Solver API (SAPI) servers.

https://docs.ocean.dwavesys.com/projects/cloud-client/en/stable/

Apache License 2.0

59 stars 40 forks source link

Add config options for defining Leap API endpoint #569

Closed randomir closed 1 year ago

randomir commented 1 year ago

We currently support:

metadata_api_endpoint (file/kwarg) option and DWAVE_METADATA_API_ENDPOINT (env var)
endpoint (file/kwarg) option and DWAVE_API_ENDPOINT (env var) for specifying SolverAPI (SAPI) endpoint - legacy names back from the era when cloud-client worked only with SAPI.

To support LeapAPI client, we're lacking:

leap_api_endpoint/DWAVE_LEAP_API_ENDPOINT options for specifying Leap API endpoint

Note: previously this issue included #573, but it makes sense to decouple them.