Open joshsleeper opened 1 year ago
Hi @joshsleeper. Thanks for the suggestion. It would be super helpful if you could explain why this scenario came up.
I'm a little concerned about complexity here. We can detect pulumi
only if it is on $PATH
while we install, and that might not be the version users are using.
so in my head I'd think that check is very likely to succeed, but easy to fallback to current behavior if it fails?
pulumi
is already installing to a known, well-documented place
~/.pulumi/bin
as per the docs: https://www.pulumi.com/docs/get-started/install/pulumi
isn't on the path for some reason, I'd think that checking that known (and about to be overwritten anyway) path for the current binary is sanepulumi
can't be found either on the path or by absolute path, I'd just continue as normalas for the reasoning, it's mostly just the "don't do work you don't need to do" mentality~ less bandwidth usage + I/O for both hosting and users, and a faster update experience for users that are already updated.
Thanks for the quick feedback. I'm not sure when we will have bandwidth to address this, but I'm convinced that it would be an improvement.
+1 really need this
Hello!
Issue details
it'd be nice if the install scripts could detect that the currently installed
pulumi
version is already the latest and short-circuit the download + install processAffected area/feature
get.pulumi.com
install scripts