How facets-cloud/inca works
Main Components
a) Catalog Layer
• Should include the Intent Types Registry (based on the intent_types directory)
• Versioning structure (v1alpha1 format seen in the MySQL example)
b) Schema Definition Layer
• JSON schema system (evident from schema.json files)
• Validation and type definition components
• Relationship with intent types
c) Implementation Layer
• How different infrastructure providers can be plugged in
• Demonstrate the abstraction between intent and actual implementation
• Sample implementations (like MySQL shown in the intent_types)
Relationships to Highlight
[Catalog Definition] → [Intent Type Registry] → [Schema Validation] → [Implementation Layer] → [Cloud Providers]
Specific Elements
• Rectangle: Intent Type Registry
• Hexagon: Schema Validators
Hierarchical Structure
Top to Bottom:
Important Details to Capture
• Version control system for intent types (v1alpha1 structure)
• Schema validation flow
• Implementation flexibility
• Provider-agnostic nature
• Utility functions and tools
Specific Project Elements
• Intent type registration system
• MySQL as a sample intent type
• Schema validation flow
• Index management system (from utils/update_index.py)