Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exclude tables from access #17

Open
cpdean opened this issue Apr 25, 2018 · 3 comments
Open

Exclude tables from access #17

cpdean opened this issue Apr 25, 2018 · 3 comments
Labels
enhancement New feature or request

Comments

@cpdean
Copy link
Contributor

cpdean commented Apr 25, 2018

Say we had a schema, the_data with three tables, a, b, and c. We have some users that have read/write access to all the tables in the_data, but after a while we decide that we do not like table b so we'd like to deprecate it by first restricting access to it for a while and then dropping the table properly later.

I'm open to other suggestions like "how about you just move table b to an off-limits schema", but I wanted to discuss if this is a pattern that's useful and if so what would that look like in the spec def?

@cpdean cpdean added the enhancement New feature or request label Apr 25, 2018
@zcmarine
Copy link
Contributor

@cboline's suggestion is that we have a list of objects that pgbedrock will just ignore, so that's one possibility.

@cpdean
Copy link
Contributor Author

cpdean commented Apr 25, 2018

ohh that's a good call. then we don't have to check weird interactions, we can just mark stuff to be ignored and manually manage it out of band from the spec.

@cboline cboline closed this as completed Apr 26, 2018
@cboline cboline reopened this Apr 26, 2018
@cpdean
Copy link
Contributor Author

cpdean commented Apr 26, 2018

yeah i guess we either rename this or open a new ticket for that feature request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants