Cloud Code for Visual Studio Code

Cloud Code for VS Code brings the power and convenience of IDEs to cloud-native application development. Cloud Code integrates with Google Cloud services like Google Kubernetes Engine, Cloud Run, Cloud APIs and Secret Manager, and makes you feel like you are working with local code.

Cloud Code works with Google’s command-line container tools like skaffold, minikube, and kubectl under the hood, providing local, continuous feedback on your project as you build, edit, run, and deploy your applications locally or in the cloud. Cloud Code also deeply integrates with Cloud SDK to provide a unified authentication experience when you develop with Google Cloud Services.

Key Features

Supporting your development workflow

Get run-ready sample applications, out-of-the-box configuration snippets, support for key Google Cloud Services like Cloud APIs and Google Cloud Build, Cloud Native Buildpacks, Secrets Manager, one-click deployment, a tailored debugging experience, iterative run/debug experience and much more. Cloud Code makes developing with Kubernetes and Cloud Run a whole lot easier!

Kubernetes development

Create and run a new app in minutes with Cloud Code’s Kubernetes support. Or work on an existing application, customize its YAML with Cloud Code’s intelligent authoring support, debug it relentlessly with the setup-free debugger, and run it on any of your Kubernetes clusters. Whatever your workflow is, Cloud Code helps you spend less time on configuration and context-switching, so you can focus on developing your app.

Cloud Run development

Create and deploy a new service in minutes with Cloud Code’s equally robust Cloud Run support, monitoring your service’s progress with the Cloud Run Explorer and service logs accessible in the Log Viewer. If you’d prefer a local development workflow, you can also develop and debug a service locally with the built-in Cloud Run emulator .

Containerization made easy

Create secure, production-ready container images from source code without having to worry about a Dockerfile with Cloud Code’s built-in support for Google Cloud Buildpacks. You get to focus on building your application, not containerizing it.

Built-in Secret Manager support

Protect sensitive information and keep your app secure with Cloud Code’s integrated Secret Manager support. You can create, view, update, and use secrets in the Secret Manager view without having them in your codebase. Read the docs

Google Cloud APIs at your fingertip

Browse available Cloud APIs, enable services, and install and learn how to integrate client libraries in your app without leaving your IDE and breaking your development flow, all with the API library browser. Read the docs

Develop using Compute Engine Virtual Machines

Browse Compute Engine Virtual Machines and their relevant properties without leaving your IDE. Easily SSH into your VM using the terminal window and transfer files from your local environment to your virtual machine all with Cloud Code support for Compute Engine. Read the docs

Develop APIs with Apigee

Develop your API proxies and verify the functionality through unit and manual testing using the Apigee Emulator (local runtime). Quickly iterate through build and test cycles without impact to dependent applications. Read the docs

Resources

• Learn more: Learn more about Cloud Code and what it has to offer.
• Documentation: Cloud Code has a lot of features to explore. Head over to our documentation to discover more.
• Talk to us: Connect to the Cloud Code development team by joining the #cloud-code Slack channel
• File an issue: If you discover an issue, file a bug and we’ll fix it as soon as possible.
• Request a feature: If you have any feature requests, ideas for improvement, and general feedback, submit a feature request.

Security Disclosures

Please see our security disclosure process. All security advisories are managed on Github.

Apache Log4j 2 Vulnerability (Log4j 2): the Cloud Code guide to "Setting up a samples repository" linked to a demonstration project with a sample using a vulnerable version of Log4j 2. We strongly advise customers to update their samples repositories. Visit the security advisory for details and remediation.