We need to add a couple of new metadata properties to the search index. For that, we have created a custom index, included the additional properties, and made it part of our source code. Referred this link - https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/operations/indexing... to do this. Built and deployed the code successfully in my local AEM instance. Now when we try to deploy the same code into the cloud instance through cloud manager pipeline, it fails in the code scanning step with this error - "The index /oak:index/damAssetLucene-7-custom-1 is a customization of the out of the box index /oak:index/damAssetLucene which requires a config.xml file under the child node named tika". The strange thing is that we already have this tika folder as part of our index code and a config.xml inside it. But somehow, AEM/pipeline doesn't recognize it and keeps on failing. Can anyone help to resolve this?