tar_delete: Delete locally stored target return values.

View source: R/tar_delete.R

tar_deleteR Documentation

Delete locally stored target return values.


Delete the return values of targets in _targets/objects/. but keep the records in _targets/meta/meta.


tar_delete(names, cloud = TRUE, store = targets::tar_config_get("store"))



Names of the targets to remove from _targets/objects/. You can supply symbols or tidyselect helpers like any_of() and starts_with().


Logical of length 1, whether to delete objects from the cloud if applicable (e.g. AWS, GCP). If FALSE, files are not deleted from the cloud.


Character of length 1, path to the targets data store. Defaults to tar_config_get("store"), which in turn defaults to _targets/. When you set this argument, the value of tar_config_get("store") is temporarily changed for the current function call. See tar_config_get() and tar_config_set() for details about how to set the data store path persistently for a project.


If you have a small number of data-heavy targets you need to discard to conserve storage, this function can help. Local external files files (i.e. format = "file" and repository = "local") are not deleted. For targets with repository not equal "local", tar_delete() attempts to delete the file and errors out if the deletion is unsuccessful. If deletion fails, either log into the cloud platform and manually delete the file (e.g. the AWS web console in the case of repository = "aws") or call tar_invalidate() on that target so that targets does not try to delete the object. For patterns recorded in the metadata, all the branches will be deleted. For patterns no longer in the metadata, branches are left alone.

See Also

Other clean: tar_destroy(), tar_invalidate(), tar_prune()


if (identical(Sys.getenv("TAR_EXAMPLES"), "true")) {
tar_dir({ # tar_dir() runs code from a temporary directory.
    tar_target(y1, 1 + 1),
    tar_target(y2, 1 + 1),
    tar_target(z, y1 + y2)
}, ask = FALSE)
tar_delete(starts_with("y")) # Only deletes y1 and y2.
tar_make() # y1 and y2 rebuild but return same values, so z is up to date.

targets documentation built on Jan. 6, 2023, 5:16 p.m.