배포시 챙겨야할것
secret 정상적용 되어있는지 확인
elastic container registry
crm-api
mildang-backend-crm-api-develop
mildang-backend-crm-api-staging
mildang-backend-crm-api-production
crm-worker
mildang-backend-crm-worker-develop
mildang-backend-crm-worker-staging
mildang-backend-crm-worker-production
hup-api
mildang-backend-hub-api-develop
mildang-backend-hub-api-staging
mildang-backend-hub-api-production
k8s kustomize
crm-api
develop
deployment-patch-develop.yml
env
secretKeyRef: env-dev
key: CrmApi
container image
mildang-backend-crm-api-develop
service-patch-develop.yml
labels, selector 체크
stage
deployment-patch-stage.yml
env
secretKeyRef: env-stage
key: CrmApi
container image
mildang-backend-crm-api-staging
service-patch-stage.yml
labels, selector 체크
prod
deployment-patch-prod.yml
env
secretKeyRef: env-prod
key: CrmApi
container image
mildang-backend-crm-api-production
service-patch-prod.yml
labels, selector 체크
crm-worker
develop
deployment-patch-develop.yml
env
secretKeyRef: env-dev
key: CrmWorker
image
mildang-backend-crm-worker-develop
stage
deployment-patch-stage.yml
env
secretKeyRef: env-stage
key: CrmWorker
image
mildang-backend-crm-worker-stage
prod
deployment-patch-prod.yml
env
secreyKeyRef: env-prod
key: CrmWorker
image
mildang-backend-crm-worker-production
hub-api
develop
deployment-patch-develop.yml
env
secretKeyRef: env-dev
key: HubApi
image
mildang-backend-hub-api-develop
stage
deployment-patch-stage.yml
env
secretKeyRef: env-stage
key: HubApi
image
mildang-backend-hub-api-staging
prod
deployment-patch-prod.yml
env
secretKeyRef: env-prod
key: HubApi
image
mildang-backend-hub-api-production
aws secret manager
crm-api
mildang-backend-crm-api-stage
dev에 추가된 필드 싱크
mildang-backend-crm-api-prod
dev에 추가된 필드 싱크
crm-worker
mildang-backend-crm-worker-dev
mildang-backend-crm-worker-stage 만들어야함, DB dev
dev에 추가된 필드 싱크
mildang-backend-crm-worker-prod
dev에 추가된 필드 싱크
hub-api
mildang-backend-hub-api-dev
mildang-backend-hub-api-stage
dev에 추가된 필드 싱크
mildang-backend-hub-api-prod
dev에 추가된 필드 싱크
CRM_API_BASE_URL
hub-gateway
MILDANG_HUB_SUBGRAPH_URL
사전작업 mildang-backend-hub-api-sevice 올리기
gradle jib
crm-api
crm-worker
hub-api
external secret store
crm-api
dev, stage, prod
hub-api
dev, stage, prod
crm-worker
dev, stage, prod
confluent topic 생성
sa-dev
sa-stage
sa-prod
argo application
crm-api
dev,stage,prod
hub-api
dev,stage
prod
crm-worker
dev
stage
prod
sa production 배포
체리픽
sa ingress
hub
crm
gateway 배포 (refresh-token)
배포 이후 migration 작업
기존 sales_counseling migration 처리 (FE 배포 전에 완료되어야 합니다)
SalesCounseling
counseling_type -> "SALES_COUNSELING"
title -> "판매팀 상담 내역"
prose_mirror_content -> default value 그대로 사용
counseling_time -> 음성파일 전체길이
counseling_method -> 음성파일 포함 시 "PHONE" else "KAKAO_TALK"
payment_key -> legacy purchaseId 로 paymentKey 조회해서 적용
StudentRecord
subject -> legacy purchase 조회 후 product name 으로 검색해서 subject 적용
priority -> "REFERENCE"
created_at, updated_at -> student_record 의 counseling_date 로 hard update
CounselingTag
tag -> "SALES_COUNSELING"
updated_at 을 수동업데이트 처리
배포 시 주의사항
•
SA 미리 배포
•
존재하지 않는 APP 전부 생성
•
secret manager 전부 적용
•
Hub producdtion 배포 직후에 gateway 에서 crm-api-service 로 요청하는 것을 hub-api app 을 타도록 변경해야 한다. → secret 교체 후 gateway 리스타트
•