Alexander Schwartz 05d0c34681
Automatically connect to a writer instance of PostgreSQL (#40384)
Closes #40383

Signed-off-by: Alexander Schwartz <alexander.schwartz@gmx.net>
Co-authored-by: Václav Muzikář <vaclav@muzikari.cz>
Co-authored-by: Martin Bartoš <mabartos@redhat.com>
2025-07-04 16:46:49 +02:00

50 lines
2.1 KiB
Plaintext

// ------------------------ Breaking changes ------------------------ //
== Breaking changes
Breaking changes are identified as requiring changes from existing users to their configurations.
In minor or patch releases we will only do breaking changes to fix bugs.
=== <TODO>
// ------------------------ Notable changes ------------------------ //
== Notable changes
Notable changes where an internal behavior changed to prevent common misconfigurations, fix bugs or simplify running {project_name}.
=== Usage of the `exact` request parameter when searching users by attributes
If you are querying users by attributes through the User API where you want to fetch users that match a specific attribute key (regardless the value),
you should consider setting the `exact` request parameter to `false` when invoking the `/admin/realms/{realm}/users` using
the `GET` method.
For instance, searching for all users with the attribute `myattribute` set should be done as follows:
```
GET /admin/realms/{realm}/users?exact=false&q=myattribute:
```
The {project_name} Admin Client is also updated with a new method to search users by attribute using the `exact` request parameter.
=== Automatic database connection properties for the PostgreSQL driver
When running PostgreSQL reader and writer instances, {project_name} needs to always connect to the writer instance to do its work.
Starting with this release, and when using the original PostgreSQL driver, {project_name} sets the `targetServerType` property of the PostgreSQL JDBC driver to `primary` to ensure that it always connects to a writable primary instance and never connects to a secondary reader instance in failover or switchover scenarios.
You can override this behavior by setting your own value for `targetServerType` in the DB URL or additional properties.
// ------------------------ Deprecated features ------------------------ //
== Deprecated features
The following sections provide details on deprecated features.
=== <TODO>
// ------------------------ Removed features ------------------------ //
== Removed features
The following features have been removed from this release.
=== <TODO>