Ryan Idrogo

> My issue was not this issue but rather [that other](https://github.com/microsoft/vscode-remote-release/issues/6997) alleged "duplicate" which, for some reason, got closed. > > Good news: [This](https://github.com/microsoft/vscode-remote-release/issues/6997#issuecomment-1310030863) absolutely works! > > ``` >...

Workaround for anyone interested: ``` (this.cluster as any).autoscalingGroup = this.autoScalingGroup; ```

As a hack (since I know that `newInstancesProtectedFromScaleIn: true` is set on my ASG), I tried: ``` (this.autoScalingGroup as AutoScalingGroup).protectNewInstancesFromScaleIn = () => ({}); ``` But actually adding the `AsgCapacityProvider`...

> I cannot think of any reasonable output that can support every use case of such function. I know I haven't thought about it as much as I'm sure you...

> > I would like this even more on a file level: > > ```js > > test.describe.configure({ workers: 1 }); > > ``` > > > > > >...

Hi Siren team, we're looking to start playing with this branch and since it has been a month without accepting the pull request, is there a reason/call out for why...

> Can confirm this on a clean install on MacOS Sonoma 14.3.1 with an M1 (not that any of that really matters for the ESM error). This seems worth fixing...

Looks like it's a positional argument not a named one, so shouldn't be a breaking change? (unless this is some breaking change quirk of JSII?)

Rather than us needing to build our own warmers can Amplify just expose the lambda config so we can provide a `ProvisionedConcurrency` configuration. It would be more $$ in AWS...