rig_postgres 0.4.0

rig_postgres: ^0.4.0 copied to clipboard

• The suite marker rule and the database naming moved into rig; this package now uses them. No API change.
• Fixed along the way: reading a suite marker no longer throws when another suite's teardown removes it at the same moment.

No functional change in this package. It moves to rig: ^0.3.0, because ^0.2.0 does not admit rig 0.3.0 and would otherwise hold you to rig 0.2.x.

No functional change in this package. It moves to rig: ^0.2.0, because ^0.1.0 does not admit rig 0.2.0 and would otherwise hold you to rig 0.1.x.

One consequence is worth knowing: rig 0.2.0 changes every configuration hash, so the containers 0.1.0 left running are not reused. The first run on this version creates fresh ones and leaves the old ones behind; rig prune clears them.

First release.

• usePostgres() gives a test suite a Postgres container and a connection string for it.
• The authentication method is genuinely in force. Naming PgAuth.md5 or PgAuth.scram is not enough on its own: Postgres stores a verifier when the password is set, so changing the method afterwards leaves the old verifier in place and a test that believes it exercises md5 exercises nothing. usePostgres re-hashes the password once the server is up and then confirms the stored verifier has the shape the method requires.
• A database per suite. Suites sharing a container each get their own database, created before the suite runs and dropped when it ends, so concurrent suites never see each other's tables.
• Databases left behind by a run that died before teardown are reclaimed on a later run, guarded by a marker file so a suite between connections is not mistaken for an abandoned one.
• PgTls.selfSigned generates a certificate with the host's openssl and arranges for Postgres to read it, working around bind mounts appearing as root:root inside the container.
• verboseLogs: true turns on statement, connection and duration logging.
• Speaks to the server through psql inside the container, so this package adds no Postgres client dependency — the client side of md5, SCRAM and TLS is exactly what tests using this package are usually there to verify.