Release v0.4.0

.github/CODEOWNERS

@@ -1,3 +1,3 @@
-/.azure-pipelines @Microsoft/documentdb-for-vscode-engineering
-/.config @Microsoft/documentdb-for-vscode-engineering
-* @Microsoft/documentdb-for-vscode-engineering
+/.azure-pipelines @microsoft/documentdb-for-vscode-core-engineering
+/.config @microsoft/documentdb-for-vscode-core-engineering
+* @microsoft/documentdb-for-vscode-core-engineering

.github/copilot-instructions.md

@@ -68,6 +68,7 @@ This document provides comprehensive guidelines and context for GitHub Copilot t
 - Use l10n for any user-facing strings with `vscode.l10n.t()`.
 - Use `npm run prettier-fix` to format your code before committing.
 - Use `npm run lint` to check for linting errors.
+- Use `npm run build` to ensure the project builds successfully (do not use `npm run compile`).
 - Use `npm run l10n` to update localization files in case you change any user-facing strings.
 - Ensure TypeScript compilation passes without errors.
 
@@ -422,3 +423,69 @@ const message = vscode.l10n.t(
 - Ensure compatibility with Node.js version specified in `.nvmrc`.
 - Follow the project's ESLint configuration for consistent code style.
 - Use webpack for bundling and ensure proper tree-shaking.
+
+---
+
+## Null Safety with nonNull Helpers
+
+**Always use the nonNull utility functions** from `src/utils/nonNull.ts` instead of manual null checks for better error reporting and debugging.
+
+#### Available Functions
+
+- **`nonNullProp()`**: Extract and validate object properties
+- **`nonNullValue()`**: Validate any value is not null/undefined
+- **`nonNullOrEmptyValue()`**: Validate strings are not null/undefined/empty
+
+#### Parameter Guidelines
+
+Both `message` and `details` parameters are **required** for all nonNull functions:
+
+- **`message`**: Use the actual member access or assignment LHS from your code. Since this is open source, use real variable names:
+  - Member access: `'selectedItem.cluster.connectionString'`
+  - Wizard context: `'wizardContext.password'`
+  - Local variables: `'connectionString.match(...)'`
+
+- **`details`**: Use the actual file base name where the code is located:
+  - Examples: `'ExecuteStep.ts'`, `'ConnectionItem.ts'`, `'DatabaseTreeItem.ts'`
+  - Keep it short, use the actual file name, don't create constants
+
+#### Usage Examples
+
+```typescript
+// ✅ Good - Property extraction with validation
+const connectionString = nonNullProp(
+  selectedItem.cluster,
+  'connectionString',
+  'selectedItem.cluster.connectionString',
+  'ExecuteStep.ts',
+);
+
+// ✅ Good - Value validation
+const validatedConnection = nonNullValue(await getConnection(id), 'getConnection(id)', 'ConnectionManager.ts');
+
+// ✅ Good - String validation (not empty)
+const databaseName = nonNullOrEmptyValue(
+  wizardContext.databaseName,
+  'wizardContext.databaseName',
+  'CreateDatabaseStep.ts',
+);
+
+// ✅ Good - Manual null check for user-facing validation
+if (!userInput.connectionString) {
+  void vscode.window.showErrorMessage(vscode.l10n.t('Connection string is required'));
+  return;
+}
+
+// ❌ Bad - Manual null checks for internal validation (use nonNull helpers instead)
+if (!selectedItem.cluster.connectionString) {
+  throw new Error('Connection string is required'); // This should use nonNullProp
+}
+
+// ❌ Bad - Generic parameter values
+const value = nonNullValue(data, 'some value', 'file.ts');
+```
+
+**When to use each approach:**
+
+- **Use nonNull helpers**: For internal validation where you expect the value to exist (programming errors)
+- **Use manual checks**: For user-facing validation with localized error messages shown to users

.github/workflows/main.yml

@@ -60,7 +60,7 @@ jobs:
                       ${{ runner.os }}-node-
 
             - name: 📦 Install Dependencies (npm ci)
-              run: npm ci
+              run: npm ci --verbose
 
             - name: 🌐 Check Localization Files
               run: npm run l10n:check

.vscode/launch.json

@@ -3,36 +3,7 @@
   "version": "0.2.0",
   "configurations": [
     {
-      "name": "Launch Extension",
-      "type": "extensionHost",
-      "request": "launch",
-      "runtimeExecutable": "${execPath}",
-      "args": ["--extensionDevelopmentPath=${workspaceFolder}"],
-      "outFiles": ["${workspaceFolder}/out/**/*.js"],
-      "preLaunchTask": "${defaultBuildTask}",
-      "env": {
-        "DEBUGTELEMETRY": "true", // set this to "verbose" to see telemetry events in debug console
-        "NODE_DEBUG": ""
-      }
-    },
-    {
-      "name": "Launch Extension + Host",
-      "type": "extensionHost",
-      "request": "launch",
-      "runtimeExecutable": "${execPath}",
-      "args": [
-        "--extensionDevelopmentPath=${workspaceFolder}",
-        "--extensionDevelopmentPath=${workspaceFolder}/../vscode-azureresourcegroups"
-      ],
-      "outFiles": ["${workspaceFolder}/out/**/*.js"],
-      "preLaunchTask": "${defaultBuildTask}",
-      "env": {
-        "DEBUGTELEMETRY": "verbose", // set this to "true" to suppress telemetry events in debug console
-        "NODE_DEBUG": ""
-      }
-    },
-    {
-      "name": "Launch Extension (webpack)",
+      "name": "Defaut: Launch Extension (webpack)",
       "type": "extensionHost",
       "request": "launch",
       "runtimeExecutable": "${execPath}",
@@ -64,7 +35,7 @@
       }
     },
     {
-      "name": "Launch Extension + Host (webpack)",
+      "name": "Launch Extension + AzureResources (webpack)",
       "type": "extensionHost",
       "request": "launch",
       "runtimeExecutable": "${execPath}",
@@ -74,31 +45,46 @@
         "--extensionDevelopmentPath=${workspaceFolder}/../vscode-azureresourcegroups"
       ],
       "outFiles": ["${workspaceFolder}/dist/**/*.js", "${workspaceFolder}/../vscode-azureresourcegroups/out/**/*.js"],
+      "preLaunchTask": "Watch",
+      "autoAttachChildProcesses": true,
+      "debugWebWorkerHost": true,
+      "debugWebviews": false,
+      "trace": true,
+      "sourceMaps": true,
+      "pauseForSourceMap": true,
+      "skipFiles": ["**/node_modules/**"],
+      "smartStep": true,
+      "sourceMapRenames": true,
+      "rendererDebugOptions": {
+        "webRoot": "${workspaceFolder}"
+      },
       "resolveSourceMapLocations": ["${workspaceFolder}/dist/**", "!**/node_modules/**"],
       "sourceMapPathOverrides": {
         "./*": "${workspaceFolder}/*"
       },
-      "preLaunchTask": "Watch",
       "env": {
         "DEBUGTELEMETRY": "verbose", // set this to "true" to suppress telemetry events in debug console
         "NODE_DEBUG": "",
         "DEBUG_WEBPACK": "",
         "DEVSERVER": "true",
         "STOP_ON_ENTRY": "false" // stop on entry is not allowed for "type": "extensionHost", therefore, it's emulated here (review main.ts)
       },
-      "debugWebWorkerHost": true,
-      "rendererDebugOptions": {
-        "pauseForSourceMap": true,
-        "sourceMapRenames": true,
-        "sourceMaps": true,
-        "webRoot": "${workspaceFolder}/src/webviews/"
-      },
-      "skipFiles": ["**/node_modules/**"],
-      "smartStep": true,
-      "sourceMapRenames": true,
-      "sourceMaps": true,
-      "pauseForSourceMap": true,
-      "trace": true
+    },
+    {
+      "name": "Launch Extension + Host",
+      "type": "extensionHost",
+      "request": "launch",
+      "runtimeExecutable": "${execPath}",
+      "args": [
+        "--extensionDevelopmentPath=${workspaceFolder}",
+        "--extensionDevelopmentPath=${workspaceFolder}/../vscode-azureresourcegroups"
+      ],
+      "outFiles": ["${workspaceFolder}/out/**/*.js"],
+      "preLaunchTask": "${defaultBuildTask}",
+      "env": {
+        "DEBUGTELEMETRY": "verbose", // set this to "true" to suppress telemetry events in debug console
+        "NODE_DEBUG": ""
+      }
     },
     {
       "name": "Launch Tests",

CHANGELOG.md

@@ -1,5 +1,18 @@
 # Change Log
 
+## 0.4.0
+
+### New Features & Improvements
+
+- **Deep Azure Integration**: Introduces deep integration with the Azure Resources extension, providing a unified experience for discovering and managing Azure Cosmos DB for MongoDB (RU and vCore) resources directly within the Azure view. [#58](https://github.com/microsoft/vscode-documentdb/issues/58)
+- **Service Discovery for MongoDB (RU)**: Adds a new service discovery provider for Azure Cosmos DB for MongoDB (RU) resources, enabling effortless connection and authentication through the Discovery View. [#244](https://github.com/microsoft/vscode-documentdb/issues/244)
+- **Official DocumentDB Logo**: Updated the extension's icon and branding to use the official DocumentDB logo for better brand recognition and consistency. [#246](https://github.com/microsoft/vscode-documentdb/pull/246)
+
+### Fixes
+
+- **Connection String Password Support**: Restored support for passwords when creating new connections using a connection string, fixing a regression that affected certain configurations. [#247](https://github.com/microsoft/vscode-documentdb/pull/247)
+- **Improved Debugging Information**: Enhanced internal error handling for `nonNull` checks to include file context, making it easier to diagnose and triage issues. [#236](https://github.com/microsoft/vscode-documentdb/pull/236)
+
 ## 0.3.1
 
 ### Fixes

README.md

@@ -4,6 +4,7 @@
 
 [![Version](https://img.shields.io/visual-studio-marketplace/v/ms-azuretools.vscode-documentdb.svg)](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-documentdb)
 
+<img src="resources/readme/documentdb-logo.png" alt="DocumentDB Logo" style="width:40%; min-width:180px; max-width:320px; height:auto;" />
 <!-- endregion exclude-from-marketplace -->
 
 **A powerful, open-source DocumentDB and MongoDB GUI for everyone.**

docs/index.md

@@ -62,7 +62,8 @@ This section contains detailed documentation for specific features and concepts
 
 Explore the history of updates and improvements to the DocumentDB for VS Code extension. Each release brings new features, enhancements, and fixes to improve your experience.
 
-- [0.3](./release-notes/0.3.md)
+- [0.4](./release-notes/0.4.md)
+- [0.3, 0.3.1](./release-notes/0.3.md)
 - [0.2.4](./release-notes/0.2.4.md)
 - [0.2.3](./release-notes/0.2.3.md)
 - [0.2.2](./release-notes/0.2.2.md)

docs/learn-more/service-discovery-azure-cosmosdb-for-mongodb-ru.md

@@ -0,0 +1,49 @@
+<!-- filepath: /home/tomek/github/ms/vscode-documentdb/docs/learn-more/service-discovery-azure-cosmosdb-for-mongodb-ru.md -->
+<!-- Learn More Section Badge or Breadcrumb -->
+
+> **Learn More** &mdash; [Back to Learn More Index](./index)
+
+---
+
+# Azure CosmosDB for MongoDB (RU) Service Discovery Plugin
+
+The **Azure CosmosDB for MongoDB (RU)** plugin is available as part of the [Service Discovery](./service-discovery) feature in DocumentDB for VS Code. This plugin helps you find and connect to Azure Cosmos DB accounts provisioned with Request Units (RU) for the MongoDB API by handling authentication, resource discovery, and connection creation from inside the extension.
+
+## How to Access
+
+You can access this plugin in two ways:
+
+- From the `Service Discovery` panel in the extension sidebar.
+- When adding a new connection, select the `Azure CosmosDB for MongoDB (RU)` option.
+
+![Service Discovery Activation](./images/service-discovery-activation.png)
+
+## How It Works
+
+When you use the Azure CosmosDB for MongoDB (RU) plugin, the extension performs the following steps:
+
+1. **Authentication:**
+   The plugin uses your Azure credentials available in VS Code. If needed, it will prompt you to sign in via the standard Azure sign-in flows.
+
+2. **Subscription Discovery:**
+   The plugin lists subscriptions available to your account so you can pick where to search for resources.
+
+3. **Account Discovery:**
+   The provider queries Azure using the CosmosDB Management Client and filters results by the MongoDB "kind" for RU-based accounts. This ensures the list contains accounts that support the MongoDB API under RU provisioning.
+
+4. **Connection Options:**
+   - Expand an account entry to view databases and connection options.
+   - Save an account to your `DocumentDB Connections` list using the context menu or the save icon next to its name.
+   - When connecting or saving, the extension will extract credentials or connection details from Azure where available. If multiple authentication methods are supported, you will be prompted to choose one.
+
+## Additional Notes
+
+- You can filter subscriptions in the Service Discovery panel to limit the scope of discovery if you have access to many subscriptions.
+- The provider reuses shared authentication and subscription selection flows used across other Service Discovery plugins.
+- If you save a discovered account, the saved connection will appear in your Connections view for later use.
+
+## Feedback and Contributions
+
+If you have suggestions for improving this provider or would like to add support for additional resource types, please [join the discussion board](https://github.com/microsoft/vscode-documentdb/discussions) and share your feedback.
+
+---

docs/learn-more/service-discovery.md

@@ -23,8 +23,9 @@ This approach allows you to connect to a variety of platforms without needing to
 
 ## Available Service Discovery Plugins
 
-Currently, two service discovery plugins are available:
+Currently, the following service discovery plugins are available:
 
+- **[Azure CosmosDB for MongoDB (RU)](./service-discovery-azure-cosmosdb-for-mongodb-ru)**
 - **[Azure CosmosDB for MongoDB (vCore)](./service-discovery-azure-cosmosdb-for-mongodb-vcore)**
 - **[Azure VMs (DocumentDB)](./service-discovery-azure-vms)**
 

docs/release-notes/0.4.md

@@ -0,0 +1,62 @@
+<!-- Release Notes Section Badge or Breadcrumb -->
+
+> **Release Notes** — [Back to Home](../index.md)
+
+---
+
+# DocumentDB for VS Code Extension v0.4
+
+We are excited to announce the release of **DocumentDB for VS Code Extension v0.4**. This is a landmark update that introduces deep integration with the Azure ecosystem, adds powerful new service discovery capabilities, and aligns our branding with the official [DocumentDB](https://documentdb.io) identity.
+
+<p align="center"><img src="images/0.4.0_documentdb-logo.png" alt="DocumentDB Logo" style="width:40%; min-width:180px; max-width:320px; height:auto;" /></p>
+
+This release improves how developers working with Azure discover, connect to, and manage their MongoDB-compatible databases, all from within a unified VS Code experience.
+
+## What's New in v0.4
+
+### ⭐ **Deep Integration with the Azure Resources Extension** ([#58](https://github.com/microsoft/vscode-documentdb/issues/58))
+
+> **Note: This is a staged feature release**
+> It is coordinated across three extensions: DocumentDB for VS Code, Azure Databases, and Azure Resources.
+>
+> The full integration experience will be enabled when the Azure Resources extension update is released in the coming days.
+
+This release improves the user experience for developers in the Azure ecosystem by integrating directly with the **Azure Resources extension**. The DocumentDB extension now takes ownership of the **Azure Cosmos DB for MongoDB (RU)** and **(vCore)** nodes directly within the Azure resource tree.
+
+This collaboration provides a single, authoritative view for all your Azure resources while enriching the experience with the specialized MongoDB tooling that our extension provides.
+
+- **Unified Azure View**: Discover and manage your MongoDB resources directly within the familiar Azure Resources view without needing to switch between extensions.
+- **Rich MongoDB Tooling**: Access all of DocumentDB for VS Code's features - like data exploration, query scrapbooks, and management commands - directly from the Azure tree.
+- **Coordinated Orchestration**: The Azure Resources extension now directs which extension manages which resource, ensuring a stable and conflict-free experience.
+- **Automatic Migration**: Existing MongoDB connections are automatically migrated for an efficient transition.
+
+<p align="center"><img src="./images/0.4.0_azure_resources.png" alt="Authentication Method Selection" width="360" style="max-width:100%;height:auto;"></p>
+
+### 2️⃣ **Service Discovery for Azure Cosmos DB for MongoDB (RU)** ([#244](https://github.com/microsoft/vscode-documentdb/issues/244))
+
+We've expanded our service discovery capabilities by adding a dedicated provider for **Azure Cosmos DB for MongoDB (RU)** resources. This complements our existing vCore provider and makes connecting to RU-based accounts easier than ever.
+
+- **New Discovery Option**: A new "Azure Cosmos DB for MongoDB (RU)" provider is now available in the Discovery View.
+- **Consistent User Experience**: The new provider uses the same authentication and wizard-based workflow (select subscription → select cluster → connect) that users are already familiar with.
+- **Optimized for RU**: The provider uses RU-specific Azure APIs to ensure accurate and reliable discovery.
+
+[Learn more about Service Discovery →](../learn-more/service-discovery.md)
+
+### 3️⃣ **Official DocumentDB Logo and Branding** ([#246](https://github.com/microsoft/vscode-documentdb/pull/246))
+
+The extension has been updated with the **official DocumentDB logo and branding**. This change provides better brand recognition and creates a more consistent visual identity across the DocumentDB ecosystem. You'll see the new logo in the VS Code activity bar, the marketplace, and throughout our documentation.
+
+## Key Fixes and Improvements
+
+#### 🐛 **Restored Password Support for Connection Strings** ([#247](https://github.com/microsoft/vscode-documentdb/pull/247))
+
+We've fixed a regression that prevented users from creating new connections using a connection string with a password in certain configurations. The validation logic in the connection workflow has been improved to ensure all valid connection strings are handled correctly.
+
+#### 🛠️ **Improved Debugging with Enhanced Error Details** ([#236](https://github.com/microsoft/vscode-documentdb/pull/236))
+
+As part of our commitment to stability, we've enhanced our internal error handling. `nonNull` checks now include file context in their error messages, making it significantly easier for our team to diagnose and triage reported issues.
+
+## Changelog
+
+See the full changelog entry for this release:
+➡️ [CHANGELOG.md#040](https://github.com/microsoft/vscode-documentdb/blob/main/CHANGELOG.md#040)

eslint.config.mjs

@@ -52,7 +52,20 @@ export default ts.config(
             'no-case-declarations': 'error',
             'no-constant-condition': 'error',
             'no-inner-declarations': 'error',
-            'no-restricted-imports': ['error', { patterns: ['**/*/extension.bundle'] }],
+            'no-restricted-imports': [
+                'error',
+                {
+                    paths: [
+                        {
+                            name: '@microsoft/vscode-azext-utils',
+                            importNames: ['nonNullValue', 'nonNullProp', 'nonNullOrEmptyValue'],
+                            message:
+                                "Do not import nonNull helpers from '@microsoft/vscode-azext-utils'. Use the local 'src/utils/nonNull' instead.",
+                        },
+                    ],
+                    patterns: ['**/*/extension.bundle'],
+                },
+            ],
             'no-unused-vars': ['error', { argsIgnorePattern: '^_' }],
             'no-useless-escape': 'error',
             'license-header/header': [

extension.bundle.ts

@@ -19,6 +19,7 @@ export { ObjectId } from 'bson';
 // The tests should import '../extension.bundle.ts'. At design-time they live in tests/ and so will pick up this file (extension.bundle.ts).
 // At runtime the tests live in dist/tests and will therefore pick up the main webpack bundle at dist/extension.bundle.js.
 export { AzureAccountTreeItemBase, createAzureClient } from '@microsoft/vscode-azext-azureutils';
+// eslint-disable-next-line no-restricted-imports -- bundle intentionally re-exports many helpers for tests; nonNull helpers are provided locally in this repo
 export * from '@microsoft/vscode-azext-utils';
 export { isWindows, wellKnownEmulatorPassword } from './src/constants';
 export { connectToClient, isCosmosEmulatorConnectionString } from './src/documentdb/scrapbook/connectToClient';