Releases: dataform-co/dataform
1.12.0: Add support for Snowflake secure views.
Add support for Snowflake secure views. (#1017)
1.11.1: Fix all Redshift assertions to use late-bound views.
Use late-binding views for Redshift assertions. (#1012) * Use late-binding views for Redshift assertions. * bump version
1.11.0: Remove support for bound views in Redshift. (#1008)
* Remove support for bound views in Redshift. * lewis comments
1.9.3: Fix transpilation of JS placeholders inside literal SQL strings. (#962)
* Fix transpilation of JS placeholders inside literal SQL strings. * bump version
1.9.2
1.9.1: Always run auto assertions (#959)
This release changes the behaviour of auto-assertions when running named actions from the CLI or via the API (or Dataform Web).
When running an action by name, the auto-assertions for the action will always be included in the run. They will still retain existing behaviour of not blocking any downstream actions unless explicitly added as dependencies.
This change doesn't require an upgrade of @dataform/core
in your project, but upgrading your CLI version with npm i -g @dataform/cli
.
1.8.6: BigQuery policy tag support (#939)
This release adds beta
support for setting BigQuery policy tags in table and view definitions. These can be set as part of the columns
specification in the configuration block. Currently only one tag can be set, and you must provide the fully qualified name of the tag (example below).
Read the documentation here for guides and examples: https://docs.dataform.co/warehouses/bigquery#managing-bigquery-policy-tags
1.6.1
Adds alpha support for connecting to Redshift/Postgres via an SSH tunnel.
Currently this needs to be configured manually, by editing the .df-credentials.json
file directly.
Example credentials JSON file for SSH tunnels
{
"username": "db-username",
"databaseName": "dev",
"password": "db-password",
"port": 5439,
"host": "internal-redshift-pg-hostname",
"sshTunnel": {
"host": "x-x-x-x-x.compute-1.amazonaws.com",
"port": 22,
"privateKey": "-----BEGIN RSA PRIVATE KEY-----\nMIIEpAI.......42qzB6+Ow==\n-----END RSA PRIVATE KEY-----",
"username": "ssh-username"
}
}
1.6.0
This release introduces potentially breaking changes, as we are now much more strict about excess properties in various configuration blocks.
Any excess properties that aren't allowed will be rejected and cause a compilation error, for example:
config {
unknownProperty: "x"
}
Will now throw an error. To resolve this, remove any excess properties as indicated by the errors. None of these properties would have had any impact on the project, so it's safe to remove them.