3 ms·

If you're doing Puppet then the plugin for IntelliJ works pretty well with Puppet code, including reference checks and all the good stuff you'd expect from a ha

If you're doing Puppet then the plugin for IntelliJ works pretty well with Puppet code, including reference checks and all the good stuff you'd expect from a half-decent IDE. Can't say anything about Chef or Salt, but with Ansible you get basically shit for help since the IDE just sees a YAML file and nothing more. This is partially the fault of Ansible though, to be honest, modules being standalone scripts that is cool - but they provide no standardized way to inspect their parameters and outputs beyond documentation.

kilburn 9y ago
Ansible's modules documentation is auto-generated from the code. Hence, there is a standardized (across all ansible's modules) way to extract their parameters/outputs. See https://github.com/ansible/ansible/blob/devel/lib/ansible/modules/files/iso_extract.py https://github.com/ansible/ansible/blob/devel/lib/ansible/mo... for example: DOCUMENTATION is a yaml snippet that follows their documentation schema to tell you about all the module's input parameters. EXAMPLES gives you some usage examples. RETURN documents the outputs. A proper IDE plugin could parse those snippets for each module and do some pretty nice autocompletion/inline documentation for you...