Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upHow to disable/ignore update warning when calling Lando from scripts? #1000
Comments
This comment has been minimized.
This comment has been minimized.
@dsnopek at this point, nope, we don't have a way to disable this message without updating the project. Your use case is yet another indication that we need to look at cleaning up the output in some way though I think the problem with pushing to stderr might be that CI processes etc might fail if there is output in stderr? I might be wrong on that. |
This comment has been minimized.
This comment has been minimized.
I'm not aware of a CI platform that fails just because there's something output on stderr, most usually look at the exit code, but if there was such a CI platform you could just redirect stderr somewhere, for example:
|
This comment has been minimized.
This comment has been minimized.
You're probably right, my fear was likely unneeded I like the idea of dumping it to stderr as a way of seperating the output but pretty much always making sure it shows up (the main reason there really isn't a way to turn it off). |
pirog
referenced this issue
Jan 13, 2019
Closed
Don't prompt for latest version for every command #1077
pirog
self-assigned this
Jan 23, 2019
pirog
added this to the 3.0.0-rc.2 milestone
Jan 23, 2019
This comment has been minimized.
This comment has been minimized.
This has been changed in forthcoming RC2. The update warning will now be sent to |
pirog
closed this
Jan 23, 2019
added a commit
that referenced
this issue
Jan 23, 2019
This comment has been minimized.
This comment has been minimized.
Awesome, thanks! |
dsnopek commentedMay 28, 2018
So, we have a bunch of scripts that call
lando
and parse it's output, for example:lando info
lando drush pm-list --format=json
However, when there's a new Lando update available, the update message gets put before the JSON and breaks parsing.
Is there a way to disable the warning entirely when running from a script? Or, if the message was output on stderr, then it could still be shown, but the stdout will be clean, parseable JSON.
Just encoutered this again because there was just a release a little bit ago :-)