Files

defiQUG 1fb7266469 Add Oracle Aggregator and CCIP Integration

- Introduced Aggregator.sol for Chainlink-compatible oracle functionality, including round-based updates and access control.
- Added OracleWithCCIP.sol to extend Aggregator with CCIP cross-chain messaging capabilities.
- Created .gitmodules to include OpenZeppelin contracts as a submodule.
- Developed a comprehensive deployment guide in NEXT_STEPS_COMPLETE_GUIDE.md for Phase 2 and smart contract deployment.
- Implemented Vite configuration for the orchestration portal, supporting both Vue and React frameworks.
- Added server-side logic for the Multi-Cloud Orchestration Portal, including API endpoints for environment management and monitoring.
- Created scripts for resource import and usage validation across non-US regions.
- Added tests for CCIP error handling and integration to ensure robust functionality.
- Included various new files and directories for the orchestration portal and deployment scripts.

2025-12-12 14:57:48 -08:00

2.0 KiB

Raw Permalink Blame History

Azure Resource Group Naming Convention

Standard Naming Convention

Format: {cloud}-{env}-{region}-rg-{type}-{instance}

Components

cloud: az (Azure)
env: p (prod), d (dev), t (test), s (staging)
region: we (westeurope), ne (northeurope), etc. (see terraform/locals.tf)
rg: Resource Group identifier
type:
- net - Network resources
- comp - Compute resources (AKS, VMs)
- stor - Storage resources
- sec - Security resources (Key Vault)
- mon - Monitoring resources
- tfstate - Terraform state storage
instance: 001, 002, etc.

Examples

az-p-we-rg-comp-001 - Production compute resource group in West Europe
az-p-we-rg-net-001 - Production network resource group in West Europe
az-p-we-rg-stor-001 - Production storage resource group in West Europe
az-p-we-rg-sec-001 - Production security resource group in West Europe
az-p-we-rg-mon-001 - Production monitoring resource group in West Europe

Configuration

Terraform

In terraform/terraform.tfvars, leave resource_group_name empty to use default naming:

resource_group_name = ""  # Uses default: az-p-we-rg-comp-001

Or specify Well-Architected Framework resource groups:

use_well_architected = true
network_resource_group_name  = "az-p-we-rg-net-001"
compute_resource_group_name  = "az-p-we-rg-comp-001"
storage_resource_group_name  = "az-p-we-rg-stor-001"
security_resource_group_name = "az-p-we-rg-sec-001"

Environment Variables

Set in .env:

AZURE_SUBSCRIPTION_ID=fc08d829-4f14-413d-ab27-ce024425db0b

Verification

Run the standardization script:

./scripts/azure/standardize-resource-groups.sh

Migration

If you have existing resource groups that don't follow the convention:

Option 1: Update Terraform to use existing names (not recommended)
Option 2: Migrate resources to properly named resource groups (recommended)
Option 3: Use Well-Architected Framework with proper naming from the start

2.0 KiB Raw Permalink Blame History