Releases: pantsel/konga
v0.9.0-1
v0.9.0
What's new
A database update is required! Make sure you run Konga in dev mode once so that
the migrations will take place.
- [Enhancement] Only admin users can access snapshots.
- [Enhancement] You don't have to manually specify Kong version when creating a connection anymore. It is now retrieved automatically throughout the application.
- [Enhancement] You can now schedule your Kong node snapshots and leave Konga to do the rest.
- [Enhancement] Introducing connection types (Breaking change).
- [Enhancement] Added support for
JWT Auth Loopback API
. - [Fix] Fixed some issues with snapshots and snapshot restoration.
- [Fix] Consumer imports are working again.
- [Fix] Fixed database info display on dashboard page when using Cassandra.
Breaking Changes
Due to the new Connection types logic, the existing connections to Kong admin
API are likely to stop working. You will need to create new ones using the new forms.
No data or settings will be lost.
v0.8.9
v0.8.8
What's new
- When starting the app for the first time using postgres or MySQL adapters, Konga will now create the databases automatically.
- Parts of UI are redesigned in a cleaner way.
- Consumer page now also displays the APIs a consumer can access based on his ACLs.
- Slack integration. You can now configure Konga to send notifications to slack.
- Fix issue which prevented consumer creation with empty username or custom_id.
- Other minor bug fixes and improvements.
v0.8.7
CHANGELOG
- [FIX] Tests are working again.
- [FIX] Better error handling when adding groups and credentials to consumers.
- [FIX] kongadata dir is now created inside the project folder by default. The docker volume now becomes /app/kongadata
v0.8.5
v0.8.4
v0.8.3
v0.8.1
v0.8.0
What's new
- UI/UX revamp.
- Massive refactoring and logic improvements.
- Configurable user permissions.
- Various bug fixes and improvements.
Default db and data paths changed
Default file storage path (in case you're not integrating Konga with a database) has been moved outside of the application's directory so it can be used as a docker volume.
The default storge path is /kongadata/
but it can be changed from the process.env.STORAGE_PATH
env var.
If you're building Konga from source, you can specify it yourself to be in a folder where Konga has read-write permissions so that you don't get the EACCES: permission denied, mkdir '/kongadata/'
error when running the application.