I couldn't find an obvious way to run just the subset of tests which can be performed on a remote database.
It would be awesome if there was a flag that said "do everything you can without having access to the PGCONFIG folder". Many of the tests are purely query based, so it seems like we could get at least a partial audit if we could keep it from blowing up when it can't find that folder.
For those of us running postgresql in docker containers, or in hosted cloud implementations where some of the configuration is inaccessible, being able to survey what additional lockdown tweaks we can configure would be a big win. Operating at scale with hundreds of postgresql databases to support, I'm sure there are things we can do better, and automation is essential.
I couldn't find an obvious way to run just the subset of tests which can be performed on a remote database.
It would be awesome if there was a flag that said "do everything you can without having access to the PGCONFIG folder". Many of the tests are purely query based, so it seems like we could get at least a partial audit if we could keep it from blowing up when it can't find that folder.
For those of us running postgresql in docker containers, or in hosted cloud implementations where some of the configuration is inaccessible, being able to survey what additional lockdown tweaks we can configure would be a big win. Operating at scale with hundreds of postgresql databases to support, I'm sure there are things we can do better, and automation is essential.