ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #powershell
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
I had a script that needed to run as an administrator but then run a single command in a non-elevated context. I was previously doing it with runas /trustlevel:0x20000 program.exe , but after updating Windows 11 to 22H2 the command now gives the following output (running Notepad here as an example): PS > runas /trustlevel:0x20000 notepad RUNAS ERROR: Unab
Goal: Use PowerShell’s built‑in transaction cmdlets to automatically roll back database schema changes when an error occurs during a script. Constraint: The SqlServer provider does not implement ITransactionSupport , so Start-Transaction does not enlist Invoke-Sqlcmd statements; any SQL executed outside an explicit SqlTransaction is committed immediately and
I am trying to use PowerShell Graph cmdlets instead of the Azure AD module cmdlets. With the Azure AD module, I can do this: # This is what I want: get-azureadgroupmember -objectid $GroupID | select-object -property displayname, ` mail, userprincipalname, objectid DisplayName Mail UserPrincipalName ObjectId ----------- ---- ----------------- -------- John Sm
Background jobs created with Start-Job remain in the session until Remove-Job is called, even after completion. This behavior can lead to elevated memory consumption in long‑running scripts. In PowerShell 7.2 a known bug caused job objects to stay in memory after Remove-Job , resulting in a measurable leak; the issue was fixed in 7.3 and later releases. Howe
I'm beginning to build out a kubernetes cluster for our applications. We are using Azure for cloud services, so my K8s cluster is built using AKS. The AKs cluster was created using the portal interface for Azure. It has one node, and I am attempting to create a pod with a single container to deploy to the node. Where I am stuck currently is trying to connect
commented · 06 May 2025, 18:47 UTC
answered · 12 Dec 2024, 09:04 UTC
azure
kubernetes