> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/languages/yaml.md).

# YAML

Language-specific information about the way that SonarQube Cloud supports the analysis of YAML files.

The analysis of YAML files is enabled for some organizations via a feature flag, and will soon be enabled by default for all users. If you want to manually opt-in, you can set the `sonar.featureflag.cloud-security-enable-generic-yaml-and-json-analyzer` property to `true`.

By setting the above mentioned property to `false`, you can also opt-out of the analysis during this roll-out phase.

You can permanently disable the analysis by setting the `sonar.yaml.activate` property to `false` .

These properties do not affect analysis of language / framework specific YAML files.

In addition to this general YAML analysis, YAML files detected as belonging to [CloudFormation](/sonarqube-cloud/analyzing-source-code/languages/cloudformation.md), [Kubernetes/Helm](/sonarqube-cloud/analyzing-source-code/languages/kubernetes.md), or [Ansible](/sonarqube-cloud/analyzing-source-code/languages/ansible.md) are also analyzed by the dedicated analyzers.

## Language-specific properties <a href="#language-specific-properties" id="language-specific-properties"></a>

To discover and update the YAML-specific properties, navigate in SonarQube Cloud to *Your Project* > **Administration** > **General Settings** > **Languages** > **YAML**. See [Configuration overview](/sonarqube-cloud/analyzing-source-code/analysis-parameters/configuration-overview.md) for more information about setting properties.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-cloud/analyzing-source-code/languages/yaml.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.