Data connections from the studio

Until now, a report's database connections lived in config.yaml, so adding one meant editing a file and restarting the server. In 0.10.0 they're set up under Data sources › Connections, per environment, with no restart: PostgreSQL, MySQL, SQL Server, SQLite and HTTP. The form previews the connection string it will use and tests it before saving. Every change is in the audit log, and a change to a production binding asks to be confirmed.

An administrator decides first which hosts a connection may reach, in Admin › Settings › Studio connections. Until then, no connection can be saved. A new built-in role, Data administrator, manages connections and data sources without editing templates, so it doesn't take a designer seat.

Secrets in a store or a vault

A connection's password no longer has to sit in an environment variable. Secret plugins answer references such as secret:vault:kv/reporting/billing#password, and the image carries four of them:

  • The store plugin keeps the secrets people type into a connection form, encrypted with a master key you give it. It is in Community.
  • HashiCorp Vault, Azure Key Vault and AWS Secrets Manager read secrets you already keep there.

reportd runs only the plugins its config names. A value never reaches a command line, a log or a file reportd writes. The protocol is published, with an example plugin and a kit that checks a plugin against it, so you can write your own. Data connections and secret plugins in the docs say how to set them up.

Libraries that carry a house style

A linked library now gives a report its starting point: its theme, images, fonts and document settings. The report's own values override it, property by property, and the designer tags each value with where it comes from.

  • Page templates follow their library. A letterhead copied from a library takes the library's next release as a merge: what only the library changed comes in, what only the report changed stays, and you're asked where both changed.
  • Slots mark where each report puts its own content in a page template. A developer can lock the letterhead and leave the reference line to the people who write the letters.
  • Elements are sets of nodes kept in a library, such as a label beside its value, for any report to insert as a copy.
  • A new release, live. A report open in the designer takes a linked library's new release as soon as it reaches the report's environment, with the release notes.

Every modern locale

The engine now formats numbers, dates, currencies and plurals for every locale Unicode CLDR rates at modern coverage: 364 of them, up from 12. en-ZA writes R1 234,50, as South Africans do. A report can take its locale and currency from its data, so one invoice template bills a French customer in euros and an Australian one in dollars. RFML 0.3 adds default formats for numbers, dates and times.

In the designer

Spans style a few words inside a text. The Code view completes elements, attributes and style properties as you type, and renames a class or token everywhere it's used. Empty elements show their id on the canvas, so you can click and drop onto them. A warning comes five minutes before a sign-in ends, and if it does end, your unsaved changes wait in the page until you sign in again. F1 opens the docs for the version you're running. The gallery has eight new examples, and every example is now public domain (CC0), so you can copy them for anything.

Hardened

Before this release we reviewed the server, the engine and the studio end to end. Roles and API keys follow stricter rules, sign-ins are throttled more closely and failed ones are audited, and reports have fixed limits so that no one report can stop the engine. The image is signed with Sigstore, scanned for vulnerabilities and shipped with an SBOM. Each release also carries the source of the Debian packages in the image.

Upgrading from 0.9.0

Read Upgrading and the release notes before you upgrade. The main points:

  • Compose installs move from the .zip to a clone of report-server-releases. Copy your .env into its compose/ folder and start from there; it finds your data. Later upgrades are a git pull.
  • The data's format changes, and reportd backs it up first. 0.9.0 can't read the upgraded data, so going back means restoring that backup.
  • Upgrade every install that shares templates before you use RFML 0.3's new features: 0.9.0 can't open a 0.3 report.
  • Some settings and requests are stricter. reportd config check names any setting the new version refuses, without starting the server.