I'm using terragrunt with terraform and it creates a lot of copies of *.tf files under .terragrunt-cache folder. Those are then being indexed and consume a lot of CPU as the projects are quite large. How can I exclude the path from being indexed?
there is a setting for that called something like
terraform.indexing.exclude or something like that
On Fri, Apr 12, 2019 at 11:58 AM Khar Tahk notifications@github.com wrote:
I'm using terragrunt with terraform and it creates a lot of copies of *.tf
files under .terragrunt-cache folder. Those are then being indexed and
consume a lot of CPU as the projects are quite large. How can I exclude the
path from being indexed?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mauve/vscode-terraform/issues/169, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGCJGD6DCDGLCO7ZBQZ2PTPQBMLXANCNFSM4HFPCKGA
.
Thank you. I didn't know that copying the json config string in VS Code could hold an array of settings. I've copied indexing and I got the entire object and I the added .terragrunt-cache to be excluded next to .terraform:
"terraform.indexing": {
"enabled": true,
"liveIndexing": true,
"delay": 500,
"exclude": [
".terraform/**/*",
"**/.terraform/**/*",
".terragrunt-cache/**/*",
"**/.terragrunt-cache/**/*"
]
}
It would be nice if all the config options were available in the documentation or it was mentioned you can copy the json object in VS Code settings for the extension :)
No matter what I put in it doesn't exclude anything. Even If I put * it still indexes everything.
This finally worked:
"exclude": [
".terraform/**/*",
"**/.terraform/**/*",
".terragrunt-cache/**/*",
"**/.terragrunt-cache/**/*",
".terragrunt-cache/**/.terraform/**/*",
"**/.terragrunt-cache/**/.terraform/**/*"
]
the **/* glob does not cover .DIR type dirs.
Also
".**/*",
"**/.**/*"
does not work.
which version do you have of the plugin? a recent release fixed a bug
which consumed CPU even for ignored files.
On Mon, Apr 15, 2019 at 3:31 PM Khar Tahk notifications@github.com wrote:
>
No matter what I put in it doesn't exclude anything. Even If I put * it still indexes everything.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
Version 1.3.9
Thanks @khartahk for posting the exclude patterns. That works! Had to add this to a couple of other plugins too. My VSC was running hot whenever I starteed terragrunt.
We just released v2.0.0-rc.1 of the extension. The main features include:
You can find additional information and specifics in the release notes and CHANGELOG.
With this release we expect that many of the prior issues and PRs are no longer relevant or have been addressed, and are therefore being closed. If you feel the action taken on an issue or PR is in error, please comment as such and we can figure out the appropriate way to address it.
We plan to add the final 2.0.0 release to the marketplace soon, but are actively seeking your feedback now on the release candidates. You can download the .vsix from the releases page and manually install it in VS Code to try it out.
I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the context necessary to investigate further.
Most helpful comment
No matter what I put in it doesn't exclude anything. Even If I put
*it still indexes everything.This finally worked:
the
**/*glob does not cover.DIRtype dirs.Also
does not work.