|
2 | 2 |
|
3 | 3 | Deploy the **Real-Time Intelligence Data Platform** solution accelerator using Azure Developer CLI - get a complete real-time analytics platform with Event Hub, Fabric Eventhouse, and KQL dashboards in minutes. |
4 | 4 |
|
5 | | -## 🚀 Quick Start |
| 5 | +## Quick Start |
6 | 6 |
|
7 | 7 | **One-command deployment** - Deploy everything with Azure Developer CLI ([prerequisites required](#prerequisites)). See also other available [deployment options](#deployment-options): |
8 | 8 |
|
@@ -70,8 +70,9 @@ Before starting, ensure your deployment identity has the following requirements. |
70 | 70 | - [ ] **`Microsoft.EventHub` Resource Provider Access**: Verify your Azure Subscription has Event Hub resource provider enabled |
71 | 71 |
|
72 | 72 | ### 🔗 API Permissions |
73 | | -- [ ] **Fabric REST API - Workspace Management**: Access to create and manage Fabric workspaces |
74 | | -- [ ] **Fabric REST API - Item Creation**: Access to create Eventhouses, KQL databases, and dashboards |
| 73 | +- [ ] **Service principals and managed identities support on Fabric REST API**: To use service principals and managed identities with Fabric REST APIs (GitHub actions require it), [enable the `Service principals can use Fabric` APIs tenant setting](https://learn.microsoft.com/rest/api/fabric/articles/identity-support) |
| 74 | +- [ ] **Fabric REST API - Workspace Management**: Access to create and manage Fabric workspaces ([see scopes](https://learn.microsoft.com/rest/api/fabric/articles/scopes)) |
| 75 | +- [ ] **Fabric REST API - Item Creation**: Access to create Eventhouses, KQL databases, and dashboards ([see scopes](https://learn.microsoft.com/rest/api/fabric/articles/scopes)) |
75 | 76 | - [ ] **Azure Event Hubs API**: Access to create and manage Event Hub resources |
76 | 77 |
|
77 | 78 | ### 💻 Software Requirements |
@@ -216,57 +217,74 @@ The solution includes comprehensive sample data for real-time analytics scenario |
216 | 217 |
|
217 | 218 | Choose your deployment environment based on your workflow and requirements. All options use the same [Deploy with AZD](#deploy-with-azd) commands with environment-specific setup. |
218 | 219 |
|
219 | | -| Environment | Best For | Setup Required | Notes | |
220 | | -|-------------|----------|----------------|-------| |
221 | | -| **[Local Machine](#local-machine)** | Full development control | Install [software requirements](#software-requirements) | Most flexible, requires local setup | |
222 | | -| **[Azure Cloud Shell](#azure-cloud-shell)** | Zero setup | Just a web browser | Pre-configured tools, session timeouts | |
223 | | -| **[GitHub Codespaces](#github-codespaces)** | Team consistency | GitHub account | Cloud development environment | |
224 | | -| **[Dev Container](#vs-code-dev-container)** | Standardized tooling | Docker Desktop + VS Code | Containerized consistency | |
| 220 | +| Environment | Setup Required | Notes | |
| 221 | +|-------------|----------------|-------| |
| 222 | +| **[Local Machine](#local-machine)** | Install [software requirements](#software-requirements) | Most flexible, requires local setup | |
| 223 | +| **[Visual Studio Code Dev Container](#visual-studio-code-dev-container)** | Docker Desktop + VS Code | Containerized consistency | |
| 224 | +| **[GitHub Codespaces](#github-codespaces)** | GitHub account | Cloud development environment | |
| 225 | +| **[Azure Cloud Shell](#azure-cloud-shell)** | Web browser | Pre-configured tools, session timeouts | |
| 226 | +| **[GitHub Actions](#github-actions)** | Azure service principal | Federated identity, automated deployment | |
225 | 227 |
|
226 | 228 | ### Local Machine |
| 229 | + |
227 | 230 | Deploy with full control over your development environment. |
228 | 231 |
|
229 | | -**Setup requirements**: Install the [software requirements](#software-requirements) |
| 232 | +**Setup**: Install the [software requirements](#software-requirements) |
230 | 233 |
|
231 | | -**Deployment**: Use the standard [Deploy with AZD](#deploy-with-azd) commands |
| 234 | +**Deployment**: Follow the [quick start steps](#quick-start) commands |
232 | 235 |
|
233 | | -### Azure Cloud Shell |
234 | | -Deploy from Azure's browser-based terminal with zero local installation. |
| 236 | +### Visual Studio Code Dev Container |
| 237 | +Deploy from a containerized environment for team consistency. |
235 | 238 |
|
236 | | -**Setup**: Open [Azure Cloud Shell](https://shell.azure.com) and install Azure Developer CLI: |
237 | | -```bash |
238 | | -curl -fsSL https://aka.ms/install-azd.sh | bash && exec bash |
239 | | -``` |
| 239 | +**Setup**: |
| 240 | +1. Install Visual Studio Code, [Docker Desktop](https://www.docker.com/products/docker-desktop) and [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) |
| 241 | +2. Clone repository and open in VS Code |
| 242 | +3. Reopen in container when prompted |
240 | 243 |
|
241 | | -**Deployment**: Run the [Deploy with AZD](#deploy-with-azd) commands (Azure CLI pre-authenticated) |
| 244 | +**Deployment**: All tools pre-installed - follow the [quick start steps](#quick-start) commands |
242 | 245 |
|
243 | 246 | ### GitHub Codespaces |
| 247 | + |
244 | 248 | Deploy from a cloud development environment with pre-configured tools. |
245 | 249 |
|
246 | 250 | **Setup**: |
247 | 251 | 1. Go to the repository |
248 | | -2. Click **Code** → **Codespaces** → **Create codespace** |
| 252 | +2. Click **Code** → **Codespaces** → **Create codespace on main** |
249 | 253 |
|
250 | | -**Deployment**: Install azd and run deployment commands with device authentication: |
| 254 | +**Deployment**: All tools pre-installed - follow the [quick start steps](#quick-start) commands |
| 255 | + |
| 256 | +### Azure Cloud Shell |
| 257 | + |
| 258 | +Deploy from Azure's browser-based terminal with zero local installation. |
| 259 | + |
| 260 | +**Setup**: Open [Azure Cloud Shell](https://shell.azure.com) and install Azure Developer CLI: |
251 | 261 | ```bash |
252 | | -# Install azd if needed |
253 | 262 | curl -fsSL https://aka.ms/install-azd.sh | bash && exec bash |
| 263 | +``` |
254 | 264 |
|
255 | | -# Use device code authentication |
256 | | -azd auth login --use-device-code |
| 265 | +**Deployment**: Follow the [quick start steps](#quick-start) commands |
257 | 266 |
|
258 | | -# Continue with deployment commands |
259 | | -``` |
| 267 | +### GitHub Actions |
260 | 268 |
|
261 | | -### VS Code Dev Container |
262 | | -Deploy from a containerized environment for team consistency. |
| 269 | +Deploy using automated CI/CD pipeline with GitHub Actions and Azure federated identity. |
263 | 270 |
|
264 | | -**Setup**: |
265 | | -1. Install [Docker Desktop](https://www.docker.com/products/docker-desktop) and [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) |
266 | | -2. Clone repository and open in VS Code |
267 | | -3. Reopen in container when prompted |
| 271 | +**Setup**: |
| 272 | +1. Fork the repository to your GitHub account |
| 273 | +2. Configure [Azure service principal with federated identity credentials](https://learn.microsoft.com/en-us/azure/developer/github/connect-from-azure-openid-connect) for GitHub Actions (recommened) |
| 274 | +3. Set repository variables in GitHub: |
| 275 | + - `AZURE_CLIENT_ID`: Service principal client ID |
| 276 | + - `AZURE_TENANT_ID`: Azure tenant ID |
| 277 | + - `AZURE_SUBSCRIPTION_ID`: Target subscription ID |
| 278 | + - `AZURE_ENV_NAME`: Environment name for resource naming |
| 279 | +4. Set optinall repository variables in GitHub if needed: |
| 280 | + - `FABRIC_WORKSPACE_ADMINISTRATORS`: Comma-separated admin identities |
| 281 | + - `FABRIC_ACTIVATOR_ALERTS_EMAIL`: Email for alert notifications |
268 | 282 |
|
269 | | -**Deployment**: All tools pre-installed - run [Deploy with AZD](#deploy-with-azd) commands directly |
| 283 | +**Deployment**: |
| 284 | +1. Navigate to **Actions** tab in your GitHub repository |
| 285 | +2. Select **CI/CD Azure - Real-Time Intelligence Operations** workflow |
| 286 | +3. Click **Run workflow** to trigger deployment |
| 287 | +4. Monitor deployment progress and view summary with Azure Portal links |
270 | 288 |
|
271 | 289 | --- |
272 | 290 |
|
@@ -359,8 +377,9 @@ The `azd down` command orchestrates a complete environment cleanup process that: |
359 | 377 |
|
360 | 378 | 1. **Removes Fabric Workspace Components**: Executes [`delete_fabric_rti.py`](../infra/scripts/fabric/delete_fabric_rti.py) via `predown` hook to safely delete workspace connections and components |
361 | 379 | 2. **Deletes Fabric Workspace**: Removes the Microsoft Fabric workspace and all associated items |
362 | | -3. **Deprovisions Azure Resources**: Removes all Azure infrastructure components including Event Hub and Fabric Capacity |
363 | | -4. **Preserves Local Environment**: Keeps your local development environment and configurations intact |
| 380 | +3. **Deletes Fabric connection**: Removes the Microsoft Fabric Event Hub connection |
| 381 | +4. **Deprovisions Azure Resources**: Removes all Azure infrastructure components including Event Hub and Fabric Capacity |
| 382 | +5. **Preserves Local Environment**: Keeps your local development environment and configurations intact |
364 | 383 |
|
365 | 384 | **Complete cleanup commands:** |
366 | 385 |
|
|
0 commit comments