This page documents production updates to Cloud Code for Visual Studio Code. You can check this page for announcements about new or updated features, bug fixes, known issues, and deprecated functionality.
-
Secret Manager Support: Many applications require credentials to connect to a database, API keys to invoke a service, or certificates for authentication. Cloud Code now integrates with Google Cloud's Secret Manager to make it easy to create, view, update, and use secrets from within your IDE so you can keep this sensitive data out of your codebase and keep your applications secure. Get started today by viewing secrets, creating a new secret, or add secret manager API support to your code. You can learn more about Secret Manager support from the Cloud Code Secret Manager documentation.
- View secrets, their versions, permissions, and properties in the Secret Manager view.
- View secrets, their versions, permissions, and properties in the Secret Manager view.
-
Minikube Credentials Support: When running or debugging on Cloud Run Emulator or minikube, Cloud Code will automatically set up the minikube gcp-auth addon. This will enable you to use your Google developer credentials to authenticate Google API client libraries in your apps when running in these environments with zero configuration required. Cloud Code also has a new login flow to ensure you have developer credentials installed when you login.
-
Managed Dependencies in Integrated Terminal: You can now use Cloud Code managed dependency CLIs, such as minikube and gcloud, through VSCode Integrated Terminals.
-
Improved Cloud Run (fully managed) support:
-
Deploy Cloud Run services from your IDE to these newly added regions. View the full supported list here.
-
Allocate up to 4GiB of memory to your services with the increased quota.
-
-
#286 #313 Minikube status checks are aggressive and lead to generating more log files that can slow down other build tools. The change is to remove the live status bar but use minikube status bar to monitor status of different profiles and is less invasive.
-
Cloud run emulator didn’t bootstrap itself on windows since it chose the hyper-v that got blocked on the need for special permissions, Cloud code now defaults to using docker driver for the emulator.
-
#314 Regions are not available when I use "Deploy to Cloud Run"
-
Improved performance: Reduced load times for populating the GKE explorer (from about a 12 second load time to under 5 seconds!); logging out or switching accounts is now a much faster experience.
-
Kubernetes run/debug bootstrapping improvements: Cloud Code now helps you set an active context at the start of a run or debug session to help you get your Kubernetes application deployed quickly. If you don’t have any contexts, Cloud Code helps you create one.
-
Auto-start minikube: Cloud Code now manages minikube more proactively. When running/debugging on a minikube cluster that is paused or stopped, Cloud Code automatically starts the cluster at the beginning of the session and pauses it when you’re done.
-
Cloud Run local development: Develop Cloud Run applications locally using Minikube clusters with the newly added Run and Debug on Cloud Run Emulator commands.
-
Expanded CRD support: Cloud Code has been expanded to support validation, hover documentation, and code completions for hundreds of popular Kubernetes Custom Resources.
-
Buildpacks support: In addition to Docker, you can now build your images with Google Cloud buildpacks.
-
Auto generate configuration experience for existing K8s apps: The UI that helps auto generate configuration for an existing app moving in to using Cloud Code extensions now supports specifying all available build and configuration settings.
-
Improved New Application UI: Creating a new application now uses the system file picker to help you quickly place the new files in a familiar way. You can rename the new application folder through your system file manager.
-
Kubernetes Context Management: Contexts are now accessible from the Kubernetes Explorer! You can now browse and switch between Kubernetes contexts as you would during your development workflow with Cloud Code. With the updated Kubernetes Explorer, it's easier to understand the active context associated with your current cluster and move to another if you need.
-
PersistentVolumeClaim support: The Kubernetes Explorer will now show your cluster's PersistentVolumeClaim (PVC) resources and each PVC's status and key details.
- Issue #131: Cloud Code will now allow you to browse and switch between Kubernetes contexts!
- Issue #193: You can now browse PersistentVolumeClaim in the Kubernetes Explorer!
We are pleased to announce Cloud Run support in Cloud Code for VS Code!
-
Cloud Run support in VS Code: Cloud Code now makes it easy to develop and deploy your services to Cloud Run (fully managed) or Cloud Run for Anthos on GKE directly from within Visual Studio Code. You can get started with our starter templates for Java, Node.js, Go, or Python.
- Browse your Cloud Run services directly from the IDE using the Cloud Run explorer. Easily see details of deployed services as well as revisions and status.
- Follow the Cloud Run quickstart guide to get started!
-
Improved dependency management: Better experience when Cloud Cloud is managing dependencies.
- Improved performance when installing managed dependencies.
- Stay up to date with the latest versions of dependencies.
-
Cloud Code: Debug on Kubernetes: New command to debug applications with the same configuration used to run the application.
- Invoking this command will launch the application and debugs all the containers in the app.
- Refer to the documentation for more on this feature.
-
Separate views for Kubernetes, Cloud Run and APIs: Reorganized UI to focus on the flows that matter.
- Dependency management: Previously offered "On," "Off," and "Ask" as choices for managing dependency with "Ask" as the default. In the latest release we've removed the "Ask" choice with "On" as the default. Anyone who has picked "Ask" will be defaulted to "On."
- Deprecation of Kubernetes deploy commands: The deprecated ‘Cloud Code: Deploy’ and ‘Cloud Code: Continuous Deploy’ have been removed. Use ‘Cloud Code: Run on Kubernetes’ command.
- #231 Add support for Google Cloud Run
- #227 Hanging while installing dependencies
- #225 Cannot start debugger for .NetCore project
- #224 GKE Explorer does not work in windows 10
- #223 Add Configuration to Existing Project is broken
- #203 Add a guidance message in case no Kubernetes manifest are present
Updated the extension to be compatible with the latest version of Visual Studio code. Fixed an issue introduced by the latest update that caused specific terminal commands to hang.
-
Flexible Kubernetes YAML editing: Edit your Kubernetes YAML with additional support for multiple Kubernetes versions.
-
Streamlined remote development flow: Work with Cloud Code using a remote development environment, taking advantage of newly added support:
-
Start development with just Visual Studio Code installed.
-
Receive direct reporting on the progress of ‘Open with Cloud Code’ throughout its flow.
-
Cancel the open any time during the operation.
-
If an error does occur, know that it will come with actionable guidance.
-
-
Cloud Code: Deploy deprecation: ‘Cloud Code: Deploy’ and ‘Cloud Code: Continuous Deploy’ commands are deprecated. While these commands continue to work, they will be removed in the next release (v1.3), targeted for the end of March.
Use ‘Cloud Code: Run on Kubernetes’ command instead.
-
Improved Logs Viewer: Make the most out of your log viewing with the following new filters:
-
Log Type: switch between kubectl, Cloud Logging and Cloud Run logs.
-
Cluster: switch between different clusters when viewing Cloud Logging logs. This allows you to query logs from specific clusters instead of from all of them. For kubectl logs, this will only show the current active cluster.
-
- Issue #176: Cloud Code will no longer continually switch user context to the output window!
- Issue #201: Fixed an issue where the Logs Viewer hangs when you don’t have permission to list all namespaces.
- Fixed an issue where Open with Cloud Code would not clone a repository in some cases.
- Fixed an issue where Cloud Shell would fail to create an SSH configuration when the gcloud command-line tool prompted for survey participation.
- Fixed an issue in the "Open in Cloud Code" feature
- Fixed an issue where logs in "Cloud Code Yaml Support" output channel will grab focus
- Minor bug fixes
- Enable the deprecated
Cloud Code: DeployandCloud Code: Continuous Deploycommands along side with the new and recommended commandCloud Code: Run on Kubernetes. You can now continue with your existing workflow while taking the time to make a switch!
- Run in Kubernetes: Cant disable the watch (#198)
-
Client Library Browser: Manage your Google Cloud APIs with Cloud Code’s freshest new feature: the Client Library Browser. View all available Google Cloud APIs, enable an API, view API status (enabled or disabled), and install client libraries to consume an API, all from within your IDE.
-
Cloud Code: Run on Kubernetes:
A new command, ‘Cloud Code: Run on Kubernetes,’ has been added that lets you run your kubernetes application and view it live. 'Cloud Code: Deploy' and 'Cloud Code: Continuous Deploy' commands have been deprecated in favor of this command. For more details on this change, please refer to this link.
-
In addition to the above features, this release also includes some bug fixes. You can view the full list here.
We are pleased to announce that Cloud Code is now GA!
-
Cloud Shell Integration Use the ‘Open with Cloud Code’ feature to quickly get started using Google Cloud Platform. It uses a remote development environment in Cloud Shell which means you’ll get to skip setup and start developing with Cloud Code with the click of a button.
With ‘Open with Cloud Code’, you can edit, run, and debug code; as well as utilize all of Cloud Code's features directly from inside Cloud Shell. Visual Studio Code's integrated terminal allows direct interaction with command line utilities running in Cloud Shell, such as the gcloud command-line tool, skaffold, and kubectl.
-
YAML editing Get started with Cloud Build with Cloud Code’s built-in snippets for Cloud Build and Cloud Build trigger YAML files.
- Added ability to view and edit yaml of Ingress resource (#158)
-
Logs Viewer Browse through and filter Kubernetes cluster logs easily using the new Logs Viewer. For clusters that do not support Stackdriver logging cluster logs will now be colorized.
-
Dependency Installer Cloud Code will manage kubectl and Skaffold CLI dependencies automatically. This can be controlled using the
cloudcode.auto-installsetting.
-
YAML Editing Create and modify YAML with Cloud Code’s richer YAML editing experience for these configuration types:
-
Colorized Streams Deployment and Continuous Deployment output streams will be colorized to highlight key events.
