oscerd opened a new pull request, #2012: URL: https://github.com/apache/camel-spring-boot/pull/2012
Fixes [CAMEL-25185](https://issues.apache.org/jira/browse/CAMEL-25185). `camel-openfga` landed on `main` for 4.23.0 in [CAMEL-25028](https://issues.apache.org/jira/browse/CAMEL-25028) ([apache/camel#26974](https://github.com/apache/camel/pull/26974)), so it gets a starter alongside its two companions, `camel-opa-starter` and `camel-spiffe-starter`. ## What is hand-written * `components-starter/camel-openfga-starter/pom.xml` — `camel-openfga` plus `camel-core-starter`, following `camel-opa-starter`. * The `META-INF` `LICENSE.txt` / `NOTICE.txt` boilerplate. * Registration in `components-starter/pom.xml`, `tooling/camel-spring-boot-bom/pom.xml`, `tooling/camel-spring-boot-dependencies/pom.xml`, and `docs/spring-boot/modules/ROOT/nav.adoc`. ## What is generated Everything else comes from `camel-spring-boot-generator-maven-plugin`, which ran all five of its goals: the auto-configuration, configuration and converter classes, `src/main/docs/openfga.json`, the `AutoConfiguration.imports` entry, the `camel-catalog-provider-springboot` entries, and the starter documentation page. Thirty options bind. The ones worth a glance, since they are not plain scalars: | option | binds as | |---|---| | `connect-timeout`, `read-timeout` | `Long` (millisecond values, declared `javaType = "java.time.Duration"` on the component) | | `open-fga-client` | `dev.openfga.sdk.api.client.OpenFgaClient`, autowired | | `ssl-context-parameters` | `SSLContextParameters` | | `configuration` | `OpenFgaConfiguration` | `api-token` and `client-secret` are the component's secrets, and `fail-open` is the option annotated `security = "insecure:dev"` there. ## Not in scope `OpenFgaSecurityPolicy` gets no auto-configuration: it is a plain bean rather than a component, so an application declares it as a `@Bean` exactly as it would outside Spring Boot. Note that `useGlobalSslContextParameters` on the component does not reach that policy — the component documentation covers this. ## One thing found while building, deliberately left out The full reactor also regenerated the **spiffe** starter, adding an `x509Response` option that exists in `camel-spiffe` on camel's `main` but is not yet in this repo's committed `camel-spiffe-starter`. That change is legitimate but has nothing to do with this PR, so I reverted it rather than fold an unrelated starter update into a new-starter commit. It is worth a separate regen: `camel-spiffe-starter` is currently a `9`-option starter here against a 10-option component upstream. This PR itself deletes nothing — 15 files, all additions, the same file set as the `camel-opa-starter` commit (`7a3d8d14bad`). `camel-openfga:4.23.0-SNAPSHOT` is already published to the ASF snapshot repository, so the starter resolves and CI should not hit the usual new-component snapshot lag. --- _Claude Code on behalf of @oscerd_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
