Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Make SAPI endpoint config option name(s) clearer

Open
#573 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Start by locating the configuration handling for the existing endpoint, metadata_api_endpoint, and leap_api_endpoint options and their environment variables. Trace how the SAPI endpoint is selected, then verify that solver_api_endpoint and DWAVE_SOLVER_API_ENDPOINT work while the existing endpoint aliases remain compatible; decide whether deprecation is included.

Written by the indexing model from the issue text.

Description

feature

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.

And after #569:

  • leap_api_endpoint (file/kwarg) option and DWAVE_LEAP_API_ENDPOINT (env var).

For consistency, we should:

  • add solver_api_endpoint/DWAVE_SOLVER_API_ENDPOINT options, and
  • make endpoint/DWAVE_API_ENDPOINT aliases of these new SAPI endpoint options

Optionally:

  • deprecate endpoint/DWAVE_API_ENDPOINT aliases
Dominant language
Python
Stars
63
Forks
44
Avg merge
9d 21h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwavesystems/dwave-cloud-client

All issues in dwavesystems/dwave-cloud-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.