dbt-artifacts-status

Check dbt artifact readiness by inspecting manifest.json and run_results.json in your resolved target directory. This gating step verifies essential files exist and prevents downstream dbt-tools commands from failing due to missing data or incomplete runs.

Gating dbt workflows requires manifest.json and run_results.json in the target directory. Optionally, catalog.json and sources.json can be inspected to provide a more comprehensive readiness state before running graph, summary, or run-report commands.

Prevent dbt-tools failures in CI by adding an artifact readiness check before executing analyses. Evaluating manifest.json and run_results.json ensures incomplete runs or missing data do not cause unexpected errors during automated pipeline execution.

Yes, the dbt artifact check requires a valid --dbt-target directory or an equivalent environment configuration. It resolves this path to locate manifest.json and run_results.json, emitting structured outputs like target_dir to guide downstream steps.

The check emits a structured readiness state including manifest.path, run_results.path, and target_dir. These outputs guide downstream dbt-tools commands by confirming artifact presence and providing clear paths for recovery from missing file errors.

Yes, you can use artifact gating for new dbt workspace setup. Confirming that manifest.json and run_results.json exist before running dbt-tools analyses avoids initial failures, making it highly applicable for safely onboarding new project environments.