Skip to main content
This release is built from Vantage Cloud 3.2.2. For the product features, improvements, and fixes in that version, see the Vantage 3.2.2 release notes.

​
Breaking changes

​
Reporting is now opt-in

The reporting workload is now deployed only when vantage.reportingEnabled is true. The default is false. If you use reporting, set vantage.reportingEnabled: true before you upgrade. Reporting requires Microsoft SQL Server. For more information, see Reporting requires SQL Server.

​
Features

​
PostgreSQL support

Vantage self-hosted can now use PostgreSQL. Set vantage.databaseProvider to PostgreSQL (the default is SqlServer) and provide a connection string for each service’s database. Reporting is not available with PostgreSQL. For more information, see PostgreSQL and per-service Secrets.

​
Improvements

  • When reporting is turned off, the reportingDatabaseConnectionString secret is no longer required.

​
Fixes

  • Fixed an issue where upgrading to a new chart version through ArgoCD, Flux, or other GitOps tools did not update Vantage.
  • Emails sent by the authentication service now use the sender address in vantage.mailFrom.