All Projects → ansible-community → schemas

ansible-community / schemas

Licence: MIT License
Hosts JSON validation schemas for Ansible files, used by vscode-ansible extension.

Programming Languages

typescript
32286 projects

Projects that are alternatives of or similar to schemas

molecule-podman
Molecule Podman Driver allows use of podman as backend for testing.
Stars: ✭ 48 (+92%)
Mutual labels:  ansible-devtools
ansible-language-server
Ansible Language Server
Stars: ✭ 114 (+356%)
Mutual labels:  ansible-devtools
json-schema-js-gui-model
Handy gui model and associated translator that can be used to construct javascript UI forms from json-schemas
Stars: ✭ 19 (-24%)
Mutual labels:  json-schemas
molecule-docker
Molecule Docker Driver allows molecule users to test Ansible code using docker containers.
Stars: ✭ 71 (+184%)
Mutual labels:  ansible-devtools
express-json-validator-middleware
Express middleware for validating requests against JSON schema
Stars: ✭ 148 (+492%)
Mutual labels:  json-schemas
fbp-protocol
Tests, schemas, and specifications for the Flow Based Programming Network Protocol
Stars: ✭ 35 (+40%)
Mutual labels:  json-schemas
WG3-MetadataSpecifications
WG3 Metadata Specification
Stars: ✭ 25 (+0%)
Mutual labels:  json-schemas
Ansible Lint
Best practices checker for Ansible
Stars: ✭ 2,648 (+10492%)
Mutual labels:  ansible-devtools
Molecule
Molecule aids in the development and testing of Ansible roles
Stars: ✭ 3,262 (+12948%)
Mutual labels:  ansible-devtools

Schemas for Ansible, Zuul and Molecule

tox Code style: black Repository License: MIT

About Schemas for Ansible, Zuul and Molecule

This project aims to generate JSON/YAML validation schemas for Ansible files such as playbooks, tasks, requirements, meta or vars and also for Zuul and Molecule configuration.

Keep in mind that these schemas will limit your freedom of choice regarding the syntax you can use to write Ansible tasks as they do not allow some historical forms which are still allowed by Ansible itself.

Not any file accepted by Ansible will pass these schemas but we do expect that any file that passed these schemas should be accepted by Ansible.

  • YAML 1.2 booleans are required as true or false, while Ansible itself allows you to use more relaxed forms like yes or no.
  • Inline actions are not allowed, as schema cannot validate them
  • Non builtin modules must be called using action: blocks
  • Module arguments are not yet verified but we plan to implement it

As these schemas are still experimental, creating pull-requests to improve the schema is of much greater help. Though you are still welcome to report bugs but expect them to take a longer time until someone finds time to fix them.

If you want to help improve the schemas, have a look at the development documentation.

Activating the schemas

At this moment installing Ansible VS Code Extension by Red Hat will activate these schemas. The file patterns used to trigger their use can be seen here

Because these schemas are generic, you can easily use them with any validators that support them.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].