1fb7266469
- 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.
2.5 KiB
Configuration Documentation Index
Last Updated: 2025-01-27
Status: Active
This index helps you find the right configuration guide for your needs.
Which Guide Should I Use?
Network Configuration
Use: Network Configuration Guide
When: You need to configure the Besu network, genesis file, or network topology
Covers: Network configuration tool, genesis block, network settings
Azure and Cloudflare Setup
Use: Azure/Cloudflare Environment Setup
When: You need to set up environment variables for Azure and Cloudflare integration
Covers: Azure subscription, Cloudflare zone ID, API tokens, Terraform backend
Contract Deployment Setup
Use: Contract Deployment Environment Setup
When: You need to configure environment variables for deploying contracts
Covers: Private keys, CCIP configuration, WETH deployment, Oracle setup
Azure Naming Conventions
Use: Azure Naming Convention (3 Character) - Recommended
When: You need to name Azure resources using the standard 3-character region codes
Covers: Standard naming pattern with 3-character region codes (e.g., wst, nor)
Alternative: Azure Naming Convention (2-3 Character)
When: You need to use 2-3 character region codes (legacy/alternative)
Covers: Alternative naming pattern with 2-3 character region codes (e.g., we, ne)
Quick Reference
| Guide | Purpose | When to Use |
|---|---|---|
| Network Configuration Guide | Besu network setup | Configuring blockchain network |
| Azure/Cloudflare Environment Setup | Azure/Cloudflare env vars | Setting up infrastructure |
| Contract Deployment Environment Setup | Contract deployment env vars | Deploying smart contracts |
| Azure Naming (3 Char) | Azure naming (standard) | Naming Azure resources (standard) |
| Azure Naming (2-3 Char) | Azure naming (alternative) | Naming Azure resources (alternative) |
Related Documentation
Last Updated: 2025-01-27