Add warnings about cloning index templates

Author: kilfoyle

docs/en/ingest-management/data-streams.asciidoc

@@ -103,6 +103,7 @@ For data streams, the index template configures the stream's backing indices as
 These templates are loaded when the integration is installed, and are used to configure the integration's data streams.
 
 [discrete]
+[[data-streams-index-templates-edit]]
 == Edit the {es} index template
 
 WARNING: Custom index mappings may conflict with the mappings defined by the integration
@@ -187,6 +188,8 @@ this pipeline can be used for custom data processing, adding fields, sanitizing
 
 Starting in version 8.12, ingest pipelines can be configured to process events at various levels of customization.
 
+NOTE: If you create a custom index pipeline, Elastic is not responsible for ensuring that it indexes and behaves as expected. Creating a custom pipeline involves custom processing of the incoming data, which should be done with caution and tested carefully.
+
 `global@custom`::
 Apply processing to all events
 +
@@ -305,6 +308,7 @@ Specifically, apply the built-in `90-days-default` {ilm-init} policy so that dat
 
 NOTE: If you cloned an index template to customize the data retention policy on an {es} version prior to 8.13, you must update the index template in the clone to use the `ecs@mappings` component template on {es} version 8.13 or later. See <<data-streams-pipeline-update-cloned-template-before-8.13,Update index template cloned before {es} 8.13>> for the step-by-step instructions.
 
+NOTE: 
 
 [discrete]
 [[data-streams-ilm-one]]
@@ -370,7 +374,7 @@ Now that you've created a component template,
 you need to create an index template to apply the changes to the correct data stream.
 The easiest way to do this is to duplicate and modify the integration's existing index template.
 
-WARNING: When duplicating the index template, do not change or remove any managed properties. This may result in problems when upgrading.
+WARNING: When duplicating the index template, do not change or remove any managed properties. This may result in problems when upgrading. Cloning the index template of an integration package involves some risk as any changes made to the original index template when it is upgraded will not be propagated to the cloned version.
 
 . Navigate to **{stack-manage-app}** > **Index Management** > **Index Templates**.
 . Find the index template you want to clone. The index template will have the `<type>` and `<dataset>` in its name,

docs/en/ingest-management/integrations/integrations-assets-best-practices.asciidoc

@@ -7,6 +7,10 @@ When you use integrations with {fleet} and {agent} there are some restrictions t
 * <<assets-restrictions-without-agent>>
 * <<assets-restrictions-custom-integrations>>
 * <<assets-restrictions-copying>>
+* <<assets-restrictions-editing-assets>>
+* <<assets-restrictions-custom-component-templates>>
+* <<assets-restrictions-custom-ingest-pipeline>>
+* <<assets-restrictions-cloning-index-template>>
 
 [discrete]
 [[assets-restrictions-standalone]]
@@ -46,3 +50,37 @@ This way, because the assets are not managed by another integration, there is le
 
 Note, however, that creating standalone integration assets based off of {fleet} and {agent} integrations is considered a custom configuration that is not tested nor supported. Whenever possible it's recommended to use standard integrations.
 
+[discrete]
+[[assets-restrictions-editing-assets]]
+== Editing assets managed by {fleet}
+
+{fleet}-managed integration assets should not be edited. Examples of these assets include an integration index template, the `@package` component templates, and ingest pipelines that are bundled with integrations. Any changes made to these assets will be overwritten when the integration is upgraded.
+
+[discrete]
+[[assets-restrictions-custom-component-templates]]
+== Creating custom component templates
+
+While creating a `@custom` component template for a package integration is supported, it involves risks which can prevent data from being ingested correctly. This practice can lead to broken indexing, data loss, and breaking of integration package upgrades.
+
+For example:
+
+ * If the `@package` compoment template of an integration is changed from a "normal" datastream to `TSDB` or `LogsDB`, some of the custom settings or mappings introduced may not be compatible with these indexing modes.
+ * If the type of an ECS field is overridden from, for example, `keyword` to `text`, aggregations based on that field may be prevented for built-in dashboards.
+
+A similar caution against custom index mappings is noted in <<data-streams-index-templates-edit>>.
+
+[discrete]
+[[assets-restrictions-custom-ingest-pipeline]]
+== Creating a custom ingest pipeline
+
+If you create a custom index pipeline (as documented in the <<data-streams-pipeline-tutorial,Transform data with custom ingest pipelines>> tutorial), Elastic is not responsible for ensuring that it indexes and behaves as expected. Creating a custom pipeline involves custom processing of the incoming data, which should be done with caution and tested carefully.
+
+Refer to <<data-streams-pipelines>> to learn more.
+
+[discrete]
+[[assets-restrictions-cloning-index-template]]
+== Cloning the index template of an integration package
+
+When you clone the index template of an integration package, this involves risk as any changes made to the original index template when it is upgraded will not be propagated to the cloned version. That is, the structure of the new index template is effectively frozen at the moment that it is cloned. Cloning an index template of an integration package can therefore lead to broken indexing, data loss, and breaking of integration package upgrades.
+
+Additionally, cloning index templates to add or inject additional component templates cannot be tested by Elastic, so we cannot guarantee that the template will work in future releases.