You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it might be useful to support REST URIs in addition to console URIs.
An advantage of using REST URIs is these are easily generated with the CLI e.g.
gcloud container clusters list --project=${project} --format="table(name,selfLInk)"
In the context of RunMe this seems like a more useful pattern for generating the link because I can execute it directly in RunMe. If I have to go to the cloud console and then copy the link; then it kind of begs the question why wouldn't I just do everything I need to in the cloud console once I'm there.
The text was updated successfully, but these errors were encountered:
jlewi
changed the title
Could the GCP support REST URIs?
Could the GCP renderer support REST URIs?
Aug 1, 2024
It looks like the GCP renderers depend on pasting the URLs corresponding to the cloud console.
vscode-runme/src/extension/resolvers/gcpResolver.ts
Line 53 in ef69d97
E.g. for a GKE cluster you'd paste a link like
In contrast if I was using the REST URI it would look like.
or
I think it might be useful to support REST URIs in addition to console URIs.
An advantage of using REST URIs is these are easily generated with the CLI e.g.
In the context of RunMe this seems like a more useful pattern for generating the link because I can execute it directly in RunMe. If I have to go to the cloud console and then copy the link; then it kind of begs the question why wouldn't I just do everything I need to in the cloud console once I'm there.
The text was updated successfully, but these errors were encountered: