How oracle-devrel/cd3-automation-toolkit works
Main Components Overview
The system should be represented as a multi-layered architecture with these primary components:
a) Input Layer:
• Excel Templates (represented as document symbols)
• Existing OCI Infrastructure (for export functionality)
b) Core Processing Layer:
• CD3 Automation Engine
• Validation Components
• Parser Components
c) Output Layer:
• Terraform Modules
• Resource Manager Configurations
• Jenkins Pipeline Integrations
Key Relationships
• Bi-directional flow between OCI Infrastructure and CD3 (for both creation and export)
• Data flow from Excel templates through the processing layer to Terraform output
• Integration points with CI/CD systems
Detailed Component Breakdown
Service Modules (shown as grouped components):
Identity & Security:
• IAM
• Tagging
• Quotas
• Network Firewall
• KMS
Infrastructure:
• Network
• Compute
• Storage
• Database
• Load Balancers
• DNS Management
Container & Orchestration:
• OKE (Oracle Kubernetes Engine)
• SDDC
Management:
• Resource Manager
• Monitoring
• Logging
• Cloud Guard
• Budgets
Integration Points
External system connections:
• Jenkins Pipeline integration
• OCI Resource Manager
• DevOps Git service
• OPA (Open Policy Agent) integration
Data Flow Patterns
Three main workflows:
Architectural Layers
Top: User Interface/Input Layer
Middle: Processing/Automation Layer
Bottom: Infrastructure/Output Layer
Implementation Notes
• Use standard architectural symbols for clarity
• Version control indicators
• Security boundaries clearly
• Scalability points
• Compliance checkpoints
• Automation capabilities
• Bi-directional functionality
• Security integration
• Compliance support
• DevOps enablement