


Let's review the differences between the copy artifact/config and download commands. At deployment runtime, Harness uses the metadata to copy or download the artifact to the target hosts/containers.

Harness services allows you to identify artifacts using their metadata. The following command types are supported: In this case, using the looping strategy. These commands will download the artifact and copy the artifact/config to the delegate only, not the target hosts.įor a script command, you might want to run the script for each instance that was output from the Fetch Instance step. These commands should be run once on the delegate. For the download artifact and copy the artifact/config commands, you do not need the looping strategy.
