From b526565b90b873b4fe7e7817d57b447cd323e370 Mon Sep 17 00:00:00 2001
From: Dentrax <furkan.turkal@chainguard.dev>
Date: Tue, 19 Nov 2024 21:57:06 +0300
Subject: [PATCH] pipelines/cargo: ability to override output-dir

Some projects exports the binaries to different paths
so that we couldn't use the cargo/build pipeline properly.

Signed-off-by: Dentrax <furkan.turkal@chainguard.dev>
---
 pkg/build/pipelines/cargo/build.yaml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/pkg/build/pipelines/cargo/build.yaml b/pkg/build/pipelines/cargo/build.yaml
index 366b20113..3b5244b6a 100644
--- a/pkg/build/pipelines/cargo/build.yaml
+++ b/pkg/build/pipelines/cargo/build.yaml
@@ -36,11 +36,16 @@ inputs:
       Directory where binaries will be installed
     default: bin
 
+  output-dir:
+    description: |
+      Directory where the binaris will be placed after building. Defaults to target/release
+    default: target/release
+
 pipeline:
   - runs: |
       # Installation directory should always be bin as we are producing a binary
       INSTALL_PATH="${{targets.contextdir}}/${{inputs.prefix}}/${{inputs.install-dir}}"
-      OUTPUT_PATH="target/release"
+      OUTPUT_PATH="${{inputs.output-dir}}"
 
       # Enter target package directory
       cd "${{inputs.modroot}}"