-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distinguish flex flow and dag flow(use flow.flex.yaml for flex flow, flow.dag.yaml for dag flow) #2626
Conversation
promptflow-core test result 12 files 12 suites 2m 59s ⏱️ Results for commit 7baf7ef. ♻️ This comment has been updated with latest results. |
promptflow SDK CLI Azure E2E Test Result chenyzhang/distinguish_flex_and_dag 4 files 4 suites 3m 59s ⏱️ Results for commit 7baf7ef. ♻️ This comment has been updated with latest results. |
SDK CLI Test Result chenyzhang/distinguish_flex_and_dag 12 files 12 suites 48m 39s ⏱️ Results for commit 7baf7ef. ♻️ This comment has been updated with latest results. |
SDK CLI Global Config Test Result chenyzhang/distinguish_flex_and_dag3 tests 3 ✅ 49s ⏱️ Results for commit 7baf7ef. ♻️ This comment has been updated with latest results. |
…to obtain the flow path and flow file. (#2662) # Description Please add an informative description that covers that changes made by the pull request and link all relevant issues. Base this [PR](#2626): Distinguish flex flow and dag flow(use flow.flex.yaml for flex flow, flow.dag.yaml for dag flow), And next [PR](#2548): Migrate the yaml used by the eager flow to flow.flex.yaml, code support both flow.flex.yaml and flow.dag.yaml. To standardize the construction method of flow paths and flow files: 1. Delete **DAG_FILE_NAME** constant and use the **resolve_flow_path** function to obtain the flow path and flow file. 2. Using **FLOW_DAG_YAML** instead of **DAG_FILE_NAME** . # All Promptflow Contribution checklist: - [x] **The pull request does not introduce [breaking changes].** - [ ] **CHANGELOG is updated for new features, bug fixes or other significant changes.** - [ ] **I have read the [contribution guidelines](../CONTRIBUTING.md).** - [ ] **Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: [suggested workflow](../CONTRIBUTING.md#suggested-workflow).** ## General Guidelines and Best Practices - [x] Title of the pull request is clear and informative. - [ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, [see this page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md). ### Testing Guidelines - [ ] Pull request includes test coverage for the included changes.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
It is necessary to distinguish between the flow yaml used by the eager flow and the dag flow (flex yaml and dag yaml), and modify the code to enable the eager flow to use flex yaml correctly and to enable the code to automatically recognize flex yaml and dag flex, which is divided into two steps:
All Promptflow Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines