[DRC-721] [Feature] support a different path for the production manifest

[noel]

Describe the feature

Today Recce expects the production manifest to be at target-base/ I would like to pass a different location for the manifest. Ideally there would be a parameter like --base-manifest-path where I can pass a different location.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

_DRC-721

[popcornylu]

Thank you for your suggestion.

In dbt, a similar option is --target-path, so we may lean towards using --target-base-path for consistency with other dbt commands. Additionally, this path doesn't just include the manifest, but also other artifacts like the catalog.

[noel]

Actually Dbt flag for this is —state

[popcornylu]

Yes, thanks for the reminder. Indeed, the closest equivalent in dbt is --state, and we do use a mechanism like -s state:modified to determine modified nodes.

However, in the context of Recce, --state might conflict with specifying a state file. We are considering options like --state, --dbt-state, and --target-base-path to choose the most suitable one.

[popcornylu]

Decide to use --target-base-path, and we will implement --target-path as well.

[noel]

Great. Thanks On Oct 1, 2024, at 7:07 PM, popcornylu ***@***.***> wrote: Decide to use --target-base-path, and we will implement --target-path as well. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>