Skip to content

Support for caching outside of $env:temp #30

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

Closed
jwmoss opened this issue Feb 17, 2021 · 3 comments
Closed

Support for caching outside of $env:temp #30

jwmoss opened this issue Feb 17, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@jwmoss
Copy link

jwmoss commented Feb 17, 2021

Describe the solution you'd like
In our environment, we have security requirements that block .exe files from being ran from $env:temp

Describe alternatives you've considered
I've did a find/replace for all $env:temp with $env:userprofile and I'm still running into issues.

Additional context
NA.

@jwmoss jwmoss added the enhancement New feature or request label Feb 17, 2021
@jantari
Copy link
Owner

jantari commented Feb 20, 2021

That makes sense, I went with $env:TEMP initially because they are temp files so it does make sense to store them there,
but I did not consider AppLocker policies etc.

Coincidentally though I've already been working on making this path configurable in preparation for implementing offline/custom repository support (issue #17), so this will likely be fixed in the next release - soon (tm)

@jwmoss
Copy link
Author

jwmoss commented Feb 20, 2021

Perfect, then that's another vote for me for me for Issue #17 that would solve this.

@jantari
Copy link
Owner

jantari commented Feb 28, 2021

Version 1.2.3, which includes this fix, just released 🎉

You can use the new, optional -ScratchDirectory parameter of Get-LSUpdate to set a custom path for these temp files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants