You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we rely on the jaws-libp container to initialize Kafka topics and also initialize the Schema Registry. This should be done via this app (delegating to jaws-libj) and then the jaws-libp container would not be needed when the admin GUI app is in use. Probably the jaws-libj command line needs to be shored up as well if it is to be a drop in replacement (and jaws-libj CLI scripts also must be installed into the admin GUI container).
The text was updated successfully, but these errors were encountered:
Getting Kafka configured quickly is in the critical path and the Wildfly app server boots relatively slowly so consider simply moving scripts to admin container.
Currently we rely on the jaws-libp container to initialize Kafka topics and also initialize the Schema Registry. This should be done via this app (delegating to jaws-libj) and then the jaws-libp container would not be needed when the admin GUI app is in use. Probably the jaws-libj command line needs to be shored up as well if it is to be a drop in replacement (and jaws-libj CLI scripts also must be installed into the admin GUI container).
The text was updated successfully, but these errors were encountered: