> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/armory/general/using-find-artifacts-from-resource-manifest-overwrites-rendered-artifacts.md).

# Using Find Artifacts From Resource (Manifest) overwrites rendered artifacts

### Issue <a href="#issue" id="issue"></a>

This occurs when there is a pipeline that uses `Find Artifacts From Resource (Manifest)` to find details of the currently running deployment.However, when using the `Find Artifacts From Resource (Manifest)` stage, it overrides any pod images with the one that is currently in production. Example issue: <https://github.com/spinnaker/spinnaker/issues/6506>

### Cause <a href="#cause" id="cause"></a>

There was no specification available to opt-out of this artifact binding. Without this, it will always bind the artifact by `default`.