Conversation
2c4fe20 to
fe1efdb
Compare
fe1efdb to
ecd3b11
Compare
|
Great! So users are expected to configure this in their settings.toml somehow? Should we add something to the docs stating how to do that? And/or add a helper function to the config class that makes patching it (like you did in the test) easier? Also, the description of this PR is out of date I think, still mentions |
|
@dbanty Good question about the docs. I'm inclined to say that client configuration documentation shouldn't leak into pyQuil. That said, we could probably be more explicit about configuration in the There will be explicit documentation about configuring group accounts at https://docs.rigetti.com/qcs/. It will require something along the lines of: |
|
Maybe just a link from where config is mentioned in pyquil to the relevant API docs? Although, I'm thinking now we should document all config-related things on the main docs website and link to there from everywhere else since the C and Rust SDKs also use the same file formats. |
c4accf6 to
97fa90a
Compare
97fa90a to
69c4b50
Compare
|
We can probably add a bit more detail to this section in the docs, but probably the best entry point to configuration documentation that can link out to other documentation and sources. https://docs.rigetti.com/qcs/guides/using-the-qcs-cli#configuring-credentials |
* Update: support qcs account headers on engagement creation * Docs: provide a link to QCS cli configuration
Description
We want to support the client's ability to execute against a Rigetti QCS QPU using a QCS group account. To this end, we upgrade
qcs-api-clientwhich will addX-QCS-ACCOUNT-{ID/TYPE}headers to outgoing requests when the profile hasaccount_{id/type}set.Supersedes #1438
Checklist
rcbranch (notmaster).flake8conventions.