pangea 0.0.45 → 0.0.46

data/CONTRIBUTING.md

@@ -1,143 +0,0 @@
-# Contributing to Pangea
-
-First off, thank you for considering contributing to Pangea! It's people like you that make Pangea such a great tool.
-
-## Code of Conduct
-
-This project and everyone participating in it is governed by the [Pangea Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to the project maintainers.
-
-## How Can I Contribute?
-
-### Reporting Bugs
-
-Before creating bug reports, please check existing issues as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible:
-
-* **Use a clear and descriptive title**
-* **Describe the exact steps which reproduce the problem**
-* **Provide specific examples to demonstrate the steps**
-* **Describe the behavior you observed after following the steps**
-* **Explain which behavior you expected to see instead and why**
-* **Include details about your configuration and environment**
-
-### Suggesting Enhancements
-
-Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion, please include:
-
-* **Use a clear and descriptive title**
-* **Provide a step-by-step description of the suggested enhancement**
-* **Provide specific examples to demonstrate the steps**
-* **Describe the current behavior and explain which behavior you expected to see instead**
-* **Explain why this enhancement would be useful**
-
-### Pull Requests
-
-* Fill in the required template
-* Do not include issue numbers in the PR title
-* Follow the Ruby style guide
-* Include thoughtfully-worded, well-structured tests
-* Document new code with YARD comments
-* End all files with a newline
-
-## Development Setup
-
-1. Fork and clone the repo
-2. Install dependencies:
-   ```bash
-   bundle install
-   ```
-3. Make sure tests pass:
-   ```bash
-   bundle exec rake spec
-   ```
-4. Create a branch:
-   ```bash
-   git checkout -b my-feature-branch
-   ```
-5. Make your changes and add tests
-6. Run the test suite:
-   ```bash
-   bundle exec rake spec
-   ```
-7. Run type checking:
-   ```bash
-   bundle exec steep check
-   ```
-8. Run linting:
-   ```bash
-   bundle exec rubocop
-   ```
-
-## Testing
-
-* Write RSpec tests for any new functionality
-* Ensure all tests pass before submitting PR
-* Aim for high test coverage (80%+)
-* Include both unit and integration tests where appropriate
-
-### Running Tests
-
-```bash
-# Run all tests
-bundle exec rake spec
-
-# Run specific test file
-bundle exec rspec spec/path/to/spec.rb
-
-# Run with coverage
-bundle exec rake coverage
-```
-
-## Type Checking
-
-Pangea uses RBS for type definitions and Steep for type checking:
-
-```bash
-# Check types
-bundle exec steep check
-
-# Generate RBS signatures
-bundle exec rbs prototype rb lib/pangea/new_file.rb > sig/pangea/new_file.rbs
-```
-
-## Style Guidelines
-
-### Ruby Style
-
-* Follow the community Ruby style guide
-* Use RuboCop for style checking
-* Prefer functional style where appropriate
-* Use descriptive variable names
-* Keep methods small and focused
-
-### Git Commit Messages
-
-* Use the present tense ("Add feature" not "Added feature")
-* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
-* Limit the first line to 72 characters or less
-* Reference issues and pull requests liberally after the first line
-
-### Documentation
-
-* Use YARD for API documentation
-* Update README.md with details of changes to the interface
-* Create or update example files in the `examples/` directory
-* Document complex logic with inline comments
-
-## Project Structure
-
-```
-pangea/
-├── lib/           # Main library code
-├── spec/          # RSpec tests
-├── examples/      # Example templates
-├── sig/           # RBS type signatures
-└── docs/          # Additional documentation
-```
-
-## Release Process
-
-Releases are automated via GitHub Actions when a new tag is pushed. Only maintainers can create releases.
-
-## Questions?
-
-Feel free to open an issue with your question or reach out to the maintainers directly.

data/EXAMPLES.md

@@ -1,376 +0,0 @@
-# Pangea Examples: Infrastructure as Code Patterns
-
-This directory contains comprehensive examples demonstrating Pangea's power for infrastructure management. From simple single-resource deployments to complex enterprise architectures, these examples showcase how Pangea's template-level isolation, type safety, and Ruby DSL enable scalable, maintainable infrastructure.
-
-## 🎯 Quick Start Examples
-
-### [simple.rb](examples/simple.rb)
-**The simplest possible Pangea template**
-- Single S3 bucket with basic configuration
-- Perfect for understanding template syntax
-- Demonstrates basic resource creation
-
-```bash
-pangea apply examples/simple.rb
-```
-
-### [basic-web-app/](examples/basic-web-app/) ⭐ **New**
-**Complete web application in one template**
-- VPC with public/private subnets
-- EC2 instance with security groups
-- Application load balancer
-- Shows cross-resource references
-- Includes `pangea.yaml` for multi-environment management
-
-```bash
-cd examples/basic-web-app
-pangea apply infrastructure.rb
-```
-
-### [multi-tier-architecture/](examples/multi-tier-architecture/) ⭐ **New**
-**Three-tier application with database**
-- Web tier with load balancer
-- Application tier with auto-scaling
-- Database tier with RDS
-- Demonstrates template isolation benefits
-- Three separate templates with cross-template communication
-
-```bash
-cd examples/multi-tier-architecture
-pangea apply infrastructure.rb --template networking
-pangea apply infrastructure.rb --template database
-pangea apply infrastructure.rb --template application
-```
-
-## 🏢 Enterprise Examples
-
-### [scalable_infrastructure.rb](examples/scalable_infrastructure.rb)
-**Multi-template scalable architecture**
-- Foundation template for networking
-- Application template for compute
-- Database template for persistent storage
-- Shows incremental deployment patterns
-
-### [microservices-platform/](examples/microservices-platform/) ⭐ **New**
-**Complete microservices platform**
-- Container orchestration with ECS
-- Service discovery and mesh
-- API Gateway integration
-- Event-driven architecture patterns
-- Includes complete Pangea repository structure
-
-```bash
-cd examples/microservices-platform
-pangea apply infrastructure.rb --template platform
-pangea apply infrastructure.rb --template services
-```
-
-### [advanced_global_infrastructure.rb](examples/advanced_global_infrastructure.rb)
-**Global multi-region deployment**
-- Cross-region VPC peering
-- Global load balancing
-- Disaster recovery setup
-- Advanced networking patterns
-
-### [comprehensive_database_platform.rb](examples/comprehensive_database_platform.rb)
-**Database-as-a-Service platform**
-- Multiple database engines
-- Backup and monitoring
-- Performance optimization
-- High availability setup
-
-## 🚀 Specialized Examples
-
-### [advanced_ml_healthcare_infrastructure.rb](examples/advanced_ml_healthcare_infrastructure.rb)
-**Healthcare ML platform**
-- FHIR datastores for clinical data
-- SageMaker training pipelines
-- Compliance-ready security
-- HIPAA-compliant architecture
-
-### [ml-platform/](examples/ml-platform/) ⭐ **New**
-**Production ML platform**
-- Data lake infrastructure
-- Feature store implementation
-- Model training and serving
-- MLOps pipeline automation
-
-### [gaming_infrastructure.rb](examples/gaming_infrastructure.rb)
-**Game backend infrastructure**
-- GameLift fleet management
-- Real-time multiplayer support
-- Player data storage
-- Scalable game sessions
-
-### [robotics_and_specialized_services.rb](examples/robotics_and_specialized_services.rb)
-**IoT and robotics platform**
-- IoT device management
-- RoboMaker integration
-- Edge computing setup
-- Telemetry processing
-
-## 🔧 Integration Examples
-
-### [api_gateway_complete.rb](examples/api_gateway_complete.rb)
-**Complete API management**
-- REST and WebSocket APIs
-- Authentication integration
-- Rate limiting and caching
-- Multi-stage deployment
-
-### [cicd-pipeline/](examples/cicd-pipeline/) ⭐ **New**
-**CI/CD pipeline infrastructure**
-- CodeBuild projects
-- CodePipeline setup
-- Artifact management
-- Multi-environment promotion
-
-### [messaging_example.rb](examples/messaging_example.rb)
-**Event-driven messaging**
-- SQS/SNS integration
-- Dead letter queues
-- Event processing patterns
-- Scalable message handling
-
-### [data-processing/](examples/data-processing/) ⭐ **New**
-**Big data processing pipeline**
-- Kinesis streaming
-- EMR clusters for batch processing
-- Glue ETL jobs
-- Data lake storage patterns
-
-## 🌍 Multi-Environment Examples
-
-### [multi-environment/](examples/multi-environment/) ⭐ **New**
-**Environment-aware templates**
-- Development/staging/production configs
-- Environment-specific resource sizing
-- Namespace-driven customization
-- Promotion workflow patterns
-
-### [security-focused/](examples/security-focused/) ⭐ **New**
-**Security-first architecture**
-- Zero-trust networking
-- VPC Flow Logs
-- GuardDuty integration
-- Compliance automation
-
-### [global-multi-region/](examples/global-multi-region/) ⭐ **New**
-**Global application deployment**
-- Multi-region active-active
-- Cross-region data replication
-- Global load balancing
-- Disaster recovery automation
-
-## 📊 Monitoring Examples
-
-### [cloudwatch_monitoring_example.rb](examples/cloudwatch_monitoring_example.rb)
-**Comprehensive monitoring setup**
-- Custom metrics and alarms
-- Dashboard creation
-- Log aggregation
-- Automated alerting
-
-### [disaster-recovery/](examples/disaster-recovery/) ⭐ **New**
-**Enterprise disaster recovery**
-- Cross-region backup automation
-- RTO/RPO optimization
-- Failover procedures
-- Business continuity planning
-
-## 🔒 Advanced Patterns
-
-### [type_safe_infrastructure.rb](examples/type_safe_infrastructure.rb)
-**Type safety demonstration**
-- Resource function validation
-- Compile-time error prevention
-- IDE integration benefits
-- Best practices for type safety
-
-### [resource_composition_patterns.rb](examples/resource_composition_patterns.rb)
-**Complex resource relationships**
-- Advanced referencing patterns
-- Conditional resource creation
-- Dynamic configuration
-- Reusable patterns
-
-## 📋 Example Categories
-
-### By Complexity Level
-
-**🟢 Beginner (1-2 templates)**
-- [simple.rb](examples/simple.rb)
-- [basic-web-app/](examples/basic-web-app/)
-- [multi-tier-architecture/](examples/multi-tier-architecture/)
-
-**🟡 Intermediate (3-5 templates)**
-- [scalable_infrastructure.rb](examples/scalable_infrastructure.rb)
-- [microservices-platform/](examples/microservices-platform/)
-- [cicd-pipeline/](examples/cicd-pipeline/)
-- [multi-environment/](examples/multi-environment/)
-
-**🔴 Advanced (5+ templates)**
-- [advanced_global_infrastructure.rb](examples/advanced_global_infrastructure.rb)
-- [advanced_ml_healthcare_infrastructure.rb](examples/advanced_ml_healthcare_infrastructure.rb)
-- [ml-platform/](examples/ml-platform/)
-- [global-multi-region/](examples/global-multi-region/)
-- [disaster-recovery/](examples/disaster-recovery/)
-
-### By Use Case
-
-**🌐 Web Applications**
-- [basic-web-app/](examples/basic-web-app/) - Simple web server
-- [multi-tier-architecture/](examples/multi-tier-architecture/) - Full-stack application
-- [scalable_infrastructure.rb](examples/scalable_infrastructure.rb) - Scalable web platform
-
-**📱 Microservices**
-- [microservices-platform/](examples/microservices-platform/) - Container platform
-- [messaging_example.rb](examples/messaging_example.rb) - Event-driven services
-- [api_gateway_complete.rb](examples/api_gateway_complete.rb) - API management
-
-**🤖 Machine Learning**
-- [ml-platform/](examples/ml-platform/) - Production ML platform  
-- [advanced_ml_healthcare_infrastructure.rb](examples/advanced_ml_healthcare_infrastructure.rb) - Healthcare ML
-
-**🏗️ Platform Engineering**
-- [cicd-pipeline/](examples/cicd-pipeline/) - Build/deploy automation
-- [security-focused/](examples/security-focused/) - Security platform
-- [data-processing/](examples/data-processing/) - Big data platform
-
-**🌍 Enterprise Architecture**
-- [global-multi-region/](examples/global-multi-region/) - Global deployment
-- [disaster-recovery/](examples/disaster-recovery/) - Business continuity
-- [multi-environment/](examples/multi-environment/) - Environment management
-
-## 🚀 Running the Examples
-
-### Basic Usage
-
-```bash
-# Simple examples
-pangea apply examples/simple.rb
-cd examples/basic-web-app && pangea apply infrastructure.rb
-
-# Multi-template examples (deploy in order)
-pangea apply examples/scalable_infrastructure.rb --template foundation
-pangea apply examples/scalable_infrastructure.rb --template application
-pangea apply examples/scalable_infrastructure.rb --template database
-
-# Environment-specific deployment
-pangea apply examples/multi-environment-deployment.rb --namespace development
-pangea apply examples/multi-environment-deployment.rb --namespace production
-```
-
-### Configuration
-
-Most examples require a `pangea.yaml` configuration file. See [pangea.yaml.example](../pangea.yaml.example) in the root directory for a comprehensive configuration template.
-
-### Prerequisites
-
-- Ruby 3.1+ 
-- Terraform 1.5+ or OpenTofu 1.6+
-- AWS CLI configured with appropriate permissions
-- Pangea installed: `gem install pangea`
-
-## 🔧 Customizing Examples
-
-### Environment Variables
-
-Many examples support customization via environment variables:
-
-```bash
-# Customize instance types
-export INSTANCE_TYPE=t3.large
-pangea apply examples/basic-web-app.rb
-
-# Enable additional features
-export ENABLE_MONITORING=true
-export ENABLE_BACKUP=true
-pangea apply examples/multi-tier-architecture.rb
-
-# Multi-region deployment
-export PRIMARY_REGION=us-east-1
-export SECONDARY_REGION=us-west-2
-pangea apply examples/global-multi-region.rb
-```
-
-### Template Modification
-
-Examples are designed to be educational and customizable:
-
-1. **Copy** the example to your project
-2. **Modify** resource configurations for your needs
-3. **Add** additional templates as required
-4. **Deploy** with confidence using template isolation
-
-## 📚 Learning Path
-
-### 1. Start with Basics
-- Run [simple.rb](examples/simple.rb) to understand template syntax
-- Explore [basic-web-app.rb](examples/basic-web-app.rb) for resource relationships
-- Try [multi-tier-architecture.rb](examples/multi-tier-architecture.rb) for architecture patterns
-
-### 2. Understand Template Isolation
-- Deploy [scalable_infrastructure.rb](examples/scalable_infrastructure.rb) template by template
-- See how [microservices-platform.rb](examples/microservices-platform.rb) isolates different concerns
-- Practice with [multi-environment-deployment.rb](examples/multi-environment-deployment.rb)
-
-### 3. Explore Advanced Patterns
-- Study [ml-platform.rb](examples/ml-platform.rb) for complex architectures
-- Examine [global-multi-region.rb](examples/global-multi-region.rb) for enterprise patterns
-- Learn from [disaster-recovery-architecture.rb](examples/disaster-recovery-architecture.rb)
-
-## 🤝 Contributing Examples
-
-Have an interesting Pangea pattern? Add it to the examples:
-
-1. Create a new `.rb` file in the `examples/` directory
-2. Follow the existing naming pattern: `kebab-case.rb`
-3. Include comprehensive comments explaining the pattern
-4. Add error handling and validation
-5. Update this EXAMPLES.md with your example
-
-### Example Template
-
-```ruby
-# Copyright 2025 The Pangea Authors
-# Licensed under the Apache License, Version 2.0
-
-# Example: [Brief Description]
-# This example demonstrates [key concepts]
-
-template :example_template do
-  provider :aws do
-    region "us-east-1"
-  end
-  
-  # Resource definitions with comments
-  # explaining the pattern
-end
-```
-
-## 🔍 Finding Examples
-
-### By Feature
-- **Template Isolation**: [scalable_infrastructure.rb](examples/scalable_infrastructure.rb)
-- **Type Safety**: [type_safe_infrastructure.rb](examples/type_safe_infrastructure.rb)
-- **Multi-Environment**: [multi-environment-deployment.rb](examples/multi-environment-deployment.rb)
-- **Cross-Region**: [global-multi-region.rb](examples/global-multi-region.rb)
-
-### By AWS Service
-- **EC2/VPC**: [basic-web-app.rb](examples/basic-web-app.rb)
-- **ECS/Fargate**: [microservices-platform.rb](examples/microservices-platform.rb)
-- **RDS**: [multi-tier-architecture.rb](examples/multi-tier-architecture.rb)
-- **SageMaker**: [ml-platform.rb](examples/ml-platform.rb)
-- **API Gateway**: [api_gateway_complete.rb](examples/api_gateway_complete.rb)
-
-## 📖 Additional Resources
-
-- **[Getting Started Guide](guides/getting-started.md)** - First steps with Pangea
-- **[Template Isolation Guide](guides/template-isolation.md)** - Understanding Pangea's core concept
-- **[Advanced Patterns Guide](guides/advanced-patterns.md)** - Enterprise architecture patterns
-- **[API Documentation](README.md)** - Complete reference
-
----
-
-*These examples showcase the power of Pangea's template-level isolation, type safety, and automation-first design. Start simple, then explore the advanced patterns that make Pangea perfect for enterprise infrastructure management.*

data/OPEN_SOURCE_READINESS.md

@@ -1,170 +0,0 @@
-# Open Source Readiness Assessment for Pangea
-
-## Executive Summary
-
-Pangea is a scalable, automation-first infrastructure management tool built on Ruby DSL that compiles to Terraform JSON. While the project has a solid technical foundation and clear value proposition, it requires several critical improvements before being ready for open source release.
-
-## Current Status
-
-### ✅ Strengths
-
-1. **Apache 2.0 License** - Appropriate open source license already in place
-2. **Clear Technical Architecture** - Well-documented internal architecture in CLAUDE.md
-3. **Comprehensive Examples** - 15+ example files demonstrating various use cases
-4. **Test Infrastructure** - RSpec test suite with unit and integration tests
-5. **Type Safety** - RBS type definitions and Steep type checking support
-6. **Clean Codebase** - No hardcoded secrets or credentials found (only test fixtures with example account IDs)
-7. **Modular Design** - Well-organized code structure with clear separation of concerns
-
-### ❌ Critical Issues
-
-1. **License Mismatch** - gemspec says MIT while LICENSE file is Apache 2.0
-2. **No Copyright Headers** - Source files lack copyright/license headers
-3. **Missing CI/CD** - No GitHub Actions, Travis CI, or other automated testing
-4. **No Community Files** - Missing CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md
-5. **Incomplete Documentation** - README is minimal, missing installation prerequisites, detailed usage
-6. **No Version Constraints** - Dependencies lack version specifications in gemspec
-7. **Author Information** - gemspec only has email, needs proper author name
-8. **Inaccurate Description** - gemspec description doesn't match project purpose
-
-### ⚠️  Minor Issues
-
-1. **No CHANGELOG** - No record of version changes
-2. **No Issue Templates** - Missing GitHub issue/PR templates
-3. **No Badges** - README lacks status badges (CI, coverage, version)
-4. **Limited API Documentation** - YARD docs not generated/published
-
-## Required Actions for Open Source Release
-
-### 1. Legal & Licensing (Priority: Critical)
-
-- [ ] Fix gemspec license field to match Apache 2.0
-- [ ] Add copyright headers to all Ruby source files:
-  ```ruby
-  # Copyright [YEAR] [COPYRIGHT HOLDER]
-  # 
-  # Licensed under the Apache License, Version 2.0 (the "License");
-  # you may not use this file except in compliance with the License.
-  # You may obtain a copy of the License at
-  # 
-  #     http://www.apache.org/licenses/LICENSE-2.0
-  ```
-- [ ] Update copyright line in LICENSE file with actual copyright holder
-- [ ] Add NOTICE file if required by dependencies
-
-### 2. Documentation (Priority: High)
-
-- [ ] Expand README.md with:
-  - Detailed installation instructions
-  - Prerequisites (Ruby version, Terraform/OpenTofu)
-  - Quick start guide
-  - Feature overview with benefits
-  - Comparison with alternatives (Terragrunt, etc.)
-  - Badges (CI status, version, license)
-  
-- [ ] Create CONTRIBUTING.md covering:
-  - Development setup
-  - Testing guidelines
-  - Pull request process
-  - Code style guide
-  - Type checking requirements
-  
-- [ ] Add API documentation:
-  - Generate and publish YARD docs
-  - Document public APIs thoroughly
-  - Add inline documentation for complex methods
-
-### 3. Community & Governance (Priority: High)
-
-- [ ] Create CODE_OF_CONDUCT.md (use Contributor Covenant)
-- [ ] Add SECURITY.md with vulnerability reporting process
-- [ ] Create .github/ISSUE_TEMPLATE/ with:
-  - Bug report template
-  - Feature request template
-  - Question template
-- [ ] Add .github/PULL_REQUEST_TEMPLATE.md
-- [ ] Define CODEOWNERS file
-- [ ] Create GOVERNANCE.md outlining project decision-making
-
-### 4. CI/CD & Quality (Priority: Critical)
-
-- [ ] Set up GitHub Actions with:
-  ```yaml
-  name: CI
-  on: [push, pull_request]
-  jobs:
-    test:
-      runs-on: ubuntu-latest
-      strategy:
-        matrix:
-          ruby: ['3.3', '3.2', '3.1']
-    lint:
-      # RuboCop checks
-    typecheck:
-      # Steep checks
-  ```
-- [ ] Add code coverage reporting (SimpleCov + Codecov)
-- [ ] Set up automatic gem releases on tags
-- [ ] Configure Dependabot for dependency updates
-
-### 5. Project Metadata (Priority: High)
-
-- [ ] Update gemspec:
-  ```ruby
-  spec.authors = ["Your Name"]
-  spec.email = ["maintainer@example.com"]
-  spec.summary = "Scalable infrastructure management with Ruby DSL and Terraform"
-  spec.description = "Pangea provides template-level state isolation and Ruby DSL compilation for Terraform/OpenTofu infrastructure management"
-  ```
-- [ ] Add version constraints to dependencies:
-  ```ruby
-  spec.add_dependency "terraform-synthesizer", "~> 2.0"
-  spec.add_dependency "dry-types", "~> 1.7"
-  # etc...
-  ```
-- [ ] Create CHANGELOG.md with initial release notes
-
-### 6. Release Preparation (Priority: Medium)
-
-- [ ] Tag initial version (suggest 0.1.0 for pre-1.0)
-- [ ] Create GitHub releases with detailed notes
-- [ ] Prepare announcement blog post/documentation
-- [ ] Set up project website or GitHub Pages
-- [ ] Register gem name on RubyGems.org
-
-### 7. Additional Recommendations
-
-- [ ] Add Docker support for easier testing/development
-- [ ] Create getting started video/screencast
-- [ ] Set up discussion forum (GitHub Discussions)
-- [ ] Add performance benchmarks
-- [ ] Create migration guide from Terraform/Terragrunt
-- [ ] Add integration tests for major cloud providers
-
-## Timeline Estimate
-
-- **Week 1-2**: Legal/licensing fixes, basic documentation
-- **Week 2-3**: CI/CD setup, community files
-- **Week 3-4**: Enhanced documentation, examples
-- **Week 4**: Final review, initial release
-
-## Risk Assessment
-
-**Low Risk**:
-- Technical architecture is sound
-- No security vulnerabilities found
-- Clean separation from proprietary code
-
-**Medium Risk**:
-- Dependency on terraform-synthesizer library (ensure it's also open source compatible)
-- Limited test coverage for some components
-
-**Mitigation**:
-- Increase test coverage to 80%+ before release
-- Verify all dependency licenses are compatible
-
-## Conclusion
-
-Pangea has strong technical foundations but needs significant documentation and community infrastructure work before open source release. The estimated 4-week timeline would result in a professional, welcoming open source project ready for community contributions.
-
-The most critical items are fixing the license mismatch, setting up CI/CD, and creating comprehensive documentation. These should be prioritized in the first two weeks of preparation.