Skip to content

Commit 2b6b665

Browse files
committed
docs improvements
Signed-off-by: Attila Mészáros <[email protected]>
1 parent f43cf54 commit 2b6b665

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/content/en/docs/features/_index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -472,7 +472,7 @@ public class WebappReconciler
472472

473473
@Override
474474
public Map<String, EventSource> prepareEventSources(EventSourceContext<Webapp> context) {
475-
InformerConfiguration<Tomcat> configuration =
475+
InformerEventSourceConfiguration<Tomcat> configuration =
476476
InformerEventSourceConfiguration.from(Tomcat.class, Tomcat.class)
477477
.withSecondaryToPrimaryMapper(webappsMatchingTomcatName)
478478
.withPrimaryToSecondaryMapper(
@@ -547,7 +547,7 @@ fabric8 Kubernetes client class, that will listen for events associated with the
547547
you configured your `InformerEventSource` with. If you want to listen to Kubernetes resource
548548
events, `InformerEventSource` is probably the only thing you need to use. It's highly
549549
configurable so you can tune it to your needs. Take a look at
550-
[InformerConfiguration](https://github.com/java-operator-sdk/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/informer/InformerConfiguration.java)
550+
[InformerEventSourceConfiguration](https://github.com/operator-framework/java-operator-sdk/blob/main/operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/config/informer/InformerEventSourceConfiguration.java)
551551
and associated classes for more details but some interesting features we can mention here is the
552552
ability to filter events so that you can only get notified for events you care about. A
553553
particularly interesting feature of the `InformerEventSource`, as opposed to using your own

0 commit comments

Comments
 (0)