I am wanting to use docker and integrate it into this vscode extension rather than having to install packages locally.
This eases onboarding and prevents issues with other projects/packages that may be installed on a users computer.
I have this working for manually processing the scripts but it would be ideal if I could modify the config to point to docker instead of a local installation.
{
"cfnLint.path": "docker run -v $(pwd)/:/data -t mysteriouscode/cfn-lint"
}
Currently, if I do try to pass docker, I get an error due to the space after docker. Given that is a path, I would expect this to be the case.
I currently use scripts to do the linting:
{
"scripts": {
"Tools:": "echo \"Nothing to see here\" && exit 1",
" - cfn-lint": "docker run -v $(pwd)/:/data -t mysteriouscode/cfn-lint --config-file /data/.config/cfn-lint/.cfnlintrc.yaml",
"Debug:": "echo \"Nothing to see here\" && exit 1",
" - cfn-lint:version": "docker run -v $(pwd)/:/data -t mysteriouscode/cfn-lint --version"
}
}
I am wanting to use docker and integrate it into this vscode extension rather than having to install packages locally.
This eases onboarding and prevents issues with other projects/packages that may be installed on a users computer.
I have this working for manually processing the scripts but it would be ideal if I could modify the config to point to docker instead of a local installation.
Currently, if I do try to pass docker, I get an error due to the space after
docker
. Given that is a path, I would expect this to be the case.I currently use scripts to do the linting:
Please consider adding this capability. Thank you