feat(azure): add sensor-single module with VNet flow log support#4
Merged
Conversation
Creates a user-assigned Managed Identity with Storage Blob Data Reader access to a storage account containing Azure VNet Flow Logs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds the Azure sensor-single module (single VM deployment) with vnet_flow_storage_access submodule, and a flow-sensor example mirroring the existing AWS flow-sensor example for parity. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
terraform fmt alignment fixes in main.tf and test file, and regenerate README docs blocks to match terraform-docs output format (anchor tags, sorted inputs, complete variable list). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The list default values need `<pre>[<br/> ...]</pre>` format to match terraform-docs output exactly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use a full-length RSA public key in flow-sensor test fixtures to pass Azure VM key validation. Add AVD-AZU-0047 and AVD-AZU-0051 to Trivy ignore list since the sensor module intentionally exposes configurable CIDRs for monitoring ingress and outbound Fleet connectivity. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
thathaneydude
requested changes
Jun 15, 2026
- Add section comments to variables.tf documenting variable groups - Update community_string description to mention Fleet - Fix submodule README example source to use full GitHub URL - Link scripts/azure/copy-azure-image.sh in prerequisites Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
a225602 to
c1eef2a
Compare
thathaneydude
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add the Azure single-instance sensor module (
modules/azure/sensor-single/) and a companionvnet_flow_storage_accesssubmodule for VNet flow log ingestion. Includes a completeflow-sensorexample demonstrating the deployment.Type of Change
Affected Modules
Checklist
terraform fmt -recursiveterraform validateon affected modulesTesting
terraform validatepasses onmodules/azure/sensor-single/and the exampleexamples/azure/flow-sensor/tests/example.tftest.hclvalidates module structure and variable wiringAdditional Notes
New files (17 files, +924 lines):
modules/azure/sensor-single/— Single Corelight sensor VM with dual NICs (management + monitoring), cloud-init config, optional public IP, and user-assigned managed identity supportmodules/azure/sensor-single/submodules/vnet_flow_storage_access/— Creates a managed identity withStorage Blob Data Readeron a flow logs storage accountexamples/azure/flow-sensor/— End-to-end example wiring the sensor to VNet flow log ingestion, withtfvars.exampleand test coverage