-
Notifications
You must be signed in to change notification settings - Fork 13
General.ServiceX as an optional field #402
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## 3.0_develop #402 +/- ##
===============================================
+ Coverage 75.01% 75.12% +0.10%
===============================================
Files 30 30
Lines 1421 1423 +2
===============================================
+ Hits 1066 1069 +3
+ Misses 355 354 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Coming back to an earlier discussion - should this just be an argument to |
I thought that's for experts - who have multiple endpoints. I expect normal users download I am happy to add an optional argument in the to to pick up the endpoint from |
|
Right, the idea was that if the endpoint is an argument to |
| backend = self.config.default_endpoint | ||
| else: | ||
| # Take the first endpoint from servicex.yaml if default_endpoint is not set | ||
| backend = self.config.api_endpoints[0].name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the config file guaranteed, via the parsing code, to have an endpoint?
General.ServiceXas an optional field to further minimize boilerplateGeneralblock can be omitted fromServiceXSpecand onlySampleblock is requiredGeneral.ServiceXvalue is taken from thedefault_endpointif present in theservicex.yaml. Otherwise the first endpoint is taken. (Assuming normal users have one endpoint)