Is it possible to destroy a job after it has been executed. For example when using the job to run migrations for the service. This job will be executed before the deployment so after the deployment this job will do nothing. Can I configure something that this job will be destroyed after it’s been executed to reduce the costs of hosting?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.