Prior to package-spec supporting a means to add dynamic mappings through fields/*.yml files, the hashicorp_vault package created those dynamic mappings by directly specifying them through elasticsearch.index_template.mappings in the manifest.
Under package-spec 3.0.0 those fields are being treated as invalid. I think it should be possible to express those fields in a fields/*.yml file now. So let's do that to resolve these errors.
Error: building package failed: invalid content found in built zip package: found 4 validation errors:
1. file "hashicorp_vault-1.14.0.zip/data_stream/metrics/manifest.yml" is invalid: field elasticsearch.index_template.mappings.dynamic_templates.0.all_values: Additional property path_match is not allowed
2. file "hashicorp_vault-1.14.0.zip/data_stream/metrics/manifest.yml" is invalid: field elasticsearch.index_template.mappings.dynamic_templates.1.all_counters: Additional property path_match is not allowed
3. file "hashicorp_vault-1.14.0.zip/data_stream/metrics/manifest.yml" is invalid: field elasticsearch.index_template.mappings.dynamic_templates.2.all_rates: Additional property path_match is not allowed
4. file "hashicorp_vault-1.14.0.zip/data_stream/metrics/manifest.yml" is invalid: field elasticsearch.index_template.mappings.dynamic_templates.3.all_histograms: Additional property path_match is not allowed
Testing should be performed to compare the installed Elasticsearch index template before and after the change.
Prior to package-spec supporting a means to add dynamic mappings through
fields/*.ymlfiles, the hashicorp_vault package created those dynamic mappings by directly specifying them throughelasticsearch.index_template.mappingsin the manifest.Under package-spec 3.0.0 those fields are being treated as invalid. I think it should be possible to express those fields in a
fields/*.ymlfile now. So let's do that to resolve these errors.Testing should be performed to compare the installed Elasticsearch index template before and after the change.