Feature Requests

When using the DBApply step, if there is an error users are required to set up a second run step to parse execution logs for error messages to update ticketing systems, having the errors as an accesible expression during rollback would be really useful.

At this time, the build image that Harness uses is predefined and the only way to modify them is via API endpoints ( https://developer.harness.io/docs/database-devops/overview/#configure-harness-db-devops-image-versions ) For customers that have stricter security requirements, the default image may not always fulfill their needs such that it would be great if they could declare a specific image version when executing DB DevOps workflows in their pipelines.

We need a custom dashboard widget in Harness DB DevOps that displays a summary table showing all instances alongside their most recently deployed tag / running schema version. This is a critical requirement for us to achieve visibility across our entire DB estate from a single view, and is a blocker for us to move forward with Q2 onboarding of our DB deployments. Current Behaviour: The current Dashboards (account-level) show a time-series/historical view of all executions — meaning all tags deployed to each instance are listed, not just the latest one. There is no way to collapse/filter the data to show only the most recently deployed tag per instance. We explored using Step Execution Start Time as a proxy for the latest timestamp, but there is no sort filter available within the widget to surface only the latest record per instance. Expected / Desired Behaviour: A dashboard widget (or dedicated view) that shows a table with the following columns: Instance Name Schema Name Environment Latest Deployed Tag / Running Schema Version The table should show only the most recent tag per instance (not the full deployment history), with filter options for Schema Name, Environment, and Instance Name.

We would like a way to add our custom standards/requirements for changes into Author DB Change context. For example, if we have a requirement where each new table or column must have a comment providing ownership, this requirement must be part of changeset generated.

When managing reference data that ships with the application, it would be nice to automatically sync deltas in from a CSV file like we can using the relational databases using the loadUpdateData change type