We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Update the flag value --elv2-license "accept" to accept also the values "yes"/"Yes"/"Y"/"y"; e.g. --elv2-license "yes"
--elv2-license "accept"
"yes"/"Yes"/"Y"/"y"
--elv2-license "yes"
This will provide more intuitive values for most end-users instead of just "accept".
Also, it will still be a satisfactory legal answer to the question, "Do you accept the license agreement of the ELv2 license?"
"Do you accept the license agreement of the ELv2 license?"
When that is implemented, these docs need to be updated with this change:
Related issues:
rover supergraph compose command fails to prompt for license #1455
Use Boolean instead of string for accepting the License agreement #2293
Related Code: https://github.com/apollographql/rover/blob/6699487c2cae5493bb4ebd93a715a3d53b60ef0f/src/options/license.rs#L77C1-L83C2
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Update the flag value
--elv2-license "accept"
to accept also the values"yes"/"Yes"/"Y"/"y"
;e.g.
--elv2-license "yes"
This will provide more intuitive values for most end-users instead of just "accept".
Also, it will still be a satisfactory legal answer to the question,
"Do you accept the license agreement of the ELv2 license?"
When that is implemented, these docs need to be updated with this change:
Related issues:
rover supergraph compose command fails to prompt for license #1455
Use Boolean instead of string for accepting the License agreement #2293
Related Code:
https://github.com/apollographql/rover/blob/6699487c2cae5493bb4ebd93a715a3d53b60ef0f/src/options/license.rs#L77C1-L83C2
The text was updated successfully, but these errors were encountered: