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

Linux install constantly prompts for "install in path #27

Closed
enygren opened this issue Nov 6, 2017 · 3 comments
Closed

Linux install constantly prompts for "install in path #27

enygren opened this issue Nov 6, 2017 · 3 comments

Comments

@enygren
Copy link

enygren commented Nov 6, 2017

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.)

@dshafik
Copy link
Contributor

dshafik commented Nov 6, 2017

@enygren obviously there's a bug here!

  1. 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.
  2. A suppression mechanism would be good, what do you think of limiting it to the current version only?
  3. Absolutely it shouldn't prompt when stdin/out aren't TTYs, I'll double check on that.

@dshafik
Copy link
Contributor

dshafik commented Nov 21, 2017

@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.

I'll update this issue when those fixes go out.

@dshafik
Copy link
Contributor

dshafik commented Feb 5, 2018

This issue will be fixed in the 0.5.0 release.

@dshafik dshafik closed this as completed Feb 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants