Using Serverless 2.x, is it possible for me to disable provisioned concurrency in same stages and enable it in others? If i set provisionedConcurrency: 0 for a function, then I get a warning in the CLI that says “[…] should be >= 1”.
I have actually found the solution myself and will write it here in case others need it in the future:
Setting the value to null in some stages simply disables Serverless from adding provisioned concurrency.
2 Likes
Would you mind helping out - I’d love to know what you have done? Please take a look at my post Disabled provision concurrency for Development Stage
I have not been able to get ~ or null or 0 to work