CHANGELOG.md

Cloud Code for Visual Studio Code Release Notes

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.

Version 1.13.0 (June 2021)

New Features

• Simplified combined Kubernetes Explorer and Google Kubernetes Engine Explorer experience Google Kubernetes Engine Explorer is now merged into Kubernetes Explorer for a unified experience. Kubernetes Explorer now takes you to the Cloud Console for GKE cluster management operations, such as creation and deletion of clusters. Managing cluster types other than minikube and GKE is no longer supported; you’ll need to use the cloud provider's tools to create other cluster types and add them to your KubeConfig.

• Iterative debugging When you're in debug mode and you make a change to your project, Cloud Code now redeploys your project and sets up a new debug session. You can toggle this feature with the “watch” flag in the launch configuration of your project. By default, “watch” is set to true (similar to run mode).

• Change Build Environment on the fly If, when you begin your Run/Debug on Kubernetes session, Cloud Code detects that you aren't using a recommended build environment for your development environment, you will have a chance to modify the build environment in your current Skaffold profile or change your Skaffold profile to one that uses a recommended build environment.

• Auto-start docker prompt When running or debugging Kubernetes and Cloud Run, you now are presented with a new quick-pick menu to start Docker service as part of the dependency check.

Updates

• Managed Cloud SDK performance improvements Improvements to the managed Cloud SDK installation process means much of Cloud Code functionality is now available 2 to 5x times faster upon installing the extension. Additionally, these improvements come with reduced memory consumption and fewer fatal/corruption errors.

• Improvement to Cloud Run local development webview The webview now immediately shows any input error without needing to click “Run” button.

Bug Fixes

• Fixed the application name to use kebab case while cloning template repos. #430

Version 1.12.1 (June 2021)

Bug Fixes

• Fixed an issue where debug path mapping was broken with Skaffold 1.25.0.

Version 1.12.0 (May 2021)

New Features

• Build with Cloud Build When Deploying to Cloud Run or Running/Debugging on Kubernetes, you can select to build with Cloud Build. Cloud Code will guide you through setting up Cloud Build in your project, and then will automatically configure and submit builds for each image to the cloud. Cloud Code will also make suggestions to use Cloud Build based on your current development environment. For example, Cloud Build will be recommended for deployment to GKE from ARM based clients because of the processor architecture mismatch.

• Minikube Auto Stop Improved client side performance for auto scheduling the minikube clusters started by cloud code.

Updates

• Cloud Run Cloud Run managed deployments now allow up to 8 GiB memory for any deployments with at least 2 vCPUs allocated.

Bug Fixes

• Fixed an issue where validation to have docker installed is not needed when using Google Cloud Build for deploying applications.
• Support multiple skaffold configurations in one single configuration file. #424

Version 1.11.1 (May 2021)

Bug Fixes

• Fixed an issue where views were slow to load in Visual Studio Code 1.56.0.

Version 1.11.0 (April 2021)

Updates

• Updated Explorer setup experience: Explorers that require any setup steps now guide you through the process of logging in, selecting a project, and enabling any required APIs in a more interactive and friendly way.
• Streamlined Explorer views: Secret values in Secret Tree View and ConfigMaps’ values in Kubernetes Explorer are now accessible in read-only (instead of editable) documents.
• Enhanced minikube management: Multi-step quick pick menu for minikube now comes with cancel and back buttons for easy navigation.
• Prompt toggling for M1 macs: Suppress warnings that the extension might not work on M1 with improved prompt toggling. #415
• Quieter watch mode: Watch mode no longer displays Deployment Successful prompts.
• Improved error state: Get unstuck quicker with more proactive error messaging in the Kubernetes local development webview.

Bug Fixes

• Fixed an issue where .NET debugger was using the wrong debugger path with Skaffold. Added debuggerPath and processId field to the .NET debugger to enable setting the debugger path and process ID of the debuggee. #397, #418
• Fixed an issue where the artifacts property needed to be specified under the default skaffold’s profile even when there were additional profiles. #398
• Fixed an issue where multiple prompts to install necessary version of Cloud SDK that take up screen space. #414
• Fixed an issue where the Enable Cloud Run API button was disabled in the Cloud Run WebView.

Version 1.10.0 (March 2021)

New Features

• GKE Autopilot Cluster Creation: You can now create GKE Autopilot clusters with the Cluster Creation wizard for a more managed mode of operation, taking advantage of Autopilot’s auto-provisioning and autoscaling of GKE infrastructure. For more details on how to configure your cluster, see the Adding a cluster guide.

• Initial support for M1-based Apple Silicon Macs: With this update, you can now build and work locally on your M1 Mac with Cloud Code, minikube, and Skaffold for ARM64 targets. Please note that Rosetta 2 is currently required as several dependencies are still x86/64 only, refer to instructions. Follow this GitHub issue for more information and to track the latest updates.

Updates

• Dry-run YAML Files: Perform a dry run of your configuration and check its validity using the newly added dry-run command (with either client-side or server-side validation). Dry-run evaluates the resource request without persisting objects to storage, and displays the validation result as a toast notification. To discover more commands to help with editing your configuration files, see the YAML editing guide.

Bug Fixes

• Fixed passing environment variables to skaffold.yaml for customizing build arguments. #394, #378
• Fixed the ability to specify skaffold tags (like docker image tags) through launch config for customization. #335
• Fixed skaffold workspace to support config from non-root directory. #377
• Fixed the need to avoid specifying service/container name when Cloud Run is running on an emulator. #295
• Fixed an issue where the insiders build gave an inactionable error message on network failures. #404

Version 1.9.0 (February 2021)

New Features

• GKE Autopilot: You can now deploy your application to GKE Autopilot right from VSCode Cloud Code menu. GKE Autopilot is a new mode of operation of GKE clusters where infrastructure is auto managed by Google, provides auto provisioning and auto scaling of GKE infra to the end user. Overview of GKE Autopilot.
• Pre-release Channel: You can now use insider builds for trying out upcoming features and give us feedback before they are publicly released. You can go to cloud code settings “Cloud Code: Update Channel” and select an insider build that you want to try out. This will help us to make sure your development tools aren’t affected by the release of Cloud Code Plugin.

Bug Fixes

• Fixed to avoid checking for dependencies while deploying to K8 if deps are not auto managed. #375
• Fixed broken link to browse launch.json config in the output window of deployment logs.

Version 1.8.0 (January 2021)

New Features

• Custom templates: You can now create applications from custom templates! Cloud Code offers the option of importing a Git template repository so that teams can get started quickly from a standard set of starter applications, services, and infrastructure configuration best suited to teams’ organizational policies. To read more about templates and how to get started, head over to setting up a template repository guide.

• Cloud Code Status Bar options: Discover more about your currently active sessions with these additions to the Cloud Code status bar.
  • Open Service URL: Instead of scrolling through the logs to find the service URL, you can now open the application service URL in a web browser directly from the status bar.
  • Open Deployment Logs: Open the application logs with the Cloud Code Logs Viewer. This populates the necessary filters in the Logs Viewer for the selected deployment.
  • Turn on/off Watch Mode: Toggle watch mode (not available for debug session currently). This allows you to turn on/off watch mode for the current active run session without stopping, changing the launch.json watch field, and redeploying. Note that this toggle only affects the current session and not subsequent ones.

• New sample application READMEs: When you create a new sample application with Cloud Code, the new README gives updated guidance on next steps to help you get more out of Cloud Code.

Updates

• .NET launch debugging support: In addition to the attach configuration, Cloud Code now supports a launch configuration for .NET. You can now deploy and attach to a .NET application with a single configuration.
• New home for Cloud Run properties: Cloud Run properties no longer show up in a separate view. They can be found conveniently in the Cloud Run Explorer under Properties.

Bug Fixes

• Fixed Cloud SDK auto dependency installation corruption issue on Windows. #346
• Fixed Python enabling to debug external sources. #328
• Fixed YAML outline to handle arrays of objects. #339
• Fixed available cluster listing when faced with restricted project permissions. #318
• Fixed docs for Cloud Run service config, discovering logs, stopping the emulator. #298
• Fixed an issue where installation of minikube is not required for deploying to Kubernetes cluster. #280
• Fixed an issue to display deployment progress failures on the right side status bar.
• Fixed an issue that allows users to switch accounts without running into permission requests on older accounts.

Version 1.7.2 (January 2021)

Bug Fixes

• Fix an issue where dependencies path gets invalidated on Windows. #362
• Fix an issue where Cloud SDK in the path gets corrupted on Windows since there is reentry while installing dependencies. #347

Version 1.7.1 (December 2020)

New Features

• Project Selection Flows: The project selector has been refreshed to deliver an improved UX, faster load times, and recent projects listed first. The project selection/login/logout should sync between all webviews and explorers.

• Refresh GKE Explorer: The look and feel of the GKE Explorer is now consistent with the Secret Manager Explorer and the Cloud Run Explorer.
• YAML Editing Support: YAML editing support can now accurately be limited to a subdirectory under the working directory by setting cloudcode.yaml.yamlFileMatcher. Learn more

Updates

• Replace general icons with VSCode Codicons for commands.
• Improved Cloud Run (fully managed) support:
• Allocate up to 4 vCPUs to container instances with the increased limit.

Bug Fixes

• Fix .NET debugging fails to open a source file when the breakpoint is hit. #292
• Refresh AKS cluster UI after modifying the active subscription. #239

Version 1.7.0 (October 2020)

• 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.

• 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.

Updates

• 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.

Bug Fixes

• 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. #286 #313

• 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.

• Regions are not available when I use "Deploy to Cloud Run". #314

Version 1.6.0 (Septemeber 2020)

New Features

• 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.

  

Version 1.5.0 (August 2020)

New Features

• 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.

  

Version 1.4.0 (May 2020)

New features

• 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.

  

Bug Fixes

• Cloud Code will now allow you to browse and switch between Kubernetes contexts. #131
• You can now browse PersistentVolumeClaim in the Kubernetes Explorer. #193

Version 1.3.0 (April 2020)

We are pleased to announce Cloud Run support in Cloud Code for VS Code!

New Features

• 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.

  

Other Changes

• 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.

Bug Fixes

• Add support for Google Cloud Run. #231
• Hanging while installing dependencies. #227
• Cannot start debugger for .NetCore project. #225
• GKE Explorer does not work in windows 10. #224
• Add Configuration to Existing Project is broken. #223
• Add a guidance message in case no Kubernetes manifest are present. #203

Version 1.2.1 (March 2020)

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.

Version 1.2.0 (February 2020)

New features

• 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.

    

Bug Fixes

• Cloud Code will no longer continually switch user context to the output window. #176
• Fixed an issue where the Logs Viewer hangs when you don’t have permission to list all namespaces. #201
• 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.

Version 1.1.2 (February 2020)

Notable Fixes

• 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

Version 1.1.1 (February 2020)

New Features

• Enable the deprecated Cloud Code: Deploy and Cloud Code: Continuous Deploy commands along side with the new and recommended command Cloud Code: Run on Kubernetes. You can now continue with your existing workflow while taking the time to make a switch!

Bug Fixes

• Run in Kubernetes: Cant disable the watch (#198)

Version 1.1.0 (January 2020)

New Features

• 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.

Version 1.0.0 (November 2019)

We are pleased to announce that Cloud Code is now GA!

New Features

• 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.

  

Bug Fixes

• Added ability to view and edit yaml of Ingress resource. #158

Version 0.0.13 (November 2019)

New Features

• 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-install setting.

  

• YAML Editing Create and modify YAML with Cloud Code’s richer YAML editing experience for these configuration types:

  • Anthos Config Management (link)

  • Config Connector (link)

  • Migrate for Anthos (link)

    

• Colorized Streams Deployment and Continuous Deployment output streams will be colorized to highlight key events.

  

Notable Fixes

• Improved extension activation time by removing dependency on language server activation. (#140)
• Reduced the memory footprint of Kubernetes Cluster Explorer to allow handling large clusters.
• Included various stability fixes. (#147) (#101)