Jakob Drees @jakob-drees.bsky.social · 21/05/2026Very interesting! Thank you for the insight. We did it with a separate Pipeline in the past, that includes a more privileged user and requires additional signoff from the DBA team. But a package is interesting as well. I will play with the idea for a bit :) 010
Jakob Drees @jakob-drees.bsky.social · 20/05/2026Thank you! I thought I was missing something important. Do you still keep a separate "superadmin"-Deployment user to make SYS level changes (e.g. create new schemas, tablespaces, etc.)? Or do you have one mighty deployment user doing all operations (with or without proxy)? 100
Jakob Drees @jakob-drees.bsky.social · 20/05/2026But isn't this the same when you use a central deployment schema? You can lock the application schemas because the deployment user will just create and update objects with "create table app_schema.test_table". The credentials for the user would only be in the pipeline. 100
Jakob Drees @jakob-drees.bsky.social · 20/05/2026Sorry for digging out this ancient thread. But would you mind elaborating on the benefit of a proxy user in this scenario? Isn't the risk essentially the same, whether a deployment user can proxy into any schema or the deployment user is directly granted "CREATE ANY ... ON SCHEMA ..."? 100
Jakob Drees @jakob-drees.bsky.social · 26/03/2026Today, @ogobrecht.com and I have released version 1.3.0 of the great console logging framework. It includes many new unit tests and a breaking change to the "assert"-procedure. Check out what's new in my latest blog post: seedandpublish.com/blog/console...seedandpublish.comNew console v1.3 releaseAdding unit tests for logging 121