You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On v0.4.1, constantly prompts for "Akamai CLI is not installed in your PATH, would you like to install it?" even when it is in the PATH. It would be good to also have a way to surpress this check (eg, when "n" is selected or otherwise be able to put a file in ~/.akamai-cli to disable the check).
It would also be good to disable this check entirely if stdin/stdout isn't a tty (ie, if the akamai-cli isn't being used interactively then trying to prompt for anything is problematic.)
The text was updated successfully, but these errors were encountered:
Would you be able to share the path you have it installed in vs your PATH, so we can see why it doesn't think it matches. I suspect it's because you installed it to non-user-writeable path in PATH, and I excluded those from the list of potential places. Will double check this and update the logic.
A suppression mechanism would be good, what do you think of limiting it to the current version only?
Absolutely it shouldn't prompt when stdin/out aren't TTYs, I'll double check on that.
@enygren I believe I was correct about this, and have fixes in for (1) and (3) above, they will be in the next release.
I'm also working on a more comprehensive configuration file that can store information like that needed for (2), which may or may not make the next release.
On v0.4.1, constantly prompts for "Akamai CLI is not installed in your PATH, would you like to install it?" even when it is in the PATH. It would be good to also have a way to surpress this check (eg, when "n" is selected or otherwise be able to put a file in ~/.akamai-cli to disable the check).
It would also be good to disable this check entirely if stdin/stdout isn't a tty (ie, if the akamai-cli isn't being used interactively then trying to prompt for anything is problematic.)
The text was updated successfully, but these errors were encountered: