ADA v0.6.0

1. Release info

2. Summary

Release 0.6.0 adds SQL preview from local YAML with per-entity files, explicit commit, promote and deploy steps, live metadata search and graph commands, and safer upgrade and update-notice handling. It also adds yanked and blocked release handling, and splits the push and pull commands into smaller internal steps.

3. API-key permission changes

The following API-key permissions need to be added to use the new features.

POST:

/external-api/api/s1234567/datahub/design/code/v1/preview
/external-api/api/s1234567/datahub/design/deployment/v1/promotions
/external-api/api/s1234567/datahub/design/deployment/v1/environments/DEV/instances/**

Use one environments/<ENVIRONMENT>/instances/** line for each runtime environment this key may deploy to, with the name exactly as ADE shows it. Environments are listed in promotion order by ada deploy environments. Leave out environments, such as production, that this key must not deploy to.

GET:

/external-api/api/s1234567/datahub/design/metadata/v1/search
/external-api/api/s1234567/datahub/design/metadata/v1/search/**
/external-api/api/s1234567/datahub/design/deployment/v1/environments/**
/external-api/api/s1234567/datahub/design/deployment/v1/promotions
/external-api/api/s1234567/datahub/design/deployment/v1/deployments
/external-api/api/s1234567/datahub/design/deployment/v1/commits

See full list: Setting up API keys for ADA

4. Features

SQL preview from local YAML

• ada code preview now previews the SQL ADE generates from your local YAML by default.

• --remote previews what is already in ADE, as before.

• -o <directory> writes one DDL file and one DML file per entity, plus a manifest.yaml with the run order.

• Entities are ordered by what their loads read. A dependency cycle fails with a clear error and nothing is written.

• --plan with -o <directory> prints the order and what to know before running, and writes nothing.

• SQL is written exactly as ADE returns it. Runtime variables such as <timemillis> stay as tokens.

• SOURCE entities are identified as SYSTEM/schema.NAME, so two source systems can share schema.NAME. Metadata-only SOURCE entities produce no file.

Example:

ada code preview -p STG_SALES -o sql_out

sql_out/
  manifest.yaml
  STG_SALES/
    staging.STG_CUSTOMER.ddl.sql
    staging.STG_CUSTOMER.dml.sql

Explicit commit, promote and deploy

• New ada deploy promote makes a commit the current version of its package in a runtime environment.

• New ada deploy start runs one deployment of everything promoted to an environment.

• New ada deploy environments and ada deploy commits list the available targets and a package's commits.

• ada deploy status accepts several commit IDs or package names and shows one compact block per commit.

• The CLI now tells ADE not to promote or deploy automatically. Set the following variable in config/pipeline.yaml to hand these steps back to ADE.

allow_automatic_deployment: true

• --wait keeps polling while a deployment is RUNNING. It reads every page of commits when looking for a package's latest commit.

Example:

ada deploy commit -p DV_SALES
ada deploy promote --to DEV -p DV_SALES
ada deploy start --to DEV --wait

Live metadata search and graphs

• New ada metadata search runs a cross-type search against ADE by name, description, tag, node type or DW zone.

• New ada metadata graph traverses live graphs with er, lineage, packages and workflows.

• ada metadata graph lineage shows a package flow view by default.

• ada metadata graph workflows works in the design environment and with entity seeds.

• ADE API errors are reported the same way across these commands.

Example:

ada metadata search --package-name STG_SALES --query customer
ada metadata graph packages --package-name DV_SALES

Yanked and blocked releases

• ada warns when the installed version has been yanked.

• A blocked version refuses to run any command except ada upgrade.

• Withdrawn releases are listed in versions.yaml and published to the artifact index.

Quieter update notices and a more reliable upgrade

• The update notice appears at most once a day and only in a terminal.

• ada upgrade finishes the skill sync in a fresh process and has shorter output.

• On Windows, the upgrade finishes in a new window.

• Scaffolded agent instructions now say how to handle update, deprecated and blocked notices.

• Wrapped SSL errors now give a clearer message.

Skills

• New ada-metadata-discovery skill finds packages, entities, dependencies and lineage. It works locally with ada metadata index and live with ada metadata search and ada metadata graph.

• New ada-sql skill previews, diffs and reviews the SQL ADE generates, and optionally, runs it on request against a database.

• ada-testing now checks loaded data only. It is reorganized with per-database references for Snowflake and Databricks, and with run and variable references.

• ada-deploy now covers commit, promote, deploy and DAG trigger.

• ada-diagram-generation, ada-pull-metadata, ada-push-metadata and ada-workflow-monitor were updated to match the CLI changes.

5. Maintenance

• Third party dependencies updated.

• A test now fails when the pyproject.toml pins and uv.lock disagree.

• push() and pull() are split into named steps, with a readability test guarding function length and branching.

6. Compatibility

No CLI commands were removed or renamed.

ada code preview now reads local YAML by default. Use --remote for the previous behavior.

ada deploy commit and ada deploy promote no longer trigger ADE's automatic promotion and deployment by default. Add ada deploy start, or set allow_automatic_deployment: true in config/pipeline.yaml, to keep the old flow.

Skills that use the new commands require the matching ada-cli version.