Files
smom-dbis-138/terraform/backend.tf
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

30 lines
1.3 KiB
HCL

# Terraform Backend Configuration
# Configured to use naming convention: {cloud}-{env}-{region}-{resource}-{instance}
# Storage account will be created by Terraform if it doesn't exist
terraform {
backend "azurerm" {
# Using environment variables (recommended for security)
# Set these in .env or export before running terraform init:
# ARM_STORAGE_ACCOUNT_NAME - Storage account name (e.g., azpwetfstate001)
# ARM_CONTAINER_NAME - Container name (typically "tfstate")
# ARM_RESOURCE_GROUP_NAME - Resource group containing storage account
# ARM_ACCESS_KEY - Storage account access key (or use Managed Identity)
#
# Alternative: Uncomment and configure below (less secure)
# resource_group_name = "az-p-we-rg-tfstate-001"
# storage_account_name = "azpwetfstate001" # Must be globally unique, lowercase, alphanumeric
# container_name = "tfstate"
# key = "defi-oracle-mainnet.terraform.tfstate"
# Note: If using Well-Architected Framework, storage account should be in storage resource group
# For legacy deployment, it can be in the compute resource group
}
}
# Note: Storage account name must be:
# - 3-24 characters
# - Lowercase letters and numbers only
# - Globally unique across all Azure subscriptions