Quantum engine job URLs

[viathor]

Is your feature request related to a use case or problem? Please describe.

URLs to the webpage showing jobs scheduled on the quantum engine requires knowing details of the structure of the URLs that users are unlikely to remember. Context: #3304.

Describe the solution you'd like

Add an easily discoverable function that returns the URL for a given quantum engine job, i.e. URL like

https://console.cloud.google.com/quantum/programs/PROGRAM_ID/jobs/JOB_ID/overview?project=PROJECT_ID

What is the urgency from your perspective for this issue? Is it blocking important work?

P3 - I'm not really blocked by it, it is an idea I'd like to discuss / suggestion based on principle

[wcourtney]

Great suggestion, thanks. What do you think of adding a console_url() method to each of the Engine resources? Specifically, EngineProgram, EngineJob, and EngineProcessor?

[95-martin-orion]

Hey Will, this came up at Cirq sync. Is this still on the table?

[wcourtney]

Still on the table. It's filed under "usability" and "console transitions" for the QCS roadmap. This should be pretty simple though and probably doesn't need to wait. Assigning to Cheng as the new owner of cirq_google.

[dstrain115]

I don't think that this needs to be done as part of Cirq 1.0. Adding console_url() is extra functionality. Even if we "break backwards compatibility" by changing job URLs, we do not have public access to the API, so I don't think this is a crucial breakage (or even covered by our library guarantees, as it is external functionality). I propose this should be after 1.0.

@95-martin-orion Do you agree? If so, can you change this to after/1.0?