How facebook/it-cpe works
Main System Components
a) Core Infrastructure
• Chef Server (implied but not visible in code)
• Client Nodes (macOS, Windows, Linux systems being managed)
b) Cookbook Organization
• CPE Cookbooks (cpe_*)
• Facebook Cookbooks (fb_*)
• Legacy Tools
• Pantri System
Component Relationships
[Chef Server] → [Client Nodes]
• ↓
• [Configuration Management Layer]
• Core Cookbooks
• cpe_init (primary entry point)
• cpe_helpers (utility functions)
• cpe_profiles (system configurations)
• Platform-Specific Cookbooks
• Windows Management (cpe_applocker, cpe_win_telemetry)
• macOS Management (cpe_munki, cpe_profiles)
• Linux Management (cpe_flatpak, cpe_dconf)
• Service Cookbooks
• Browser Management (cpe_chrome)
• Power Management (cpe_powermanagement)
• Remote Management (cpe_remote)
• Support Tools
• Pantri (package management)
• Legacy Tools (adobe_tools, autopkg_tools)
Key Architectural Patterns to Highlight
a) Layered Architecture:
• Infrastructure Layer (Chef Server)
• Configuration Layer (Cookbooks)
• Platform Layer (OS-specific implementations)
• Tools Layer (Support utilities)
b) Modular Design:
• How cpe_init serves as the main entry point
• Cookbook dependencies
• Cross-platform support
Important Details
• Platform support (Windows/macOS/Linux)
• Configuration flow direction
• Critical components (cpe_init, cpe_helpers)
Implementation Notes
• Chef-based configuration management
• Multi-platform support
• Modular cookbook architecture
• Integration with external tools (Munki, AutoPkg)
• Support for legacy systems