8c9bcdeb1f
* Add '/notifications' endpoint for subscribing to server-sent events * Generate server and client * Try implementing the notification service endpoint * Revert "Try implementing the notification service endpoint" This does not seem to work because the generated server always responds with application/json, and it is not possible to respond with a different content-type. This reverts commit cf3ce83677649763b8166c4847501c37246dd757. * Revert "Generate server and client" This reverts commit b985c007a0561edbe185adc3b9582e12aa3f072b. * Revert "Add '/notifications' endpoint for subscribing to server-sent events" This reverts commit c5c903329f13dbe4ec096d83b1c8624fd622bef3. * Implement 'GET /notifications' SSE endpoint and logic to detect and notify Devfile changes * Leverage EventSource to subscribe to Server Sent Events Here, this is being used to automatically reload the Devfile in the YAML view whenever the API server notifies of filesystem changes in the Devfile (and related resources). * Add Preference Client to apiserver CLI This is needed to be able to persist Devfiles from the UI to the filesystem * Add E2E test case * fixup! Leverage EventSource to subscribe to Server Sent Events Co-authored-by: Philippe Martin <phmartin@redhat.com> * Limit the round-trips by sending the whole Devfile content in the DevfileUpdated event data Co-authored-by: Philippe Martin <phmartin@redhat.com> * [Cypress] Make sure to wait for APi responses after visiting the home page Co-authored-by: Philippe Martin <phmartin@redhat.com> * Generate static UI * fixup! [Cypress] Make sure to wait for APi responses after visiting the home page --------- Co-authored-by: Philippe Martin <phmartin@redhat.com>
odo - Developer-focused CLI for fast & iterative application development on Kubernetes
Overview
odo is a fast, and iterative CLI tool for developers who write, build, and deploy applications on Kubernetes and OpenShift.
Why use odo?
- Fast: Spend less time maintaining your application deployment infrastructure and more time coding. Immediately have your application running each time you save.
- Standalone:
odois a standalone tool that communicates directly with the Kubernetes API. There is no requirement for a daemon or server process. - No configuration needed: There is no need to dive into complex Kubernetes yaml configuration files.
odoabstracts those concepts away and lets you focus on what matters most: code. - Containers first: We provide first class support for both Kubernetes and OpenShift. Choose your favourite container orchestrator and develop your application.
- Easy to learn: Simple syntax and design centered around concepts familiar to developers, such as projects, applications, and components.
Learn more about the features provided by odo on odo.dev.
Installing odo
Please check the installation guide on odo.dev.
Official documentation
Visit odo.dev to learn more about odo.
Community, discussion, contribution, and support
Chat
All of our developer and user discussions happen in the #odo channel on the official Kubernetes Slack.
If you haven't already joined the Kubernetes Slack, you can invite yourself here.
Ask questions, inquire about odo or even discuss a new feature.
Issues
If you find an issue with odo, please file it here.
Contributing
- Code: We are currently working on updating our code contribution guide.
- Documentation: To contribute to the documentation, please have a look at our Documentation Guide.
We are an open community who welcomes any concerns, changes or ideas for odo! Come join the chat and hang out, ask or give feedback and just generally have a good time.
Meetings
All our calls are open to public. You are welcome to join any of our calls.
You can find the exact dates of all scheduled team calls together with sprint dates in the google calendar (iCal format).
Legal
License
Unless otherwise stated (ex. /vendor files), all code is licensed under the Apache 2.0 License.
Usage data
When odo is ran for the first time, you will be asked to opt-in to Red Hat's telemetry collection program.
With your approval, odo will collect pseudonymized usage data and send it to Red Hat servers to help improve our products and services. Read our privacy statement to learn more about it. For the specific data being collected and to configure this data collection process, see Usage data.