Does this prevent job queuing?

[rsanheim]

Heya cool project! Quick question - I see from the README:

allowing read-only external connections (disables job queueing, non-GET requests, etc.)

However, I'm not seeing anything that would prevent jobs getting enqueued via ActiveJob or Sidekiq or whatever. Am I missing the hook or code that would prevent that from happening?

We currently enforce a sandbox for our prod console via some scripting, but there is nothing preventing someone from accidentally kicking off some model method that enqueues a job that ends up modifying data off in a different process. I know there are various hooks and things that we could use in ActiveJob or Sidekiq, but came here looking to see if there are some nice established patterns to use 😁 .

[jturkel]

Apologies @rsanheim but this gem currently only supports sandboxing for Postgres connections. #1 and #22 are tracking generalizing this but we don't have any immediate plans to work on these issues (but contributions are always welcome). I'll fix the README to accurately reflect this.

[jturkel]

README updated in 0cdaeea02de8b2132bba9f5174239b56b3c8e48c.

[mileszim]

#50 handles this