Merge branch 'main' into claude/issue-60-20260309-1819

Author: kukv

examples/webflux/actuator-endpoint/README.ja.md

@@ -4,17 +4,17 @@ Spring WebFlux アプリケーションにおける、Spring Boot Actuator エ
 
 ## 機能
 
-- `GET /actuator/endpoint-gates` -- 全フィーチャーフラグの一覧取得
-- `GET /actuator/endpoint-gates/{gateId}` -- 単一フィーチャーフラグの取得
-- `POST /actuator/endpoint-gates` -- フィーチャーフラグの更新（有効状態および任意のロールアウト）
-- `DELETE /actuator/endpoint-gates/{gateId}` -- フィーチャーフラグの削除
-- `EndpointGateChangedEvent` / `EndpointGateRemovedEvent` -- `@EventListener` によるイベントハンドリング
+- `GET /actuator/endpoint-gates` — 全ゲート一覧取得
+- `GET /actuator/endpoint-gates/{gateId}` — 単一ゲート取得
+- `POST /actuator/endpoint-gates` — ゲートの更新（有効/無効・ロールアウト割合・スケジュール）
+- `DELETE /actuator/endpoint-gates/{gateId}` — ゲートの削除
+- `EndpointGateChangedEvent` / `EndpointGateRemovedEvent` — `@EventListener` によるイベントハンドリング
 
 ## 設定
 
 ```yaml
-endpoint-gates:
-  features:
+endpoint-gate:
+  gates:
     demo-feature:
       enabled: true
       rollout: 80
@@ -34,17 +34,42 @@ management:
 `MutableInMemoryRolloutPercentageProvider` を自動的に登録します。
 これらは `@ConditionalOnMissingBean` により `webflux` モジュールのデフォルト（読み取り専用）プロバイダーを置き換えます。
 
-`EndpointGateEndpoint` は `/actuator/endpoint-gates` に公開され、アプリケーションを再起動せずにランタイムでフィーチャーフラグへの完全なCRUD操作を可能にします。
+内部的には `EndpointGateEndpoint` ではなく `ReactiveEndpointGateEndpoint` が使用されます。
+API のリクエスト/レスポンス形式は WebMVC 版と同一です。
+
+`EndpointGateEndpoint` は `/actuator/endpoint-gates` に公開され、アプリケーションを再起動せずにランタイムでゲートへの完全なCRUD操作を可能にします。
 
 書き込みまたは削除のたびにイベントが発行されます:
 - `EndpointGateChangedEvent`: `gateId()`、`enabled()`、`rolloutPercentage()`（変更されていない場合は null）
-- `EndpointGateRemovedEvent`: `gateId()`（フラグが実際に存在した場合のみ発行）
+- `EndpointGateRemovedEvent`: `gateId()`（ゲートが実際に存在した場合のみ発行）
 
 ## デモ手順
 
 1. アプリケーションを起動する
-2. 全フラグを一覧表示: `GET /actuator/endpoint-gates`
-3. 単一フラグを取得: `GET /actuator/endpoint-gates/demo-feature`
+2. 全ゲートを一覧表示: `GET /actuator/endpoint-gates`
+3. 単一ゲートを取得: `GET /actuator/endpoint-gates/demo-feature`
 4. another-feature を有効化: `POST /actuator/endpoint-gates` にボディ `{"gateId":"another-feature","enabled":true}` を送信
 5. another-feature を削除: `DELETE /actuator/endpoint-gates/another-feature`
-6. コンソールログで発行されたイベントを確認する
+6. demo-feature にスケジュールを設定する:
+   ```bash
+   curl -X POST http://localhost:8080/actuator/endpoint-gates \
+     -H "Content-Type: application/json" \
+     -d '{
+       "gateId": "demo-feature",
+       "enabled": true,
+       "scheduleStart": "2026-03-10T09:00:00",
+       "scheduleEnd": "2026-03-10T18:00:00",
+       "scheduleTimezone": "Asia/Tokyo"
+     }'
+   ```
+7. demo-feature のスケジュールを削除する:
+   ```bash
+   curl -X POST http://localhost:8080/actuator/endpoint-gates \
+     -H "Content-Type: application/json" \
+     -d '{
+       "gateId": "demo-feature",
+       "enabled": true,
+       "removeSchedule": true
+     }'
+   ```
+8. コンソールログで発行されたイベントを確認する

examples/webflux/actuator-endpoint/README.md

@@ -4,17 +4,17 @@ This example demonstrates runtime endpoint gate management via the Spring Boot A
 
 ## Features
 
-- `GET /actuator/endpoint-gates` -- list all endpoint gates
-- `GET /actuator/endpoint-gates/{gateId}` -- get a single endpoint gate
-- `POST /actuator/endpoint-gates` -- update a endpoint gate (enabled state and optional rollout)
-- `DELETE /actuator/endpoint-gates/{gateId}` -- remove a endpoint gate
-- `EndpointGateChangedEvent` / `EndpointGateRemovedEvent` -- `@EventListener` handling
+- `GET /actuator/endpoint-gates` — list all endpoint gates
+- `GET /actuator/endpoint-gates/{gateId}` — get a single endpoint gate
+- `POST /actuator/endpoint-gates` — update an endpoint gate (enabled state, rollout, and schedule)
+- `DELETE /actuator/endpoint-gates/{gateId}` — remove an endpoint gate
+- `EndpointGateChangedEvent` / `EndpointGateRemovedEvent` — `@EventListener` handling
 
 ## Configuration
 
 ```yaml
-endpoint-gates:
-  features:
+endpoint-gate:
+  gates:
     demo-feature:
       enabled: true
       rollout: 80
@@ -34,18 +34,43 @@ The `actuator` module automatically registers `MutableInMemoryEndpointGateProvid
 `MutableInMemoryRolloutPercentageProvider`, which replace the default read-only providers
 from the `webflux` module via `@ConditionalOnMissingBean`.
 
+Internally, `ReactiveEndpointGateEndpoint` is used instead of `EndpointGateEndpoint`.
+The request/response format is identical to the WebMVC version.
+
 The `EndpointGateEndpoint` is exposed at `/actuator/endpoint-gates` and allows full CRUD
 operations on endpoint gates at runtime without restarting the application.
 
 Events are published on every write or delete:
 - `EndpointGateChangedEvent`: `gateId()`, `enabled()`, `rolloutPercentage()` (null if not changed)
-- `EndpointGateRemovedEvent`: `gateId()` (only fired when the flag actually existed)
+- `EndpointGateRemovedEvent`: `gateId()` (only fired when the gate actually existed)
 
 ## Demo steps
 
 1. Start the application
-2. List all flags: `GET /actuator/endpoint-gates`
-3. Get a single flag: `GET /actuator/endpoint-gates/demo-feature`
+2. List all gates: `GET /actuator/endpoint-gates`
+3. Get a single gate: `GET /actuator/endpoint-gates/demo-feature`
 4. Enable another-feature: `POST /actuator/endpoint-gates` with body `{"gateId":"another-feature","enabled":true}`
 5. Delete another-feature: `DELETE /actuator/endpoint-gates/another-feature`
-6. Check the console log for published events
+6. Set a schedule on demo-feature:
+   ```bash
+   curl -X POST http://localhost:8080/actuator/endpoint-gates \
+     -H "Content-Type: application/json" \
+     -d '{
+       "gateId": "demo-feature",
+       "enabled": true,
+       "scheduleStart": "2026-03-10T09:00:00",
+       "scheduleEnd": "2026-03-10T18:00:00",
+       "scheduleTimezone": "Asia/Tokyo"
+     }'
+   ```
+7. Remove the schedule from demo-feature:
+   ```bash
+   curl -X POST http://localhost:8080/actuator/endpoint-gates \
+     -H "Content-Type: application/json" \
+     -d '{
+       "gateId": "demo-feature",
+       "enabled": true,
+       "removeSchedule": true
+     }'
+   ```
+8. Check the console log for published events

examples/webflux/condition/build.gradle.kts

@@ -0,0 +1,9 @@
+plugins {
+    id("example-base")
+    id("spotless-java")
+}
+
+dependencies {
+    implementation(project(":spring:spring-webflux"))
+    implementation(libs.spring.boot.starter.webflux)
+}

examples/webflux/condition/src/main/java/net/brightroom/example/condition/AdminController.java

@@ -0,0 +1,22 @@
+package net.brightroom.example.condition;
+
+import net.brightroom.endpointgate.core.annotation.EndpointGate;
+import org.springframework.web.bind.annotation.GetMapping;
+import org.springframework.web.bind.annotation.RestController;
+import reactor.core.publisher.Mono;
+
+/** Role-based condition example. Requires {@code X-User-Role: admin} header to access. */
+@RestController
+public class AdminController {
+
+  /**
+   * Returns admin dashboard content when the {@code X-User-Role} header equals {@code admin}.
+   *
+   * @return admin dashboard response
+   */
+  @EndpointGate("admin-panel")
+  @GetMapping("/api/admin/dashboard")
+  public Mono<String> adminDashboard() {
+    return Mono.just("Admin dashboard");
+  }
+}

examples/webflux/condition/src/main/java/net/brightroom/example/condition/BetaFeatureController.java

@@ -0,0 +1,24 @@
+package net.brightroom.example.condition;
+
+import net.brightroom.endpointgate.core.annotation.EndpointGate;
+import org.springframework.web.bind.annotation.GetMapping;
+import org.springframework.web.bind.annotation.RestController;
+import reactor.core.publisher.Mono;
+
+/**
+ * Query parameter-based condition example. Requires {@code beta=true} query parameter to access.
+ */
+@RestController
+public class BetaFeatureController {
+
+  /**
+   * Returns beta feature content when the {@code beta} query parameter equals {@code true}.
+   *
+   * @return beta feature response
+   */
+  @EndpointGate("beta-feature")
+  @GetMapping("/api/beta/feature")
+  public Mono<String> betaFeature() {
+    return Mono.just("Beta feature enabled");
+  }
+}

examples/webflux/condition/src/main/java/net/brightroom/example/condition/ConditionExampleApplication.java

@@ -0,0 +1,18 @@
+package net.brightroom.example.condition;
+
+import org.springframework.boot.SpringApplication;
+import org.springframework.boot.autoconfigure.SpringBootApplication;
+
+/** Entry point for the WebFlux condition example application. */
+@SpringBootApplication
+public class ConditionExampleApplication {
+
+  /**
+   * Starts the application.
+   *
+   * @param args command-line arguments
+   */
+  public static void main(String[] args) {
+    SpringApplication.run(ConditionExampleApplication.class, args);
+  }
+}

examples/webflux/condition/src/main/java/net/brightroom/example/condition/InternalApiController.java

@@ -0,0 +1,22 @@
+package net.brightroom.example.condition;
+
+import net.brightroom.endpointgate.core.annotation.EndpointGate;
+import org.springframework.web.bind.annotation.GetMapping;
+import org.springframework.web.bind.annotation.RestController;
+import reactor.core.publisher.Mono;
+
+/** Header-based condition example. Requires {@code X-Internal-Token} header to access. */
+@RestController
+public class InternalApiController {
+
+  /**
+   * Returns internal data when the {@code X-Internal-Token} header matches the expected value.
+   *
+   * @return internal data response
+   */
+  @EndpointGate("internal-api")
+  @GetMapping("/api/internal/data")
+  public Mono<String> getData() {
+    return Mono.just("Internal data");
+  }
+}

examples/webflux/condition/src/main/resources/application-fail-open.yml

@@ -0,0 +1,3 @@
+endpoint-gate:
+  condition:
+    fail-on-error: false

examples/webflux/condition/src/main/resources/application.yml

@@ -0,0 +1,13 @@
+endpoint-gate:
+  condition:
+    fail-on-error: true
+  gates:
+    internal-api:
+      enabled: true
+      condition: "headers['X-Internal-Token'] == 'secret-token'"
+    beta-feature:
+      enabled: true
+      condition: "params['beta'] == 'true'"
+    admin-panel:
+      enabled: true
+      condition: "headers['X-User-Role'] == 'admin'"

examples/webflux/functional-endpoint/src/main/java/net/brightroom/example/functional/FeatureHandler.java

@@ -19,4 +19,12 @@ public Mono<ServerResponse> beta(ServerRequest request) {
   public Mono<ServerResponse> experimental(ServerRequest request) {
     return ServerResponse.ok().bodyValue("experimental-api: this endpoint is under development.");
   }
+
+  public Mono<ServerResponse> internal(ServerRequest request) {
+    return ServerResponse.ok().bodyValue("internal-api: this endpoint is for internal use only.");
+  }
+
+  public Mono<ServerResponse> preview(ServerRequest request) {
+    return ServerResponse.ok().bodyValue("preview-feature: you are in the preview group!");
+  }
 }