ansible-language-server
jinja-docsite
ansible-language-server | jinja-docsite | |
---|---|---|
13 | 6 | |
250 | 5 | |
- | - | |
8.0 | 10.0 | |
about 2 months ago | 9 months ago | |
TypeScript | HTML | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ansible-language-server
-
The Bullhorn #108 (Ansible Newsletter)
Version 1.1.0 The Ansible Language Server (ALS) underwent a substantial upgrade. ALS v1.1.0 has adopted the new YAML 2.x package and successfully updated its code base accordingly. This significant development brings enhanced capabilities in terms of YAML diagnostics and strengthened security measures. Another crucial feature addition was the completion for variables declared inside a playbook. Full list of change-logs here.
-
The Bullhorn #93 (Ansible Newsletter)
Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board
-
[Ansible] Visual Studio Code et l’extension Redhat Ansible (quelqu’un peut-il le faire fonctionner) ?
Si cela ne fonctionne toujours pas, soulève un problème Github ici https://github.com/ansible/vscode-ansible ou https://github.com/ansible/ansible-language-server avec des détails comme :
-
Anyone here have success with Ansible syntax highlightning lsp?
You are conflating multiple functions. I have used the ansible language server 1 with decent success in both 0.7 and 0.8. It provides autocompletion of modules and diagnostics from ansible-lint, but does nothing to address syntax highlighting. Your project should have either an ansible.cfg or .ansible-lint at your project’s top level and your yaml files should be of filetype yaml.ansible. If you run :LspInfo it should display ansiblels as active.
-
LSP configuration
I'm looking to use a language (Ansible flavored YAML) that does have an LSP implementation, but is not supported by tree-sitter.
- How to properly set up LSP ansible language server in emacs, for proper ansible playbook editing support?
-
A new version of vscode ansible extension is out
Does the standalone usage help?
-
The Bullhorn #45 (Ansible Newsletter)
Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board
-
Red Hat Ansibe Extension for VSCode
Additionally, I found that the entire extension stopped working because in the past, easy-install had added a .egg file to my python path. I submitted a fix and it was accepted, but I'm not sure if the fixed language server is part of the current extension version. Might be worth checking for files like that in the paths listed in sys.path.
-
Visual Studio Code and the Redhat Ansible extension (can anyone get it to work) ?
I think we found the bug as https://github.com/ansible/ansible-language-server/issues/117
jinja-docsite
-
The Bullhorn #104 (Ansible Newsletter)
Help us improve the HTML landing pages on docs.ansible.com with some better Jinja templating! Find out how to get involved and contribute to our improved content experience here.
-
Feedback wanted: Proposed new front pages to docs.ansible.com
Great idea! Logged it as an issue - https://github.com/ansible/jinja-docsite/issues/78
-
The Bullhorn #94 (Ansible Newsletter)
Come join us and help build a new docsite! The community team has been working to update the Ansible documentation landing page based on a set of user journeys. Right now we're working on a prototype docsite to improve the navigation and user experience.
-
The Bullhorn #93 (Ansible Newsletter)
The next step is to apply these journeys to an updated layout and navigation for docs.ansible.com. We're working to improve navigation and user experience for Ansible community documentation. Come join us and help build a new docsite!
-
The Bullhorn #91 (Ansible Newsletter)
Are you interested in helping improve the navigation and layout of "docs.ansible.com"? Do you think you can help connect users with information in the docs more efficiently? If so, the Ansible community team invites you to contribute to this repository. We plan to use this repository to overhaul the landing pages for Ansible community documentation and create a more intuitive and modern user experience. See you in the PR queue!
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible-community/ansible-lint]
nvim-lspconfig - Quickstart configs for Nvim LSP
docsite - Static HTML and assets for docs.ansible.com
jupyterlab-lsp - Coding assistance for JupyterLab (code navigation + hover suggestions + linters + autocompletion + rename) using Language Server Protocol
community.ioscm - iosxe in controller mode
ansible-lint - Best practices checker for Ansible [Moved to: https://github.com/ansible/ansible-lint]
cisco.ios - Ansible Network Collection for Cisco IOS
vscode-ansible - vscode/vscodium extension for providing Ansible auto-completion and integrating quality assurance tools like ansible-lint, ansible syntax check, yamllint, molecule and ansible-test.
amq - A collection to manage AMQ brokers
ansible-navigator - A text-based user interface (TUI) for Ansible.
vyos.vyos - Ansible Network Collection for VyOS