tomato·bazeldocs v0 · latest ▾
Docs/Reference/Modules/rules_beam

rules_beam

Bazel-idiomatic Apache Beam pipeline packaging + cross-runner deployment (DirectRunner, Dataflow, Flink, Spark)

Latest0.0.2
Versions1
CategoryBazel rules
MaintainersMatt Marshall
Registryhttps://registry.tbzl.dev/modules/rules_beam/
Sourcegithub.com/tomato-bazel/rules_beam
MODULE.bazelstarlark
bazel_dep(name = "rules_beam", version = "0.0.2")

View source & releases on GitHub ↗

Apache Beam pipeline build + cross-runner deployment (DirectRunner, Dataflow, Flink, Spark)

Status: v0.0.1 — scaffold

No public surface yet. See CHANGELOG.md for what has shipped.

Install

.bazelrc:

common --registry=https://registry.fastverk.com/
common --registry=https://bcr.bazel.build/

MODULE.bazel:

bazel_dep(name = "rules_beam", version = "0.0.1")

Conformance#

No gate findings. 8 contested atoms. See how gating works or the full report.

Contested atoms

Third-party modules where this module resolves a different version than others do. Not a violation of anything this module did — it is the actionable form of a registry-level convergence finding, and the sentence a maintainer can act on.

AtomResolved hereElsewhere
apple_support 1.24.2 2.2.0 ×1
bazel_skylib 1.8.2 1.9.0 ×2
nlohmann_json 3.6.1 3.12.0.bcr.1 ×1
protobuf 33.4 34.0.bcr.1 ×2
rules_jvm_external 6.7 6.8 ×4
rules_python 1.7.0 2.0.1 ×1
rules_swift 3.1.2 3.6.1 ×1
upb 0.0.0-20220923-a547704 0.0.0-20230516-61a97ef ×1

Dependencies#

rules_beam in the registry graph — what it depends on (left) and what depends on it (right).

Depends on

platforms1.0.0bazel_skylib1.8.2rules_java8.6.1rules_shell0.6.1devstardoc0.7.2dev

Versions#

1 published version, newest first. Each resolves to an immutable, integrity-checked archive.

VersionIntegrity (sha256)Source archive
0.0.2 latest 9IovyGNhkYAmXsna… tag archive ↗

Changelog#

All notable changes to rules_beam. The format is loosely Keep a Changelog — version headers mirror the published bazel-registry entries.

0.0.2 — data passthrough on beam_pipeline_binary

  • beam_pipeline_binary gains an optional data attribute that is forwarded to the underlying java_binary. Use for runtime binaries the pipeline shells to (sidecars, helper tools) when running locally on DirectRunner. Cloud-runner consumers should prefer native_binaries (bundled inside the fat jar at /native/<basename>) because runfiles aren’t carried across to Dataflow / Flink / Spark workers.

0.0.1 — scaffold

  • Initial scaffold via rels scaffold. No public API yet.

← All modules