If you are running Deploy 4+, we recommend you generate Umbraco Deploy Artifact (UDA) files from the Deploy Dashboard instead of KUDU. For more information, see the Deploy Dashboard.
Sometimes our guides require you to generate UDA files for your project's metadata. Every time you create something in the backoffice on your Umbraco Cloud project, UDA files will be generated.
Generating UDA files manually ensures that you have everything you need to deploy successfully from one environment to another.
When you create something in the backoffice of your Umbraco Cloud project and hit save, a UDA file will be generated.
The UDA file contains metadata and detailed information about the type that was created.
Here's an example of what a UDA file looks like for a Blog Page:
This UDA file represents a Document Type with the name Blog. All dependencies for the document type are listed in the file and metadata like AllowedAtRoot and Icon.
UDA files are generated for the following types:
Data types
Data type containers
Dictionary items
Document types
Document type container
Languages
Macros
Media types
Member types
Relation types
Templates
Follow these steps to generate UDA files:
Access Kudu.
Navigate to CMD under the Debug console menu.
In the file structure, navigate to site/wwwroot/umbraco/Deploy.
Type the following command in the CMD console: echo > deploy-export
The Deploy engine will generate UDA files for all the types in your project.
When it's done, you'll end up with a deploy-complete marker.
Run an extraction, making sure you can get a deploy-complete marker - see Run an extraction article.
Generating UDA files manually might sometimes end up giving you collision errors on your environments due to duplicates. This can be resolved by following our Structure Error documentation.
Find general information about Kudu and how to access the tool in the Power tools article.