You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing this a lot on the field on ETL projects using command line, and so far ENV variables have always worked perfectly (or that + yml files for more elaborated needs). I'll close for now.
Kiba v2 is out and officially supports a programmatic API allowing to issue calls from Rake, Sidekiq etc.
Because of this, I think there is no need anymore to handle command line arguments in a specific fashion, as one can easily implement their custom CLI.
Just creating an issue for now: I want to take the time to think this through.
The current way to pass arguments to tweak the settings of a given script is via
ENV['']
variables.Another possibility would be to add args passing in the
kiba
CLI itself, like @bcherrington did in 97758bb and ca5240a.I must also document this in all cases, since this is a fairly standard need.
The text was updated successfully, but these errors were encountered: