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.

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

[qiskit-ibm-experiment] Adapt to new channel parameter #27

Closed
rathishcholarajan opened this issue Mar 21, 2022 · 0 comments · Fixed by #34
Closed

[qiskit-ibm-experiment] Adapt to new channel parameter #27

rathishcholarajan opened this issue Mar 21, 2022 · 0 comments · Fixed by #34
Assignees
Labels
enhancement New feature or request

Comments

@rathishcholarajan
Copy link
Collaborator

rathishcholarajan commented Mar 21, 2022

What is the expected enhancement?

PR Qiskit/qiskit-ibm-runtime#226 and bugfix Qiskit/qiskit-ibm-runtime#251 is merged.

The configuration file which looked like below to get default-legacy account:

"default-legacy": {
    "auth": "legacy",
    "token": "abc",
}

will now look like:

"default-ibm-quantum": {
    "channel": "ibm_quantum",
    "token": "abc",
}

So qiskit-ibm-experiment needs to adapt to his change when choosing a default ibm quantum account for a user from the config file.

Acceptance Criteria

@rathishcholarajan rathishcholarajan transferred this issue from Qiskit/qiskit-ibm-provider Mar 21, 2022
@rathishcholarajan rathishcholarajan added the enhancement New feature or request label Mar 21, 2022
@rathishcholarajan rathishcholarajan changed the title [qiskit-ibm-experiment] Deprecate auth parameter and add channel parameter [qiskit-ibm-experiment] Remove auth parameter and add channel parameter Mar 30, 2022
@rathishcholarajan rathishcholarajan changed the title [qiskit-ibm-experiment] Remove auth parameter and add channel parameter [qiskit-ibm-experiment] Adapt to new channel parameter Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants