anchor.diff:      },
       "mappings": {
         "_source": {
  -        "enabled": false
  +        "enabled": true
         },
         "properties": {
           "host_name": {
  
positive.code: for `logs-*-*`.
  ====
  // end::built-in-index-templates[]
  
  When a composable template matches a given index
  it always takes precedence over a legacy template. If no composable template matches, a legacy
  template may still match and be applied.
  
  If an index is created with explicit settings and also matches an index template,
  the settings from the create index request take precedence over settings specified in the index template and its component templates.
  
  [source,console]
  --------------------------------------------------
  PUT _component_template/component_template1
  {
    "template": {
  
negative.code: [[index-templates]]
  = Index templates
  
  NOTE: This topic describes the composable index templates introduced in {es} 7.8.
  For information about how index templates worked previously,
  see the <<indices-templates-v1,legacy template documentation>>.
  
  [[getting]]
  An index template is a way to tell {es} how to configure an index when it is
  created. For data streams, the index template configures the stream's backing
  indices as they are created. Templates are configured
  *prior to index creation*. When an index is created - either manually or
  through indexing a document - the template settings are used as a basis for
  creating the index.
  
  There are two types of templates: index templates and <<indices-component-template,component templates>>. Component templates are reusable building
  blocks that configure mappings, settings, and aliases. While you can use
  component templates to construct index templates, they aren't directly applied
  to a set of indices. Index templates can contain a collection of component
  templates, as well as directly specify settings, mappings, and aliases.
  
  The following conditions apply to index templates:
  
  * Composable templates take precedence over legacy templates. If no composable
  template matches a given index, a legacy template may still match and be
  applied.
  * If an index is created with explicit settings and also matches an index
  template, the settings from the <<indices-create-index,create index>> request
  take precedence over settings specified in the index template and its component
  templates.
  * If a new data stream or index matches more than one index template, the index
  template with the highest priority is used.
  
  .Using index templates with {fleet} or {agent}
  ****
  // tag::built-in-index-templates[]
  [IMPORTANT]
  ====
  