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

Select alias in PSSQLite.psm1 #13

Open
evetsleep opened this issue Apr 16, 2017 · 2 comments
Open

Select alias in PSSQLite.psm1 #13

evetsleep opened this issue Apr 16, 2017 · 2 comments

Comments

@evetsleep
Copy link
Contributor

evetsleep commented Apr 16, 2017

This is kind of an odd one and I can fork and fix if you want, but in the PSSQLite.psm1 file you're using the alias for Select-Object as part of the function export process (at the end). Under normal circumstances this is totally ok, however I've been banging my head over the last few days trying to figure out why I can't get the PSSQLite module to work as part of a constrained endpoint (JEA) and after doing a lot of debugging the use of the Select alias is not playing nice with a locked down endpoint\shell (SessionType='Empty' and LanguageMode='RestrictedLanguage'). I tried defining Select as a valid alias with VisibleAliases but the only way I could get it to work is if I edited the module and spelled out the alias as Select-Object.

So anyway we can get the Select alias removed and the full cmdlet name put int the PSSQLite module file? I can do it if you want, but it seems like a really small change :)

@RamblingCookieMonster
Copy link
Owner

Must have missed this! Sure, makes sense to me, would gladly take a PR : ) I should probably start adding psscriptanalyzer gating for particular rules to avoid cases like this

Thanks!

@evetsleep
Copy link
Contributor Author

evetsleep commented May 9, 2017 via email

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

No branches or pull requests

2 participants