marc/ale
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
This repository has been archived on 2024-07-19. You can view files and clone it, but cannot push or open issues or pull requests.
ale/test/handler/test_terraform_handler.vader

62 lines
1.7 KiB
Text
Raw Normal View History

Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
Before:
" Load the file which defines the linter.
runtime ale_linters/terraform/terraform.vim
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
call ale#test#SetDirectory('/testplugin/test/terraform_files')
call ale#test#SetFilename('providers.tf')
Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
After:
" Unload all linters again.
call ale#linter#Reset()
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
call ale#test#RestoreDirectory()
Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
Execute(The output should be correct):
AssertEqual
\ [
\ {
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
\ 'lnum': 17,
\ 'col': 13,
Fix tests on windows
2021-01-30 09:17:28 +00:00
\ 'filename': ale#path#Simplify(g:dir . '/providers.tf'),
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
\ 'type': 'W',
\ 'text': 'Terraform 0.13 and earlier allowed provider version',
Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
\ },
\ {
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
\ 'lnum': 0,
\ 'col': 0,
Fix tests on windows
2021-01-30 09:17:28 +00:00
\ 'filename': ale#path#Simplify(g:dir . '/providers.tf'),
Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
\ 'type': 'E',
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
\ 'text': 'Plugin reinitialization required. Please run "terraform"',
\ }
Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
\ ],
\ ale_linters#terraform#terraform#Handle(bufnr(''), [
Fix 2726 - fix terraform linter. Instead of using `terraform fmt` for linting use `terraform validate` with json output.
2021-01-30 08:11:12 +00:00
\ '{',
\ '"valid": false,',
\ '"error_count": 1,',
\ '"warning_count": 1,',
\ '"diagnostics": [',
\ ' {',
\ ' "severity": "warning",',
\ ' "summary": "Version constraints inside provider configuration blocks are deprecated",',
\ ' "detail": "Terraform 0.13 and earlier allowed provider version",',
\ ' "range": {',
\ ' "filename": "providers.tf",',
\ ' "start": {',
\ ' "line": 17,',
\ ' "column": 13,',
\ ' "byte": 669',
\ ' },',
\ ' "end": {',
\ ' "line": 17,',
\ ' "column": 24,',
\ ' "byte": 680',
\ ' }',
\ ' }',
\ ' },',
\ ' {',
\ ' "severity": "error",',
\ ' "summary": "Could not load plugin",',
\ ' "detail": "Plugin reinitialization required. Please run \"terraform\""',
\ ' }',
\ ' ]',
\ '}',
Add a terraform linter This linter uses the check functionality built into terraform. ALE already has a fixer using `terraform fmt` but this doesn't provide error messages. ALE already has a linter using `tflint` but this requires an extra application to be installed. For example this linter will give a warning that ! is an illegal character in the line below: variable "example" !{} This linter runs the buffer through the command below and parses the output: terraform fmt -no-color -check=true - This commit includes a basic implementation, documentation and tests. The only option is to control which executable is run. Tested with: $ terraform -version Terraform v0.11.13
2019-05-23 13:12:36 +00:00
\ ])
Reference in a new issue Copy permalink