Extraction error: Config transforms failing
Sometimes you might notice that even though your deployments are coming through without errors, no changes are being applied to the Cloud environments. This might be due to Config Transforms failing during the extraction process.
This issue may occur if you have added custom Config Transforms to your project.
Since Config Transforms are applied on every data extraction, the behavior will continue until the Config Transform files are either corrected or removed.
How do I know I have this issue?
This problem is a bit tricky to spot, as the only indicator is that changes you made on the source environment are not being applied - even though the deployment was complete (although when pushing from local you might get a warning message).
The environment overview on your project will most likely not mention anything, which means you will have to delve into KUDU.
How to check for and resolve the issue
Access KUDU on the environment where you expected to see your changes reflected
Navigate to site > deployments folder in KUDU
Find the latest deployment folder, either by date or by ID of the deployment (you can find the latest active deployment ID by opening the active file in the folder)
If the deployment folder with the latest ID contains only two items (
log.log
andstatus.xml
), that means something went wrong as we would normally see two more files -commits.uc
andmanifest
Open the
log.log
file and look for anything mentioningXmlTransform
.
An example of a faulty config transform not being applied could look something like this:
Verify the Config Transform file mentioned in the error message and ensure the XML is valid.
Update the Config Transform file as necessary on your local solution and deploy the change to the Cloud environments.
Run a 'Schema Deployment From Data Files' to extract the schema that you previously deployed.
To find errors in the config transform, you can use an xml validation tool like https://www.xmlvalidation.com/
Last updated