https://github.com/gfleury/squaas

sql query as a service
https://github.com/gfleury/squaas

approval-process authorization gdpr postgresql query queue sql

Last synced: about 2 months ago
JSON representation

sql query as a service

• Host: GitHub
• URL: https://github.com/gfleury/squaas
• Owner: gfleury
• Created: 2019-08-24T18:04:05.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2019-12-04T09:58:22.000Z (over 6 years ago)
• Last Synced: 2025-03-26T13:48:04.192Z (about 1 year ago)
• Topics: approval-process, authorization, gdpr, postgresql, query, queue, sql
• Language: JavaScript
• Size: 4.32 MB
• Stars: 4
• Watchers: 1
• Forks: 0
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
[![Build Status](https://travis-ci.org/gfleury/squaas.svg?branch=master)](https://travis-ci.org/gfleury/squaas) [![codecov](https://codecov.io/gh/gfleury/squaas/branch/master/graph/badge.svg)](https://codecov.io/gh/gfleury/squaas)

# SQUAAS

SQUAAS (SQL query as a service). Despite the hipster name, this is all a mistake.

An automated solution to a bad habit. However sometimes we need to look for a proper way of doing wrong things.

## Query Flow

```text

[On Hold] (Query can still be edited)

    |

[Ready] - After enough approvals -> [Approved] - Query is added to the running queue -> [Done/Failed]

```

## Goals

- Remove developers direct access to the databases (Only PostgreSQL support for now)

- Enforce some behaviors on the queries (must have transactions, no delete/update without where, hehe)

- Enforce queries to be run only with tickets (only Jira support for now)

- Enforce a flow where the queries have to be 'reviewed/approved' by other developers

- Prevent multiple 'user queries' from running in parallel in the database

- Simple 'built in' SQL parser (users can't add broken queries, used https://github.com/xwb1989/sqlparser for a while and now using https://github.com/lfittl/pg_query_go)

- Last but not least, learn some react