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

Jump to bottom

Add argument to bypass the experimental disclaimer prompt #2340

Closed
2 tasks
LefterisJP opened this issue Sep 3, 2018 · 0 comments
Closed
2 tasks

Add argument to bypass the experimental disclaimer prompt #2340

LefterisJP opened this issue Sep 3, 2018 · 0 comments
Assignees
@LefterisJP
Milestone
Red Eyes Testnet 8

Comments

@LefterisJP
Copy link
Contributor

Problem Definition

After #2285 we introduced an acknowledgement of the experimental software disclaimer.

Many people will want to run raiden inside automated scripts or have it managed by an external process. Having a non-bypassable prompt like we do now may make it impossible for them to do it.

Task

  • Evaluate if adding an argument to bypass the disclaimer is okay
  • If that is fine, add an --accept-disclaimer argument which would skip the [y/N] prompt.
@LefterisJP LefterisJP self-assigned this Sep 3, 2018
@LefterisJP LefterisJP added this to the Red Eyes Testnet 8 milestone Sep 3, 2018
LefterisJP added a commit to LefterisJP/raiden that referenced this issue Sep 3, 2018
@LefterisJP
Add --accept-disclaimer argument
3c31b20 
Fix raiden-network#2340
LefterisJP added a commit to LefterisJP/raiden that referenced this issue Sep 4, 2018
@LefterisJP
Add --accept-disclaimer argument
c031c5e 
Fix raiden-network#2340
@LefterisJP LefterisJP mentioned this issue Sep 4, 2018
Merged
LefterisJP added a commit that referenced this issue Sep 4, 2018
@LefterisJP
Add --accept-disclaimer argument
5b79ed3 
Fix #2340
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@LefterisJP LefterisJP

Labels
None yet
Projects
None yet
Milestone
Red Eyes Testnet 8
Development

No branches or pull requests
1 participant
@LefterisJP