DataOps & Version Control
Establish CI/CD for data pipelines, manage multi-environment deployments, or set up version control best practices.
Prompt Template
Help me establish [DATAOPS_PRACTICE] for [PROJECT/FOLDER]:1. Current state: - Environment setup: [DEV/STAGING/PROD configuration] - Deployment process: [CURRENT_APPROACH] - Version control: [CURRENT_PRACTICES]2. Goals: - [SPECIFIC_OBJECTIVE_1] - [SPECIFIC_OBJECTIVE_2]3. Requirements: - Must maintain: [CRITICAL_CONSTRAINTS] - Team size: [NUMBER] developers - Deployment frequency: [FREQUENCY]Please provide:- Best practice recommendations- Step-by-step implementation plan- Risk mitigation strategies- Testing and validation approach
Industry Example
Help me establish environment promotion strategy for patient-analytics/clinical-outcomes folder:1. Current state: - Environment setup: We have DEV, UAT, and PROD but pipelines are manually copied between them - Deployment process: Copy-paste pipeline files and manually update table names - Version control: Pipelines are in Git but no branching strategy or approval process2. Goals: - Automate promotion from DEV → UAT → PROD with approval gates - Use pipeline variables to handle environment-specific configurations - Implement rollback capability if production deployment causes issues - Ensure HIPAA compliance throughout deployment process3. Requirements: - Must maintain: Zero patient data exposure during deployments, audit trail of all changes - Team size: 5 developers working on different clinical modules - Deployment frequency: Weekly releases to PROD, daily to DEV