Shawn Melton

Removed pulling all logins and the test alone dropped more than half the time to run  Also adding more granular WhatIf so folks can see what actually gets changed....

@potatoqualitee do you intend to implement this in the library? @kjustin765 this particular one requires changes to our C# codebase in another repository (dbatools.library). That particular repository we are not...

Appreciate the offer but I can work on this issue.

We utilize T-SQL queries in gathering these details so at this time that is not something we can support as the stored procedures in SQL Server do not support returning...

Always happening since I started using an Apple device (M1), switched to this month ago. I can't recall if Windows device gives me this issue...I can test that shortly. Extension...

So I cannot replicate this on Windows (Windows 10, VS Code Insiders, PowerShell 7.2, and `v2023.9.1`).

I'll grab diagnostic logs for the windows device I used tomorrow and upload them.

There is no PSSA settings file in the referenced project We have this in most of the project's settings.json file: ` "powershell.scriptAnalysis.settingsPath": "./ScriptAnalyzerSettings.psd1"`

So seems after updates (whether the extension pre-release or VS Code Insiders) I no longer see this issue. At least the steps I have written no longer show any errors.

I'm using the pre-release `v2023.9.4` and beginning to see this again.