# Airtable CICD-Pipeline-Migration Tracker

**Source**: Airtable Base `c60-Migration` (appADaUpn68iuuiwK)
**Table**: CICD-Pipeline-Migration
**Migration Type**: Pipeline Migration (Existing CI/CD → CircleCI)
**Total Services**: 33
**Status**: Services already running, migrating pipelines
**Started**: 2026-03-05

## Important Context

🔄 **This is a PIPELINE MIGRATION, not a greenfield deployment.**

All 33 ACC services are currently:
- ✅ Deployed and running in Kubernetes (redtag namespace)
- ✅ Have values files in tbi-environments
- ✅ Have encrypted secrets in tbi-environments
- ✅ Deploying via an existing (non-CircleCI) pipeline

**Goal**: Migrate CI/CD pipeline from existing system to CircleCI with zero downtime.

## Migration Status

### ✅ Completed (1/33)

1. **tbi-acc-hotel-mapping-service** - dev
   - Status: Complete
   - Environments: dev
   - Namespace: redtag
   - Documentation: `docs/SETUP-COMPLETE-tbi-acc-hotel-mapping-service.md`

### 🔄 In Progress (0/33)

### ⏳ Pending (32/33)

#### High Priority - Multi-Environment Services

2. **tbi-acc-hotel-service** - 6 environments
   - Environments: dev, prod, qa, tbi-acc-gx, tbi-acc-his, uat
   - Namespace: TBD
   - Notes: Core hotel service

3. **tbi-acc-package-service** - 6 environments
   - Environments: dev, prod, qa, tbi-acc-gx, tbi-acc-his, uat
   - Namespace: TBD
   - Notes: Core package service

4. **tbi-acc-hotel-service-connector** - 6 environments
   - Environments: dev, prod, qa, tbi-acc-gx, tbi-acc-his, uat
   - Namespace: TBD
   - Notes: Hotel service connector

5. **tbi-acc-travelbrandsagent** - 6 environments
   - Environments: dev, prod, qa, tbi-acc-gx, tbi-acc-his, uat
   - Namespace: TBD
   - Notes: Travelbrands agent

6. **tbi-acc-profile-service** - 6 environments
   - Environments: dev, prod, qa, tbi-acc-his, tbi-retail, uat
   - Namespace: TBD
   - Notes: Profile service

#### Medium Priority - 3-4 Environment Services

7. **tbi-acc-booking-service** - 4 environments
   - Environments: dev, prod, qa, uat
   - Namespace: TBD

8. **tbi-acc-quotes-service** - 4 environments
   - Environments: dev, prod, qa, uat
   - Namespace: TBD

9. **tbi-acc-notification-service** - 4 environments
   - Environments: dev, prod, qa, uat
   - Namespace: TBD

10. **tbi-acc-mybooking-service** - 3 environments
    - Environments: dev, prod, uat
    - Namespace: TBD

11. **tbi-acc-mybooking-frontend** - 3 environments
    - Environments: dev, prod, uat
    - Namespace: TBD

12. **tbi-acc-mybff** - 3 environments
    - Environments: dev, prod, uat
    - Namespace: TBD

13. **tbi-acc-ceetiz-connector** - 3 environments
    - Environments: dev, prod, uat
    - Namespace: TBD

14. **tbi-acc-exotiktours-connector** - 3 environments
    - Environments: dev, prod, uat
    - Namespace: TBD

15. **tbi-acc-sabreapi** - 3 environments
    - Environments: dev, prod, uat
    - Namespace: TBD

16. **tbi-acc-profile-sync-service** - 5 environments
    - Environments: dev, prod, qa, tbi-retail, uat
    - Namespace: TBD

#### Lower Priority - Dev/QA Only Services

17. **tbi-acc-travelbrands** - 2 environments
    - Environments: dev, prod
    - Namespace: TBD

18. **tbi-acc-package-cron** - 2 environments
    - Environments: dev, prod
    - Namespace: TBD

19. **tbi-acc-cron-service** - 2 environments
    - Environments: dev, uat
    - Namespace: TBD

20. **tbi-acc-gimmonix-automation** - 1 environment
    - Environments: dev
    - Namespace: TBD

21. **tbi-acc-gimmonix-automation-cron** - 1 environment
    - Environments: dev
    - Namespace: TBD

22. **tbi-acc-gimmonix-automation-cron-2** - 1 environment
    - Environments: dev
    - Namespace: TBD

23. **tbi-acc-gimmonix-automation-cron-3** - 1 environment
    - Environments: dev
    - Namespace: TBD

24. **tbi-acc-gimmonix-automation-cron-4** - 1 environment
    - Environments: dev
    - Namespace: TBD

25. **tbi-acc-gimmonix-automation-cron-5** - 1 environment
    - Environments: dev
    - Namespace: TBD

26. **tbi-acc-gimmonix-automation-cron-6** - 1 environment
    - Environments: dev
    - Namespace: TBD

27. **tbi-acc-clone-mybff** - 1 environment
    - Environments: dev
    - Namespace: TBD

28. **tbi-acc-corporate-booking** - 1 environment
    - Environments: dev
    - Namespace: TBD

29. **tbi-acc-booking-notification** - 1 environment
    - Environments: dev
    - Namespace: TBD

30. **tbi-acc-cronjobs** - 1 environment
    - Environments: qa
    - Namespace: TBD

#### Legacy/Old Services

31. **tbi-acc-hotel-service-old** - 1 environment
    - Environments: prod
    - Namespace: TBD
    - Notes: Legacy service - verify if still needed

32. **tbi-acc-package-service-old** - 2 environments
    - Environments: prod, tbi-charts/prod
    - Namespace: TBD
    - Notes: Legacy service - verify if still needed

33. **tbi-acc-hotel-service-connector-old** - 1 environment
    - Environments: prod
    - Namespace: TBD
    - Notes: Legacy service - verify if still needed

## Migration Approach

### What We're Migrating

**NOT migrating:**
- ❌ Services (already running)
- ❌ Values files (already exist)
- ❌ Secrets (already exist)
- ❌ Kubernetes deployments (already deployed)

**ARE migrating:**
- ✅ CI/CD pipeline from existing system → CircleCI
- ✅ Dockerfiles → centralized in tbi-devops-environments
- ✅ Helm charts → centralized in tbi-devops-environments
- ✅ Deployment automation → CircleCI workflows

### Phase 1: Core Services (Priority 1)
- Multi-environment services that are critical to operations
- Services 2-6 (5 services)

### Phase 2: Standard Services (Priority 2)
- 3-4 environment services
- Services 7-16 (10 services)

### Phase 3: Dev/QA Services (Priority 3)
- Development and testing services
- Services 17-30 (14 services)

### Phase 4: Legacy Services (Priority 4)
- Verify if still needed before migration
- Services 31-33 (3 services)

## Next Steps

1. Start with Phase 1 core services
2. For each service:
   - Determine namespace and technology stack
   - Check if service repository exists
   - Create CI/CD configuration in tbi-devops-environments
   - Create values and secrets in tbi-environments
   - Test deployment to dev environment first
   - Document the setup
   - Update Airtable with completion status

## Notes

- All services follow the `tbi-acc-*` naming pattern (ACC = Accommodation)
- Most services have multiple environments (dev, qa, uat, prod)
- Some services have special environments (tbi-acc-gx, tbi-acc-his, tbi-retail)
- Gimmonix automation has 6 separate cron services
- Legacy services marked with `-old` suffix need verification

## Reference

- Template Service: `tbi-acc-hotel-mapping-service`
- Patterns Document: `.kiro/steering/circleci-pipeline-patterns.md`
- Agent: `.kiro/agents/circleci-pipeline-deployment-agent.json`