This project has been funded by DG ECHO and implemented by Caritas Switzerland and the CARMA Consortium.
All release notes for this project will be documented in this file; this project follows Semantic Versioning.
- Add CRUD classes to help with CRUD operations for the models
- Re-organize project structure
- Clean-up Hyperfile lifecycle functions
- Ensure stored refresh token is active on authentication. PR #40
- Validate configurations before creation / modification. PR #32
- Add additional export configurations. PR #27
- Add Health endpoint and export metrics using
starlette_exporter. PR #23 - Allow export settings to be configured via the API. PR #24
- Include question labels as headers & values instead of using the column name & value. PR #20
- Ensure that deletions work as expected with S3. PR #15
- Fix issue raised when queuing new jobs. PR #13
- Add sync lock mechanism and custom scheduler. PR #7
- Fails to correctly store job ID for queued jobs. Issue #11
This is the first release 🎊.
Project Breakdown: Duva is RESTful API that allows users to easily create & manage Tableau Hyper databases.
- Supports automatic creation and updates of Hyper databases from an OnaData server; The application utilizes OnaDatas Export functionality to create and update the database.
- Supports creation of Hyper databases from a CSV File.
The application as mentioned above supports creation of a one-time Hyper database from a CSV File; These databases are not updated after creation.
This flow is ideal for one-off hyper database or for Servers where automatic creation & updates are not supported. NB: As of v0.0.1 the application only supports OnaData servers.
In order for one to use this flow with a desired server, the user has to first register a new Server object. Which will be used to authenticate the application and users; allowing the application to pull data on behalf of the user on a scheduled basis in order to update the managed Hyper database.
Server registration flow(One-time flow for new servers):
After a new server is registered users from the registered server are now able to create managed Hyper database files.
During the creation of the managed hyper database, users can specify a Tableau server where the hyper database should be published too after every update of the hyper database. For more information on how to configure this please view the API Docs on a deployed instance of the application(/docs).
- The application currently uses session cookies to authenticate users; there are plans to phase out session cookies in favor of API Tokens. As of now users may need to clear the cookies in order to unauthenticate.