Skip to content

Azure networking and function app bundles#36

Open
coryodaniel wants to merge 7 commits intomainfrom
example/0414-azure-networks
Open

Azure networking and function app bundles#36
coryodaniel wants to merge 7 commits intomainfrom
example/0414-azure-networks

Conversation

@coryodaniel
Copy link
Copy Markdown
Member

@coryodaniel coryodaniel commented Apr 13, 2026

Summary

  • Azure Virtual Network bundle with configurable address space, NSG per subnet, and Checkov-clean compliance
  • Azure Virtual WAN bundle with hub and optional VPN gateway, VLAN peering support
  • Azure Function App bundle (comprehensive) including App Service Plan, Storage Account, App Insights, Private Endpoints, and Recovery Vault
  • Artifact definitions for all three bundle types

Test plan

  • All three bundles published with --development and deployed to claude-test
  • Checkov compliance remediated (all passing)
  • VNet-VWAN optional binding (connecting VNets to shared WANs)
  • $md.immutable annotations review
  • Preset validation across dev/staging/prod
  • Operator guides
  • Halt-on-failure guards for production environments

🤖 Generated with Claude Code

Screenshot 2026-04-13 at 4 12 33 PM

coryodaniel and others added 7 commits April 13, 2026 15:15
User prompts:
- "a set of bundles for an azure customer"
- "Azure VNet, Virtual WAN, Azure Function App (app service plan, storage account, app insights, private endpoints, vault)"

Changes:
- Azure Virtual Network bundle with NSG per subnet, configurable address space
- Azure Virtual WAN bundle with hub and optional VPN gateway
- Azure Function App bundle with embedded App Service Plan, Storage Account,
  App Insights, Private Endpoints, and Recovery Vault
- Artifact definitions for all three bundle types
- Checkov compliance remediated across all bundles

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ides

User prompts:
- "VNet should optionally receive a WAN and bind to it if present"
- "What $md.immutable annotations make sense across all three"
- "$md.enum for subnet selection"
- "halt on failure if md-target tag has prd, prod, or production"
- "useful operator guides please"
- "how do I give it source code"
- "are we passing useful data across connections"
- "icons from massdriver-cloud/icons"

Changes:
- VNet: optional azure_virtual_wan connection with auto hub peering
- All three: $md.immutable on location, CIDR, runtime, WAN type
- Function App: $md.enum on subnet_name pulls from connected VNet
- All three: halt_on_failure uses JQ to only halt on prd/prod/production targets
- Operator guides for all three bundles (VNet rewritten, VWAN+FuncApp new)
- Function App artifact exports connection_string + principal_id
- Sensitive markers on instrumentation key and connection string
- Icons on all three artifact definitions
- source_url fixed to massdriver-cloud org

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
User prompts:
- "did you add icons to bundles too?"

Changes:
- Added icon field to all three Azure bundle massdriver.yaml files
- VNet: virtual-networks.svg, VWAN: virtual-wans.svg, FuncApp: function-apps.svg

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Changes:
- Auto-generated variable file updated by mass bundle publish

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
User prompts:
- "cut a 0.2, 0.3, and a 0.4 of wan, vnet, func app"

Changes:
- Version bump for stable release

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
User prompts:
- "bundle icons aren't done as a config, its done as a file in the repo"
- "bump each as a minor and i'll republish"

Changes:
- Removed icon URL from massdriver.yaml, added icon.svg files instead
- azure-virtual-wan 0.2.0 -> 0.3.0
- azure-virtual-network 0.3.0 -> 0.4.0
- azure-function-app 0.4.0 -> 0.5.0

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Changes:
- azure-virtual-wan 0.3.0 -> 0.2.1
- azure-virtual-network 0.4.0 -> 0.3.1
- azure-function-app 0.5.0 -> 0.4.1

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant