-
Notifications
You must be signed in to change notification settings - Fork 888
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
[Executor] Support passing connection provider to script executor #3004
[Executor] Support passing connection provider to script executor #3004
Conversation
promptflow SDK CLI Azure E2E Test Result dev/linatang/support-connection-provider-in-script-executor 4 files 4 suites 4m 7s ⏱️ Results for commit 0b007f2. ♻️ This comment has been updated with latest results. |
promptflow-core test result0 tests 0 ✅ 0s ⏱️ Results for commit 0b007f2. ♻️ This comment has been updated with latest results. |
SDK CLI Global Config Test Result dev/linatang/support-connection-provider-in-script-executor6 tests 6 ✅ 1m 22s ⏱️ Results for commit 0b007f2. ♻️ This comment has been updated with latest results. |
Executor Unit Test Result dev/linatang/support-connection-provider-in-script-executor792 tests 792 ✅ 3m 44s ⏱️ Results for commit 0b007f2. ♻️ This comment has been updated with latest results. |
Executor E2E Test Result dev/linatang/support-connection-provider-in-script-executor242 tests 237 ✅ 5m 12s ⏱️ Results for commit 0b007f2. ♻️ This comment has been updated with latest results. |
SDK CLI Test Result dev/linatang/support-connection-provider-in-script-executor 4 files 4 suites 59m 7s ⏱️ Results for commit 0b007f2. ♻️ This comment has been updated with latest results. |
976ae5b
to
9abfbe0
Compare
9abfbe0
to
1169daf
Compare
) # Description Currently we use `ConnectionProvider.get_instance` to get connections in script executor, and it doesn't support passing connections to it directly, while the flow executor can accept connections, which is inconsistent. For flow serving, we want the behaviors to be consistent to refine the conenction resolving logic, so in this PR, we support directly passing connections to script executor. # 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.** - [x] **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. - [x] 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 - [x] Pull request includes test coverage for the included changes. Co-authored-by: Lina Tang <[email protected]>
Description
Currently we use
ConnectionProvider.get_instance
to get connections in script executor, and it doesn't support passing connections to it directly, while the flow executor can accept connections, which is inconsistent. For flow serving, we want the behaviors to be consistent to refine the conenction resolving logic, so in this PR, we support directly passing connections to script executor.All Promptflow Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines