Dariel Marlow

I too am interested in this. I'd like to have things data-driven so as to be able to change things dynamically without having to re-deploy. Any suggestions for best practice...

Let's say I have two endpoints (A and B) and two clients "Bob" and "Alice". How do I saw "Bob" can call endpoint "A" at a rate of 30 times...

As far as I understand it's these stored procedures that need to be invoked, correct? https://github.com/marcingminski/sqlwatch/blob/beta4/SQLWATCHDB/Script.PostDeployment1.sql#L797-L801 I'm less concerned about running the SPs from outside of SQL than I am...

How would we know which parameters are meant for which tasks if more than one task is allowed? I guess maybe pass the same parameters to both tasks? I'll need...

My scripts have become far less than ideal because I try to avoid using properties for arguments. I end up creating tasks that are very specific. For example: ``` Task...

I did some minor hacking and was able to get parameters hooked up. Here's the task: ``` Task PTest { param($p1, $p2, $p3, $p4) "p1 is $p1" "p2 is $p2"...

I too am interested. I tried debugging and got a strange error in VS: ``` 1>Target DockerCreateComposeVsGeneratedFiles: 1> C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\Sdks\Microsoft.Docker.Sdk\build\Microsoft.VisualStudio.Docker.Compose.targets(281,5): error : (Line: 5, Col: 12, Idx:...

I'm also experiencing this issue. Seems like it's something that started happening recently, maybe in the past few weeks.