Dry run will help you to understand what are the real resources which will to be expanded and deployed to the Kubernetes cluster. In other words, it will mock to run the same logic as KubeVela's controller and output the results locally.
For example, let's dry-run the following application:
In this example, the definitions(
vela-app depends on are the built-in
components and traits of KubeVela. You can also use
--definitions to specify your local definition files.
--definitions permits users to provide capability definitions used in the application from local files.
dry-run cmd will prioritize the provided capabilities than the living ones in the cluster.