Sometimes you may want to execute arbitrary commands on your deployment container - for example, manually altering the state or manipulating a local file. These commands can be run using Custom Flows, but that requires committing the commands to your git repository, which doesn't always fit the use case. In these cases, it is possible to execute an ad hoc task on the deployment container.
Permissions to run a one time tasks
As ad hoc tasks allow you to run any command on the deployment container, only organization administrators may run these tasks.
From the environment's advanced context menu, click on
Run a Task.
It will prompt you to enter the commands you desire to execute.
Enter the commands, as you would in a bash script. Separate commands with new lines.
When you are ready to run your task - click the
RUN A TASK button below.
Tasks have a 30 minute timeout
Your task will be queued and executed on the deployment container, including the local cache env0 saves between deployments. You'll be able to see your commands execute in the Deployment Logs, like any other deployment.
During the task execution, all the variables that are defined in the environment will be available for you to use.
- Migrate state:
terraform init -migrate-state -force-copyor
echo "yes" | terraform init -migrate-state
- Unlock state:
terraform force-unlock -force LOCK_ID [DIR]
- Retrieve output:
terraform output [options] [NAME]
- Taint a resource
terraform taint [options] <address>
- Move state:
terraform state mv [options] SOURCE DESTINATION
Updated about 2 months ago