[Feature] Add new global flag `--no-write-manifest`
- Dominant language
- Rust
- Stars
- 13.8k
- Forks
- 2.6k
- Avg merge
- 21h 31m
- Merged PRs (30d)
- 56
Description
### Is this your first time submitting a feature request?
- [X] I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
- [X] I have searched the existing issues, and I could not find an existing issue for this feature
- [X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion
### Describe the feature
When running `dbt build` commands in Airflow in parallel, Stale File Handle error messages appear in the logs, the reason for this is the overwriting of `manifest.json` for each `dbt build` run
I would like to be able to disable the manifest rewrite when running the `dbt build` command and use the generated manifest at the beginning when running the `dbt parse` command.
[`--no-write-json`](https://docs.getdbt.com/reference/global-configs/json-artifacts#write-json-artifacts) is not suitable for this, because I want to get [`run_results.json`](https://docs.getdbt.com/reference/artifacts/run-results-json) for future use in Datahub or Elementary
### Describe alternatives you've considered
_No response_
### Who will this benefit?
Users of [DBT Programmatic Invocation](https://docs.getdbt.com/reference/programmatic-invocations)
### Are you interested in contributing this feature?
_No response_
### Anything else?
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.