Craig McNicholas

Resurrecting this one, is there anything I can do as an investigation to help support moving this on? With serverless 4, the default is going to be set to "error"...

This currently means deciding between localstack or serverless-domain-manager, both really powerful tools but localstack is giving me test assurance. Would love to see this working together. Is there any work...

any discussions or future plans for this from serverless, serverless-offline ? this is really a deal breaker for using other common serverless plugins like lift as it makes it impossible...

I'm experiencing the same thing, did you resolve this?

I've just got v7 alpha 54 working and this is still an issue, it creates a bad developer experience as it's not immediately apparent why this broke my monorepo setup.

Just opened this https://github.com/nuxt/nuxt/issues/23609 but I believe this may be the same issue? Happy to close if it is to avoid duplicates.

> After clone I was running `npm install` and I got this error: > > ``` > npm ERR! ERESOLVE could not resolve > npm ERR! > npm ERR! While...

is there any major blocker here just supporting passthrough for cli args that aren't supported 1st class by compose? it seems that the additional comments raised that cause concern are...

> > What would be the use case? > > A common pattern, usually called "fanout", is to subscribe SQS queues to SNS topics. AWS documentation has a basic example...

I've had a stab at implementing this, see #344 I would appreciate any help simplifying or helping to resolve the issue about having to use ARN strings instead of Refs.