Accessible dbt code in error messages

[Auric-Manteo]

What's the use case?

Currently, the dbt errors show the path to the failed sql code, but that is not accessible if you don't have access to the relevant infrastructure and even then it might get removed eventually due to the infrastructure cleaning up old resources.
Instead it would be great if the path would link to the file and that the file contents is accessible.
So in the example screenshot it would be great if we could access unique_hourly_salesforce_account_of_account_id__c.sql so I can see the code and run it directly to figure out and fix the issue.

Ideas of implementation

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.

[garethbrickman]

It is possible to log the compiled SQL for both dbt tests and models into the run logs via the ​​run­­_results.json file​​. ­See this code example here which uses DbtCliInvocation. get­_artifact.

    # fetch run_results.json to log compiled SQL
    run_results_json = dbt_cli_task.get_artifact("run_results.json")
    for result in run_results_json["results"]:
        model_name = result.get("unique_id")
        context.log.info(f"Compiled SQL for {model_name}:\n{result['compiled_code']}")

[Auric-Manteo]

Great, I'll look into that!
Any idea on how you could catch the error and get the name of the failed test to get only their code? There are a lot of them, so listing them all is not a good solution.