Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Adding multi-threaded execution for Update-DbaInstance #4775
Type of Change
Adding multithreaded invocation of SQL Server patches following proper flow.
Moving around pieces of code, improving messaging and using Invoke-Parallel when computer count -ge 2
Commands to test
update-dbainstance computer1,computer2,computerN -path '...' -credential $cred
Handling warnings from inside a runspace'd scriptblock is a pain
Thanks so much for the updates.
can you do the remotehost/credential check earlier on? it essentially takes 15 seconds to tell me that I did something wrong and I'll have to do it all over again.
I believe that last one should be a Stop-Function, especially if you're looking for $_.Message to exist.
Is the failback prompt going to be done later? I forgot what we had talked about.
Also, can you change the wording on that warning? Change
And one more change! I named that column wrong. Can you do Notes instead of Message to align with the rest of our commands?
Without breaking yet another whatif test - only as a warning without stopping a function. Whatif runs do not require credentials. Hope that works.
Fixed - with the exception that it was intended specifically as a warning, since there is no way we're getting there with -EnableExceptions when there are errors - and I don't want the output processing scriptblock to be throwing.
It's not a failback. It's running the command without elevated session, when it tries to configure CredSSP first. I don't want to enforce an elevated session and exit right away, since, theoretically, it might work even without the elevated session. But it's required for setting up a connection to a remote host for the first time. I would rather let it be and let the users know that they are supposed to run it in an elevated session.
The warning actually comes from a cmdlet - I'm just including it into the message.