Faster --update-specs
See original GitHub issuecfn-lint version: 0.25.5
Right now, cfn-lint --update-specs
doesn’t really do any checking to see if the existing specs are up to date and naively patches all of them. It would be beneficial to have some sort of local checksum which would prevent this, to increase overall speed when there are no updates.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Update weight - Strava - IFTTT
This Action will update your weight on Strava. API endpoint slug: strava.update_weight; Filter code method: Strava.updateWeight.skip(string?: reason); Runtime ...
Read more >Iqoo 3 New Update,specs,camera,| Android 12 update | Best Hidden ...
hello dosto in this video we talk about iqoo 3 new top hidden feature after Android 12 update.
Read more >Mac Mini Update Specs? | MacRumors Forums
Think Secret claims to have information on the rumored revision to the Mac Mini. According to the site, Apple will replace the existing...
Read more >Graphical update specs? : r/ffxivdiscussion - Reddit
Hi! I love FF14 and play on an older laptop with the graphic settings set medium to low. I know SE hasn't announced...
Read more >Lamborghini Gallardo LP560-4 (Update) - Specs & Performance
Lamborghini Gallardo LP560-4 (Update) – Specs & Performance ; price £/td>, £164,444 ; engine, 90° V10. w/Dry Sump Lubrication ; position, Mid, Longitudinal....
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 Free
Top 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
I am not using cfn-lint as part of any CI/CD flow, and nor do I necessarily need to check if my templates work across all regions. My main use cases are for assisting manual dev effort, and ensuring basic compatibility with all of the eu-* regions and us-east-1.
For context, slow updates don’t cause me any pain. I worked on this PR simply because it was something to do on a weekend, and it seemed more interesting than writing a couple of additional rules.
Not run by customers like
--update-specs
, but I’d love forscripts/update_specs_from_pricing.py
to be faster as well