Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: obs_base
-
Labels:
-
Team:Data Access and Database
-
Urgent?:No
Description
I’m getting no files ingested when I run butler ingest-raws, and lots of warnings. It is not obvious, short of reading the code, that adding -c failFast=True allows me to find where the problem is occurring. There is no equivalent of the old --show config mentioned in the --help.
Tim Jenness suggests (and I agree) that something like butler ingest-raws --fail-fast would be a better interface for this particular case, but I'm also concerned about the general problem of the user needing to know about any configuration parameters for the other butler sub-commands.
Attachments
Activity
Paul Price
created issue -
| Field | Original Value | New Value |
|---|---|---|
| Component/s | obs_base [ 10719 ] | |
| Component/s | daf_butler [ 11300 ] |
| Labels | gen3-middleware |
| Summary | Butler task config parameters not accessible from command-line | Butler ingest-raws config parameters not accessible from command-line |
| Team | Architecture [ 10304 ] |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Reviewers | Tim Jenness [ tjenness ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
Thanks. Looks okay.
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Assignee | Nate Pease [ npease ] |
| Team | Architecture [ 10304 ] | Data Access and Database [ 10204 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
It's always a bit tricky to work out how much should come from configuration and how much should come from command line. When we are only talking about a handful of config parameters then a command line equivalent seems like the best approach. Command line supports the -@ option as well. I would guess that a config user is someone who is running the task itself.