-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
0.0.1
- Validado de parametros en query - S
- Zen.preview(param=1) - S
- re-work database API - S
- Execution filter - S
- Default parameters - S
- Tests in CI - S
- Make release pipeline + release strategy
- Improve how Zens are printed in Screen - S
- When a query gets set as INVALID, save the error in the Zen execution - S
- Fix interpolation of parameters in cases like, val1, val2 -S
- Add more meta info to Execution model, re-use model in task return -S
- if run a new execution in client, and zen is unknown and execution is valid, set it as valid locally -S
- unwrap errors to flat messages (cratedb for example) -S
- add sane api to access data from results -S
- Release estrategy:
- build django app into docker image
- build package
- build docker composes to easily run stuff
0.0.2
- Stats - D
- Docs - DS
- api '/v1/ version to path - D
- Endpoint con stats: available workers (y su config básica) - D
- Auth - Users - JWT - D
0.0.3
- Permissions - D
- CedarDB driver - D
TODO
- Webhooks
- Scheduling
- sbom
- In final deployment step, check that DEBUG is False and _testing/clean_db does not exist.
- add https://docs.docker.com/build/ci/github-actions/test-before-push/
- make api image slimmer with .dockerignore
- make pipeline fail if tests actually fail
Small fixes
- how to distinguish query executions from different applications
- run celery worker inside docker image without superuser privileges
Ideas for later
- handle timeouts when database is not available -S
- Asynchronous runs - bulk zen run? e.g. qz.arun_bulk(zen, zen2, zen3, zen4)
- Schedule calls one after another, like chords?
- tag a queryzen execution
- caching?
- pydantic factory support for returning rows
Metadata
Metadata
Assignees
Labels
No labels