Environment Forking for Flexible Data Source Configuration #4298
pascalwhoop
started this conversation in
Idea
Replies: 4 comments
|
Hi @pascalwhoop, thanks for bringing these suggestion, they seem worthwhile exploring! |
0 replies
|
Turning this into a discussion 🙏🏼 Let's continue the conversation there. |
0 replies
|
About |
0 replies
|
About |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We're considering adding a feature to allow more flexible configuration of data sources across environments. The primary use case is to enable testing part of the pipeline using production data without needing to copy data manually. Thought I'd share here to see if others find this useful as well.
Proposed Features:
Environment Forking Flag:
Example:
kedro run --from-nodes a,b,c --fork-from prod --env devThis would read initial datasets from the 'prod' environment and then execute the rest of the pipeline in the 'dev' environment.
Dataset Copying Command:
Example:
kedro copy --datasets a,b,c --from prod --to devThis would manually copy specified datasets from 'prod' to 'dev' environment before running the pipeline.
Inverse Tag Filtering:
Example:
kedro run --without-tags tag1,tag2This would filter out nodes based on tags, inverse of the existing
--tagsoption.Use Case:
Current Limitations:
Potential Implementation:
Long-term Consideration:
All reactions