It’s been a while since we last blogged about an Egeria release, but here’s an update on this week’s release of 1.8, along with a few changes we’ve been working on since the last blog, plus some important upcoming news
The github link elaborates more on the specifics for each release, but to cover a few themes:
- We continue to improve our documentation and tutorial content. In 1.8 we have the Egeria Dojo content which was used to support classes spanning 3 days covering how to work with Egeria as a developer. This extended what we had in the tutorials which can run under docker-compose or Kubernetes and offer a Jupyter notebook/python guide through how to drive Egeria, supported by User scenarios and explanatory text.
- As well as using REST Apis, or a business UI, visualizing what is in an Egeria metadata repository is very helpful for developers and admins to understand. We already had a Type Explorer (1.1) but in 1.7, plus improved in 1.8, is the Repository Explorer which can help you see all the myriad of entities with their attributes and relationships
- We are continuing to try and improve the packaging of Egeria. In 1.8 we now package samples and utilities in our assembly complete with dependencies so that they can more easily be run directly, for example using ‘java -jar’. Looking forward we’ll continue improving this for client libraries and connectors, and if you have any feedback please do get in touch.
- When a service such as Egeria is put into production, it’s important to be able to manage and monitor. Egeria itself provides some capabilities for this exposed over its rest API, but in addition, we’ve now added support for spring boot actuator and Prometheus. This also went into 1.8.
- As we develop Egeria we’re constantly paying attention to Dependencies. As well are reviewing their use & ensuring they are accurate, we also constantly monitor for updates – including security, so with each release, you will see dependencies being updated by Dependabot. This should make the code more reliable, easier to integrate with other current code and help to address security challenges before they become an issue.
- In recent releases, we’ve also added a new audit log framework (1.6) and support for metadata discovery (1.6) as well as many bug fixes.
- As you navigate to the documentation for each component now (such as the two above) you should clearly see if a component is released (ready to use), in Tech Preview (working, with caveats, subject to more change), or in Development.
- The swagger documentation has improved, so once Egeria is running if you go to http://localhost:8080/swagger-ui.html you will now see clearer information about our REST APIs. We will continue to improve.
- Finally, we continue to improve our build processes and keep up a regular monthly cycle of tested releases so that you can always benefit from the latest work the team is working on. This also extends to our dockerhub images which are now built and updated automatically – even from the master
In all, since the last blog on 1.4 we’ve made 2,205 commits across 3,867 files . To see more about current activity the Linux foundation has an insights dashboard which also gives stats on our issue tracking and slack activity as well as who is active
A note about 2.0 ….
As we look to the future I thought it worth mentioning one significant upcoming change. So far whilst our UI has supported https, the Egeria server has not. Enterprise-ready software needs to, so we’re making the switch in Release 2.0 to use https, as well as switch our default port for the server chassis to 9443. This will affect you, but only in-so-much as the URLs changing. Whilst we’ll have a self-signed certificate to keep you working, beyond development anyone will be advised to use their own certificates to maintain the security of the platform.
If you’re interested in finding out more whether about security, how to integrate, upcoming features, or have concerns or questions, do pop along to our slack channels to discuss and feel free to contribute to our github issues too. We also run weekly calls