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

Command Line Configuration #16

Open
devyntk opened this issue Dec 7, 2018 · 3 comments
Open

Command Line Configuration #16

devyntk opened this issue Dec 7, 2018 · 3 comments

Comments

@devyntk
Copy link
Collaborator

devyntk commented Dec 7, 2018

I'd love some command line (or config file) configuration to be able to done, at least for the API key and event ID, and preferably scoring system IP.

@Techno11
Copy link
Contributor

Arguments:
-skip-config : Skip Dialog asking for config file
-event-key=<toa_event_key> : TOA Event Key
-api-key=<toa_api_key> : TOA API Key
-scoring-ip=<scoring_ip> : IP address for scoring system
-scoring-event=<first_event_key> : Event Key from FIRST scoring system
-test-toa : attempt connection to TOA with given credentials
-test-first : attempt connection to Scoring System with given data
-load-first : attempt to load event from FIRST provided the IP was correct

@jvens
Copy link
Contributor

jvens commented Oct 13, 2019

I can probably take on this feature over the next few days (I really want this feature). It looks like the suggested arguments were specific to the old datasync tool and I am not sure if they are all relevant here. Also, since you are now using firebase credentials rather than API keys I am not sure the best way to handle that. If anyone has an idea how to handle this problem I would gladly hear it. If there is no better idea I'll just have -username and -password flags, but that feels wrong for some reason.

Flags I am thinking:

  • -config=<config.json>: provide a config file that would have all these flags as fields
  • -event-key=<toa_event_key>: the TOA Event Key
  • -scoring-ip=<scoring_ip>: IP address of the score system
  • -scoring-event=<first_event_key>: Event Key from the FIRST scoring system
  • -username=<username>: TOA username
  • -password=<password>: TOA password

If anyone disputes any of these flags or would like additional flags let me know.

@jvens
Copy link
Contributor

jvens commented Nov 7, 2019

Now that it is web-based this should either be closed or changed in scope to be an uploaded config file instead of command line arguments. Unless you want to pass them in as a query string which seems not very useful to me personally, and I refuse to pass a password as a query string since that is human readable to anyone watching network traffic.

@ofekashery ofekashery unpinned this issue Nov 7, 2019
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

4 participants