spring-io / dataflow.spring.io

Microsite for Spring Cloud Data Flow
https://dataflow.spring.io/
Apache License 2.0
41 stars 92 forks source link

Registering prebuilt applications documentation is confusing; does not produce expected results #131

Closed purecharger closed 5 years ago

purecharger commented 5 years ago

This page https://dataflow.spring.io/docs/installation/local/docker/ does not have the section "Registering Pre-Built Applications" that the other sections of the guide have.

And when a user does go to another section after having followed the instructions here for manual install via docker-compose, the provided dataflow commands produce no actual apps imported:

dataflow:>app import --uri https://dataflow.spring.io/rabbitmq-maven-latest Successfully registered 0 applications from [....long list see below.....]]

dataflow:>app import --uri https://dataflow.spring.io/kafka-maven-latest Successfully registered 0 applications from [source.sftp, source.mqtt.metadata, sink.mqtt.metadata, source.file.metadata, processor.grpc.metadata, processor.tcp-client, source.s3.metadata, source.jms, source.ftp, processor.transform.metadata, source.time, sink.mqtt, sink.s3.metadata, processor.scriptable-transform, sink.log, source.load-generator, processor.transform, source.syslog, sink.websocket.metadata, source.loggregator.metadata, source.s3, source.sftp-dataflow, source.load-generator.metadata, processor.pmml.metadata, source.loggregator, source.tcp.metadata, processor.httpclient.metadata, sink.file.metadata, processor.object-detection.metadata, source.triggertask, source.twitterstream, source.gemfire-cq.metadata, processor.aggregator.metadata, sink.task-launcher-dataflow.metadata, source.mongodb, source.time.metadata, source.gemfire-cq, sink.counter.metadata, source.http, sink.tcp.metadata, sink.pgcopy.metadata, source.rabbit, source.jms.metadata, sink.gemfire.metadata, sink.cassandra.metadata, processor.tcp-client.metadata, processor.header-enricher, sink.throughput, processor.python-http, sink.mongodb, processor.twitter-sentiment, sink.log.metadata, processor.splitter, source.tcp, processor.python-jython.metadata, processor.image-recognition, source.trigger, source.mongodb.metadata, source.sftp-dataflow.metadata, processor.bridge, source.http.metadata, sink.ftp, source.rabbit.metadata, sink.jdbc, source.jdbc.metadata, source.mqtt, processor.pmml, sink.rabbit.metadata, processor.python-jython, sink.router.metadata, sink.cassandra, processor.filter.metadata, source.tcp-client.metadata, processor.header-enricher.metadata, processor.groovy-transform, source.ftp.metadata, sink.router, sink.redis-pubsub, source.tcp-client, processor.httpclient, sink.file, sink.websocket, source.syslog.metadata, sink.s3, sink.counter, sink.rabbit, processor.pose-estimation, processor.filter, source.trigger.metadata, source.mail.metadata, sink.pgcopy, processor.python-http.metadata, sink.jdbc.metadata, sink.ftp.metadata, processor.splitter.metadata, sink.sftp, processor.grpc, processor.groovy-filter.metadata, processor.twitter-sentiment.metadata, source.triggertask.metadata, sink.hdfs, sink.task-launcher-dataflow, processor.groovy-filter, sink.redis-pubsub.metadata, source.sftp.metadata, processor.image-recognition.metadata, processor.bridge.metadata, processor.groovy-transform.metadata, processor.aggregator, sink.sftp.metadata, processor.tensorflow.metadata, sink.throughput.metadata, sink.tcp, source.mail, source.gemfire.metadata, processor.tensorflow, processor.counter, source.jdbc, processor.counter.metadata, processor.pose-estimation.metadata, sink.gemfire, source.gemfire, source.twitterstream.metadata, sink.hdfs.metadata, processor.tasklaunchrequest-transform, source.file, sink.mongodb.metadata, processor.tasklaunchrequest-transform.metadata, processor.scriptable-transform.metadata, processor.object-detection]

sabbyanandan commented 5 years ago

Hi, @purecharger. When using the Docker Compose experience, once when the servers and the dependent middleware components bootstrap successfully, we automatically also register the latest GA release of pre-built applications. That's why when you attempt to import the apps, you'd get the "Successfully registered 0 applications from" message. You can confirm the list of applications either from the dashboard or via app list command.

Since we already register the apps on user's behalf, the Docker Compose getting-started guide doesn't include explicit steps re: app registration.

I hope this clarifies.

sabbyanandan commented 5 years ago

Closing this due to no activity.