Allow user to specify human readable service instance name during authentication about qiskit-ibm-runtime HOT 3 CLOSED

Yes both great points. I've update the description accordingly. Thanks @daka1510!

from qiskit-ibm-runtime.

Thanks for writing this up, @rathishcholarajan.

• If we filter by name we need to be aware that the name does necessarily uniquely identify a single service instance. In these (rare) cases I think it would be sufficient to log a warning message to make the user aware.
  
• How about reusing the generic locator parameter we agreed on in #29 instead of introducing another parameter? If we can easily implement is_crn(locator) that would make it fully transparent for the user, e.g.

IBMRuntimeService(auth="cloud",  locator="crn:v1:bluemix:public:quantum-computing:us-east:...")
IBMRuntimeService(auth="cloud",  locator="Quantum Services-og")
IBMRuntimeService(auth="legacy", locator="https://auth.quantum-computing.ibm.com") 

from qiskit-ibm-runtime.

Sounds good. My only comment is we can also save the instance name in the qiskitrc file, so we can look it up there instead of an API call. For example, we can allow

# saves a single CRN
IBMRuntimeService.save_account(token=<API key>, locator="Quantum Services-og")
# saves all CRN and sets a default
IBMRuntimeService.save_account(token=<API key>, locator=None, default="Quantum Services-og")

The equivalent legacy call would be

IBMRuntimeService.save_account(token=<API token>, default="my_hub/my_group/my_project")

from qiskit-ibm-runtime.