Christian Schwarz 4d41b2d379 fix: max_lsn_wal_lag broken in tenant conf (#4279) ...

This patch fixes parsing of the `max_lsn_wal_lag` tenant config item.
We were incorrectly expecting a string before, but the type is a
NonZeroU64.

So, when setting it in the config, the (updated) test case would fail
with

```
 E       psycopg2.errors.InternalError_: Tenant a1fa9cc383e32ddafb73ff920de5f2e6 will not become active. Current state: Broken due to: Failed to parse config from file '.../repo/tenants/a1fa9cc383e32ddafb73ff920de5f2e6/config' as pageserver config: configure option max_lsn_wal_lag is not a string. Backtrace:
```

So, not even the assertions added are necessary.

The test coverage for tenant config is rather thin in general.
For example, the `test_tenant_conf.py` test doesn't cover all the
options.

I'll add a new regression test as part of attach-time-tenant-conf PR
https://github.com/neondatabase/neon/pull/4255

2023-05-23 16:29:59 +03:00

..

benches

revert: "Add check for duplicates of generated image layers" (#4104)

2023-04-28 17:20:18 +03:00

fixtures

walredo: simple tests and bench updates (#3045)

2023-01-16 18:24:45 +02:00

src

fix: max_lsn_wal_lag broken in tenant conf (#4279)

2023-05-23 16:29:59 +03:00

Cargo.toml

feat(page_service): read timeouts (#4093)

2023-04-27 17:55:35 +00:00