Unable to specify warmup for specified stage
See original GitHub issueServerless.yml
provider:
stage: ${file(${opt:variables}):stage}
name: aws
#other configurations & functions
custom:
warmup:
schedule: 'cron(0/5 * * * ? *)' # Run every 5 minutes
enabled:
- production
The lambdas are deployed under different accounts - stages - and there’s the need to restrict warming of them to one tier. Using the above configuration fails. It might be possibly related to #100.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Intermittant issue with app service slot autoswaps and warmup
I'm attempting to setup a warmup and I'm running into the same error. Based on our app insights logs, I believe it's failing...
Read more >Azure webapi warmup - Stack Overflow
Let me answer your questions one by one: 1: custom warm-up has to be enabled for the swap to call root (or any...
Read more >How to warm up Azure Web App during deployment slots swap
First let's create a site and a staging deployment slot: Next let's set some slot settings on the App and its staging slot....
Read more >What is a Warm Up? - StretchCoach.com
It is for this reason that static stretching is conducted early in the warm-up procedure and is always followed by sports specific drills...
Read more >Configuring Warmup Requests to Improve Performance
With warmup requests enabled, App Engine issues GET requests to /_ah/warmup . You can implement handlers for this request to perform application-specific ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @drexler,
The readme is correct, the problem is that we haven’t released yet so NPM is serving you an older version. If you see the readme on NPM, you’ll see that it looks a bit different than in GitHub and actually shows the
default
option.As general advice, check always the NPM readme better than the GitHub one, since they might be out of sync (like in this case).
Does that make sense?
Just FYI, everything is released now.