[GitHub] [openwhisk] chetanmeh opened a new pull request #4680: Enable Standalone User Event Dev mode

[GitBox <gi...@apache.org>]

chetanmeh opened a new pull request #4680: Enable Standalone User Event Dev mode
URL: https://github.com/apache/openwhisk/pull/4680
 
 
   With #4656 support was added in standalone mode to launch the User Event service along with required Prometheus and Grafana service. This PR adds support for reusing an existing user-event service (say running with IDE) for faster local developement
   
   ## Description
   
   To enable fast local development of user-event service the Standalone OpenWhisk now support connecting to an existing running service instead of launching a new one via Docker
   
   First launch the standalone server with Kafka and pass the port where user-event service would be running (9095 by default)
   
   ```
   java -jar openwhisk-standalone.jar --dev-user-events-port 9095 --kafka --kafka-ui
   ```
   
   Then launch the `org.apache.openwhisk.core.monitoring.metrics.Main` via IDE with env set to `KAFKA_HOSTS=localhost:9092`
   
   After this one can do normal action invocation and see metrics appear in Grafana
   
   
   ## Related issue and scope
   <!--- Please include a link to a related issue if there is one. -->
   - [ ] I opened an issue to propose and discuss this change (#????)
   
   ## My changes affect the following components
   <!--- Select below all system components are affected by your change. -->
   <!--- Enter an `x` in all applicable boxes. -->
   - [ ] API
   - [ ] Controller
   - [ ] Message Bus (e.g., Kafka)
   - [ ] Loadbalancer
   - [ ] Invoker
   - [ ] Intrinsic actions (e.g., sequences, conductors)
   - [ ] Data stores (e.g., CouchDB)
   - [ ] Tests
   - [ ] Deployment
   - [ ] CLI
   - [ ] General tooling
   - [ ] Documentation
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Use `x` in all the boxes that apply: -->
   - [ ] Bug fix (generally a non-breaking change which closes an issue).
   - [ ] Enhancement or new feature (adds new functionality).
   - [ ] Breaking change (a bug fix or enhancement which changes existing behavior).
   
   ## Checklist:
   <!--- Please review the points below which help you make sure you've covered all aspects of the change you're making. -->
   
   - [ ] I signed an [Apache CLA](https://github.com/apache/openwhisk/blob/master/CONTRIBUTING.md).
   - [ ] I reviewed the [style guides](https://github.com/apache/openwhisk/wiki/Contributing:-Git-guidelines#code-readiness) and followed the recommendations (Travis CI will check :).
   - [ ] I added tests to cover my changes.
   - [ ] My changes require further changes to the documentation.
   - [ ] I updated the documentation where necessary.
   
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services