timescale/promscale_extension

Automatically detect and warn on DB objects without explicit GRANT to prom_* roles

Open

#91 opened on Feb 25, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)PLpgSQL (19 forks)auto 404
good first issue

Repository metrics

Stars
 (37 stars)
PR merge metrics
 (PR metrics pending)

Description

In the current Promscale SQL, there are a small number of objects which do not have an explicit GRANT to one of the prom_reader, prom_writer, ... roles. This means that these objects are not participating in the permissions system properly.

In principle we know that every object should have at least one acl entry which references one of the prom_* roles.

It should be relatively simple to write a CI job which validates that all objects in the prom_* schemas also have at least one acl assigned to one of the prom_* roles.

Contributor guide

Research direction
Write a SQL query to find objects in prom * schemas without GRANT to prom * roles. Then create a CI job that runs this query and fails if any objects are found.
Tech stack
sqlpostgresql
Domain
backenddatabaseci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
SQLPostgreSQLCI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60