7 Commits

Author SHA1 Message Date
Greg
504272e95b fix: correct GitHub secrets for canonical domains in workflows
- Fix smoke-test.yml to use DEV_CANONICAL_DOMAIN, STAGING_CANONICAL_DOMAIN, PROD_CANONICAL_DOMAIN
- Fix promote-to-production.yml domain references
- Fix deployment-status.yml domain references
- Update documentation to reflect correct secret names

The workflows were trying to use DEV_DOMAIN instead of DEV_CANONICAL_DOMAIN
which caused the smoke tests to fail. Canonical domains are the auto-generated
Knative service domains that the tests actually need to check.
2025-07-01 17:41:51 -07:00
Greg
82fc2a6691 feat: Complete PII cleanup and fully automatic pipeline
🧹 PII Cleanup & Security:
- Remove all hardcoded domains (darknex.us, hndrx.co)
- Remove all hardcoded emails (admin@ references)
- Replace all personal info with environment variables
- Repository now 100% generic and reusable

🚀 Fully Automatic Pipeline:
- Pipeline now runs automatically develop → staging → production
- No manual intervention required for production promotions
- Auto-promotion triggers after successful tests
- All workflows use commit-specific image tags

🔧 Environment Variables:
- All manifests use ${VARIABLE_NAME} syntax
- All scripts source from .env file
- GitHub Actions use secrets for sensitive data
- Complete .env.example template provided

📚 Documentation:
- New comprehensive WORKFLOWS.md with pipeline details
- New PIPELINE_QUICK_REFERENCE.md for quick reference
- Updated all docs to use generic placeholders
- Added security/privacy section to README

🔐 Security Enhancements:
- Updated .gitignore for all sensitive files
- Created PII verification script (verify-pii-removal.sh)
- Created cleanup automation script (cleanup-pii.sh)
- Repository verified PII-free and production-ready

BREAKING: Repository now requires .env configuration
- Copy .env.example to .env and configure for your environment
- Set GitHub repository secrets for CI/CD workflows
- All deployments now use environment-specific configuration
2025-07-01 17:30:26 -07:00
Greg
6ffbe5dc31 feat: add manual production promotion and deployment status
- Add manual trigger to promote-to-production workflow (type 'PROMOTE')
- Add deployment status check workflow for monitoring all environments
- Manual promotion allows skipping tests if staging already validated
- Status workflow shows current version and health of all environments
- Provides clear manual action options for production control
2025-07-01 16:21:31 -07:00
Greg
90af21ac8b fix: reorganize pipeline to run smoke tests AFTER deployments
- Change smoke tests to trigger after deployments complete (not on push)
- Auto-promotion now depends on smoke test success (not duplicate testing)
- Promotion to production depends on staging smoke tests
- Eliminates testing previous deployments instead of new ones
- Creates logical flow: deploy → test → promote
2025-07-01 16:11:35 -07:00
Greg
a509e4603e Remove custom domain testing from workflows
- Remove all custom domain SSL testing and health checks
- Use only canonical Knative domains for all testing
- Update all workflows to use domain secrets for health checks
- Remove kubectl dependencies from deployment workflows
- Update index.html to v2.0.2 for testing canonical domain workflow
- Simplify smoke tests to focus on Knative canonical domains only
- Clean up auto-promotion summaries to remove SSL references

All workflows now test only the canonical Knative domains and avoid
custom domain complexity for a cleaner, more reliable pipeline.
2025-07-01 12:42:05 -07:00
Greg
a419767e89 feat: Remove manual approval gates for fully automated deployment pipeline 2025-07-01 10:38:23 -07:00
Greg
09ec016b6a feat: Implement proper branch-based auto-promotion strategy
🚀 **New Branching Strategy:**
- develop → triggers dev deployment → auto-promotes to staging branch
- staging → triggers staging deployment → manual approval → promotes to main branch
- main → triggers production deployment

📝 **Workflow Changes:**
- deploy-dev.yml: Now triggers on develop branch
- deploy-staging.yml: Now triggers on staging branch push
- deploy-prod.yml: Now triggers on main branch push
- auto-promote.yml: Tests dev → merges develop to staging branch
- promote-to-production.yml: Tests staging → requires approval → merges staging to main
- build-image.yml: Now builds on all branches (main, develop, staging)

🎯 **Auto-Promotion Flow:**
1. Push to develop → Deploy to dev → Test → Auto-merge to staging
2. Staging deployment → Test → Manual approval → Auto-merge to main
3. Main deployment → Production live!

This provides proper separation between environments with appropriate gates.
2025-06-30 23:18:14 -07:00