The Google Cloud Shell API empowers organizations to automate cloud operations, accelerate software delivery, and improve efficiency. By providing a programmatic interface for managing Cloud Shell environments, the API unlocks new possibilities for developers, SREs, and data teams. Explore the official documentation and try the hands-on lab to experience the benefits of the Cloud Shell API firsthand. ... - Source: dev.to / about 1 year ago

Command-line (gcloud) -- Those who prefer working in a terminal can enable APIs with a single command in the Cloud Shell or locally on your computer if you installed the Cloud SDK which includes the gcloud command-line tool (CLI) and initialized its use. If this is you, issue this command to enable the API: gcloud services enable youtube.googleapis.com Confirm all the APIs you've enabled with this command:... - Source: dev.to / almost 2 years ago

Gcloud/command-line - Finally, for those more inclined to using the command-line, you can enable APIs with a single command in the Cloud Shell or locally on your computer if you installed the Cloud SDK (which includes the gcloud command-line tool [CLI]) and initialized its use. If this is you, issue the following command to enable all three APIs: gcloud services enable geocoding-backend.googleapis.com... - Source: dev.to / about 2 years ago

While you might find that using the Google Cloud online console or Cloud Shell environment meets your occasional needs, for maximum developer efficiency you will want to install the Google Cloud CLI (gcloud) on your own system where you already have your favorite editor or IDE and git set up. - Source: dev.to / over 3 years ago

Here is the product https://cloud.google.com/shell It has a quick start guide and docs. - Source: Hacker News / almost 4 years ago

Anecdotal, but I have built from scratch a fairly large OpenAPI-compliant service using the Goa dsl (https://goa.design) and a coding agent and I've suspected for a while that the reason I've been as productive as I have with few blind alleys is that Goa kept the mistake surface pretty constrained. I also like not having the model generate boilerplate, as Goa's tooling does all that so much more cheaply. YMMV. - Source: Hacker News / 6 days ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / about 2 years ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: over 2 years ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: about 3 years ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 3 years ago