refactor: 백엔드 리펙토링 진행 중

This commit is contained in:
DongHyeonka
2026-09-25 17:57:07 +09:00
parent fe80bb3ff3
commit fcddab7e2a
7518 changed files with 3217541 additions and 21259 deletions
@@ -112,6 +112,7 @@ class FileserverUploadServiceConfiguration {
QuotaCommitGateway quotaGateway,
CleanupQueue cleanupQueue,
RecoveryQueue recoveryQueue,
FileAccessPolicy accessPolicy,
LocalBlockingContentStore store,
TransactionPort transactions,
Clock clock) {
@@ -123,6 +124,7 @@ class FileserverUploadServiceConfiguration {
quotaGateway,
cleanupQueue,
recoveryQueue,
accessPolicy,
store.effectivePublishMode(),
transactions,
clock);
@@ -53,7 +53,7 @@ runtimeOnly project(':composition:notification-platform') // 알림
| 언제 | 키 |
| --- | --- |
| 항상 | persistence-jpa 줄과 그 연결 env(`APP_DATASOURCE_URL`, `APP_DATASOURCE_USERNAME`, `APP_DATASOURCE_PASSWORD`) |
| 항상 (키 8종과 각 키 id, 32바이트 이상 base64, 서로 달라야 함) | `APP_NOTIFICATION_PLATFORM_{CONTACT_ENCRYPTION,CONTACT_LOOKUP_HMAC,CALLBACK_SIGNING,PROVIDER_CREDENTIAL,PAYLOAD_ENCRYPTION,VAPID_SIGNING,PROVIDER_REQUEST_LOOKUP_HMAC,CALLBACK_FINGERPRINT_HMAC}_KEY`, 같은 이름 + `_ID` |
| 항상 (키 7종과 각 키 id, 32바이트 이상 base64, 서로 달라야 함) | `APP_NOTIFICATION_PLATFORM_{CONTACT_ENCRYPTION,CONTACT_LOOKUP_HMAC,CALLBACK_SIGNING,PROVIDER_CREDENTIAL,PAYLOAD_ENCRYPTION,PROVIDER_REQUEST_LOOKUP_HMAC,CALLBACK_FINGERPRINT_HMAC}_KEY`, 같은 이름 + `_ID` |
| SMTP provider | `APP_NOTIFICATION_PLATFORM_SMTP_ENABLED=true`, `APP_NOTIFICATION_PLATFORM_SMTP_SENDER_IDENTITY`, `SPRING_MAIL_HOST`, `SPRING_MAIL_PORT`, `SPRING_MAIL_USERNAME`, `SPRING_MAIL_PASSWORD` |
| SES provider | `APP_NOTIFICATION_PLATFORM_SES_ENABLED=true`, `APP_NOTIFICATION_PLATFORM_SES_SENDER_IDENTITY`, `APP_NOTIFICATION_PLATFORM_SES_ACCESS_KEY_ID`, `APP_NOTIFICATION_PLATFORM_SES_CREDENTIAL_KEY_ID`, `APP_NOTIFICATION_PLATFORM_SES_REGION` |
| provider 콜백 | `APP_NOTIFICATION_PLATFORM_CALLBACKS_ENABLED=true`, SES는 `APP_NOTIFICATION_PLATFORM_SES_ALLOWED_TOPIC_ARNS`, 프록시 뒤라면 `APP_NOTIFICATION_PLATFORM_CALLBACK_TRUSTED_PROXIES` |
@@ -6,7 +6,7 @@
# application-{profile}.yml, 환경 변수보다 낮음). 배포별 오버라이드는 그대로 우선한다.
#
# The platform is on while this module is present, like every capability: selecting the module is
# the decision to run it. On needs the notification schema (the persistence-jpa module), the eight
# the decision to run it. On needs the notification schema (the persistence-jpa module), the seven
# keys under secrets, and — in SERVING mode — at least one assembled provider profile; see
# docs/notification/configuration-reference.md. Off (APP_NOTIFICATION_PLATFORM_ENABLED=false) means
# no provider runtime, schema activation check, scheduler thread, notification secret or Spring Boot
@@ -64,7 +64,7 @@ ca-skeleton:
#
# providers:
# ses-primary:
# type: SES # APNS | FCM | SES | SMTP | TWILIO | WEB_PUSH | WEBHOOK
# type: SES # SES | SMTP
# enabled: true
# primary-for-channel: true # exactly one primary per channel
# environment: PRODUCTION
@@ -126,14 +126,14 @@ ca-skeleton:
sender-identity: ${APP_NOTIFICATION_PLATFORM_SMTP_SENDER_IDENTITY:no-reply@example.invalid}
max-concurrency: ${APP_NOTIFICATION_PLATFORM_SMTP_DISPATCH_CONCURRENCY:4}
# ---- Key material -------------------------------------------------------
# Eight purposes, eight keys, each base64 of at least 32 bytes and each distinct from every
# Seven purposes, seven keys, each base64 of at least 32 bytes and each distinct from every
# other. The platform decodes them at startup and refuses to boot if one is blank, short or
# shared: a blank value used to be skipped, so the platform started without the key and found
# out on the first contact point — in production, on a user's notification.
#
# These were bound by nothing until now. The subtree was missing from this file entirely while
# the settings record and its validator existed, so `enabled: true` was an unconditional boot
# failure in every environment and the only way to discover the eight names was to read the
# failure in every environment and the only way to discover the seven names was to read the
# record. That is the gap this block closes; the empty defaults keep a deployment with the
# platform off from having to supply anything.
#
@@ -144,7 +144,6 @@ ca-skeleton:
callback-signing-key: ${APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY:}
provider-credential-key: ${APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY:}
payload-encryption-key: ${APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY:}
vapid-signing-key: ${APP_NOTIFICATION_PLATFORM_VAPID_SIGNING_KEY:}
provider-request-lookup-hmac-key: ${APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY:}
callback-fingerprint-hmac-key: ${APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY:}
# The id written into every envelope this key produces, one per purpose, keyed by the
@@ -158,7 +157,6 @@ ca-skeleton:
CALLBACK_SIGNING: ${APP_NOTIFICATION_PLATFORM_CALLBACK_SIGNING_KEY_ID:}
PROVIDER_CREDENTIAL: ${APP_NOTIFICATION_PLATFORM_PROVIDER_CREDENTIAL_KEY_ID:}
PAYLOAD_ENCRYPTION: ${APP_NOTIFICATION_PLATFORM_PAYLOAD_ENCRYPTION_KEY_ID:}
VAPID_SIGNING: ${APP_NOTIFICATION_PLATFORM_VAPID_SIGNING_KEY_ID:}
PROVIDER_REQUEST_LOOKUP_HMAC: ${APP_NOTIFICATION_PLATFORM_PROVIDER_REQUEST_LOOKUP_HMAC_KEY_ID:}
CALLBACK_FINGERPRINT_HMAC: ${APP_NOTIFICATION_PLATFORM_CALLBACK_FINGERPRINT_HMAC_KEY_ID:}
# Superseded material, kept readable, grouped by the purpose it served and then by the id