From 04aeaa21187c0176330a7e87f4c53a643e93f344 Mon Sep 17 00:00:00 2001 From: Alex Szabo Date: Thu, 7 Mar 2024 12:58:36 +0100 Subject: [PATCH] [Ops] Use full relative file paths for location entries (#178205) ## Summary Another padding on https://github.com/elastic/kibana/pull/178136 - this time using another way of proper local paths, with `./` added. --- .buildkite/pipeline-resource-definitions/locations.yml | 2 +- catalog-info.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.buildkite/pipeline-resource-definitions/locations.yml b/.buildkite/pipeline-resource-definitions/locations.yml index 082746287ff6b..991da0821e7c0 100644 --- a/.buildkite/pipeline-resource-definitions/locations.yml +++ b/.buildkite/pipeline-resource-definitions/locations.yml @@ -6,4 +6,4 @@ metadata: spec: type: file targets: - - kibana-migration-staging.yml + - ./kibana-migration-staging.yml diff --git a/catalog-info.yaml b/catalog-info.yaml index f8fdc15d35819..5c176ba7fbc08 100644 --- a/catalog-info.yaml +++ b/catalog-info.yaml @@ -37,7 +37,7 @@ metadata: description: A location re-routing file, pointing to individual buildkite pipeline definition files spec: type: file - target: .buildkite/pipeline-resource-definitions/locations.yml + target: ./.buildkite/pipeline-resource-definitions/locations.yml ---