From cf0bef3e92b73a30693430ee892382517f01a67d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=98yvind=20Harboe?= Date: Tue, 25 Aug 2026 21:56:17 +0200 Subject: [PATCH] Export scripts/variables.yaml as a source label MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit flow/BUILD's exports_files already publishes scripts/synth.tcl so bazel-orfs can point a rule attribute at @orfs//flow:scripts/synth.tcl rather than vendor a drifting copy. scripts/variables.yaml -- the variable catalogue with each variable's description and stage scoping -- has the same need but no label: it is reachable only inside the private makefile filegroups' data, so a downstream target cannot data-dep the catalogue at a given commit. Add it to the same exports_files. Source-only change, no flow behaviour. Signed-off-by: Øyvind Harboe Co-Authored-By: Claude Opus 5 (1M context) --- flow/BUILD | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/flow/BUILD b/flow/BUILD index 4f57af10d8..ea3d5d9bab 100644 --- a/flow/BUILD +++ b/flow/BUILD @@ -24,7 +24,14 @@ exports_files( # instead of vendoring its own (drifting) copy at the bazel-orfs repo # root. See bazel-orfs `private/rules.bzl`. exports_files( - ["scripts/synth.tcl"], + [ + "scripts/synth.tcl", + # Expose variables.yaml as an addressable source label so a + # downstream target can data-dep the variable catalogue at this + # commit. It is reachable today only inside the private makefile + # filegroups' data, not as a source target. + "scripts/variables.yaml", + ], visibility = ["//visibility:public"], )