-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scans all yaml files with cfn-lint at startup. #198
Comments
The default configuration, if the VS Code docs are correct, is that it will only scan on files being open. Do you have a .cfnlintrc file? |
No, I don't have .cfnlintrc file in the workspace or my home dir. |
I am running into this issue as well and dont have a cfnlintrc either. Is there some way to only limit the behavior of this plugin to only evaluate the open file? |
also running into this issue, which causes 100% ram utilization since cfn-lint runs for 100+ templates. |
Issue Type: Bug
I have a couple of hundred cloudformation templates and serverless templates in my default workspace.
Every time I start or reload vscode it scans all the yaml files with cfn-lint.
It pushes to load average up to approx 200, until the WSL stops responding and disconnects.
Then reconnecting it does it again. Rinse, repeat.
I've had to start running
multiple times in a terminal session when vscode or my machine reloads to keep it under control.
Is there a way to add a setting, to only lint files on open, rather than scan the whole workspace on load?
Extension version: 0.20.0
VS Code version: Code - Insiders 1.61.0-insider (aec6ee09fa1021cb59c7f4f4d000b027febc967d, 2021-09-03T05:14:10.486Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Remote OS version: Linux x64 5.10.43.3-microsoft-standard-WSL2
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
A/B Experiments
The text was updated successfully, but these errors were encountered: