Optional postgres permissions

[vrish88]

Hello there!

Tonight I was working on getting elucidate deployed on heroku. One of the snags I ran into was the use of db permissions. On the hobbyist plan (aka the free one), they don't allow you to modify any roles or permissions. To get around this, I commented out all liquidbase sql statements that had anything to do with permission (ALTER FUNCTION ... OWNER, GRANT EXECUTE..., REVOKE ALL, etc).

Now these were obviously here for a good reason (ie a real production environment or something reasonable like that) however that reason didn't apply to my particular deployment configuration (one where the permissions are managed by the host).

Would you be open to a PR making the postgres permissions optional? Some solution which would allow elucidate to be deployed with/without postgres permissions configured?

One possible solution I came across was to use liquidbase labels to accomplish this. Thoughts?

Thank you for work of implementing the w3c annotation server! I was afraid I'd have to make my own implementation but then I fortuitously came across all the work done here!

[danielgrant]

Hi @vrish88,

The point you've raised here is valid and indeed it's probably a bit presumptuous of us to assume that everyone would want to adopt the same permissions model in their PostgreSQL database as we have when we originally put this together.

The quickest way to turn this around would probably be to open a PR against this repository with the changes you'd like to see. Otherwise it might be some time before myself or another maintainer would be able to pick it up, if at all.

Cheers,
Daniel.