Tasks

Kotless has two types of tasks — service and end-user. Despite the fact that service tasks are also available for end-user, you should not call them explicitly. All of them will be called as dependencies of end-user tasks.

Note that 99% percent of the time you should just execute ./gradlew deploy

End-user tasks:

• deploy — task that actually deploys your Kotless-based application to the cloud provider. The task will call all other necessary tasks by dependencies, and most of the time you should only use this task;
• plan — task that "plans" the deployment. The result of this task is a log of changes that will be applied to the cloud provider (Terraform generated);
• destroy — task that "destroys" the deployment. This task destroys all the resources created by deploy task. By default, this task is hidden and can be enabled through Extensions API.
• local — task that runs application locally.

Service tasks:

• generate — task that generates the deployment definition (Terraform code) for your application;
• init — task that performs terraform init on generated Terraform code;
• download_terraform — task that downloads the required version of Terraform from HashiCorp site.