Skip to content

feat: 가벼운 자체 구현 Feature Flag 추가 - #237

Merged
unam98 merged 1 commit into
mainfrom
feat/lightweight-feature-flag
Aug 11, 2026
Merged

feat: 가벼운 자체 구현 Feature Flag 추가#237
unam98 merged 1 commit into
mainfrom
feat/lightweight-feature-flag

Conversation

@unam98

Copy link
Copy Markdown
Collaborator

작업 배경

Trunk-Based Development(#236)에서 "미완성 기능은 브랜치를 오래 살려두지 말고 feature flag로 감싸 main에 빠르게 합친다"를 실제로 가능하게 하는 최소 장치가 아직 없었다. SaaS(GrowthBook/LaunchDarkly류) 대신 가벼운 자체 구현을 선택했다.

변경 사항

영역내용
config/featureflag/FeatureFlagProperties.java (신규)feature-flags.flags.{key}: true/false 값을 Map<String, Boolean>으로 바인딩
config/featureflag/FeatureFlags.java (신규)isEnabled(key) — yml에 없는 키는 기본값 false(비활성)로 처리
README.mdFeature Flag 사용법(yml 예시 + 코드 예시) 섹션 추가

영향 범위

  • 아직 어떤 서비스 로직도 이 플래그를 참조하지 않음 — 순수 스캐폴딩, 런타임 동작 변화 없음
  • yml에 feature-flags 섹션이 없어도 flags가 빈 Map으로 초기화되어 앱 구동에 영향 없음

검증 매트릭스

영향 범위테스트 코드
활성화된 플래그 조회yml에_true로_설정된_플래그는_활성이다
비활성화된 플래그 조회yml에_false로_설정된_플래그는_비활성이다
정의되지 않은 키의 기본값yml에_정의되지_않은_플래그는_기본값으로_비활성이다

Test Plan

  • 로컬 postgres/redis 기동 후 ./gradlew test 전체 254/254 통과

🤖 Generated with Claude Code

트렁크 기반 개발에서 미완성/위험도 있는 기능을 브랜치에 오래
묵히지 않고 main에 먼저 merge한 뒤, 배포 이후 원하는 시점에
켤 수 있게 하기 위한 최소 구현. SaaS(GrowthBook 등) 대신
application.yml의 feature-flags.flags.{key}: true/false 값을
FeatureFlagProperties로 바인딩하고, FeatureFlags.isEnabled(key)로
조회한다. 정의되지 않은 키는 기본값 false(비활성)로 취급한다.
@coderabbitai

Copy link
Copy Markdown

Warning

Review limit reached

@unam98, you've reached your PR review limit, so we couldn't start this review.

Next review available in:29 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c64e7a0c-8114-4b69-95e8-a08381a7ad1e

📥 Commits

Reviewing files that changed from the base of the PR and between 8da4563 and 6b34a8b.

📒 Files selected for processing (4)
  • README.md
  • src/main/java/org/runnect/server/config/featureflag/FeatureFlagProperties.java
  • src/main/java/org/runnect/server/config/featureflag/FeatureFlags.java
  • src/test/java/org/runnect/server/config/featureflag/FeatureFlagsTest.java

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@unam98
unam98 merged commit 85dbd1b into mainAug 11, 2026
2 checks passed
@unam98
unam98 deleted the feat/lightweight-feature-flag branch August 11, 2026 07:39
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@unam98@alh0409