Skip to content
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

Consider command line arguments #10

Closed
thbar opened this issue Jun 7, 2015 · 3 comments
Closed

Consider command line arguments #10

thbar opened this issue Jun 7, 2015 · 3 comments

Comments

@thbar
Copy link
Owner

thbar commented Jun 7, 2015

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.

@eduardodeoh
Copy link

👍

@thbar
Copy link
Owner Author

thbar commented Nov 14, 2016

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.

@thbar thbar closed this as completed Nov 14, 2016
@thbar
Copy link
Owner Author

thbar commented Jan 23, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants