Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make SAPI endpoint config option name(s) clearer #573

Open
randomir opened this issue Sep 12, 2023 · 0 comments
Open

Make SAPI endpoint config option name(s) clearer #573

randomir opened this issue Sep 12, 2023 · 0 comments
Labels
feature

Comments

@randomir
Copy link
Member

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@randomir