feat(stackable-operator): Add re-exports for telemetry and versioned crate (#1007)

* feat: Add re-exports to stackable-operator

* chore: Update changelog

* chore: Bump crossbeam-channel 0.5.15 (0.5.14 was yanked)

* fix(docs): Use correct references

Author: Techassi

Cargo.lock

@@ -4,6 +4,13 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+### Added
+
+- Add re-exports for `stackable-telemetry` and `stackable-versioned` ([#1007]).
+- Add new features: `default`, `full`, `telemetry`, and `versioned` ([#1007]).
+
+[#1007]: https://github.com/stackabletech/operator-rs/pull/1007
+
 ## [0.91.0] - 2025-04-08
 
 ### Changed

crates/stackable-operator/CHANGELOG.md

@@ -8,10 +8,15 @@ edition.workspace = true
 repository.workspace = true
 
 [features]
+full = ["time", "telemetry", "versioned"]
+default = ["telemetry", "versioned"]
 time = ["dep:time"]
+telemetry = []
+versioned = []
 
 [dependencies]
-stackable-telemetry = { path = "../stackable-telemetry", features = ["clap"]}
+stackable-telemetry = { path = "../stackable-telemetry", features = ["clap"] }
+stackable-versioned = { path = "../stackable-versioned", features = ["k8s"] }
 stackable-operator-derive = { path = "../stackable-operator-derive" }
 stackable-shared = { path = "../stackable-shared" }
 

crates/stackable-operator/Cargo.toml

@@ -1,3 +1,11 @@
+//! ## Crate Features
+//!
+//! - `default` enables a default set of features which most operators need.
+//! - `full` enables all available features.
+//! - `time` enables interoperability between [`time::Duration`] and the `time` crate.
+//! - `telemetry` enables various helpers for emitting telemetry data.
+//! - `versioned` enables the macro for CRD versioning.
+
 pub mod builder;
 pub mod cli;
 pub mod client;
@@ -21,14 +29,16 @@ pub mod time;
 pub mod utils;
 pub mod validation;
 
+// External re-exports
+pub use k8s_openapi;
+pub use kube;
+pub use schemars;
 // Internal re-exports
+// TODO (@Techassi): Ideally we would want webhook and certs exported here as
+// well, but that would require some restructuring of crates.
+pub use stackable_shared as shared;
 pub use stackable_shared::{crd::CustomResourceExt, yaml::YamlSchema};
-
-pub mod shared {
-    pub use stackable_shared::*;
-}
-
-// External re-exports
-pub use ::k8s_openapi;
-pub use ::kube;
-pub use ::schemars;
+#[cfg(feature = "telemetry")]
+pub use stackable_telemetry as telemetry;
+#[cfg(feature = "versioned")]
+pub use stackable_versioned as versioned;

crates/stackable-operator/src/lib.rs

@@ -700,7 +700,7 @@ especially for CustomResourceDefinitions (CRDs). These features are
 completely opt-in. You need to enable the `k8s` feature (which enables
 optional dependencies) and use the `k8s()` parameter in the macro.
 
-You need to derive both [`kube::CustomResource`] and [`schemars::JsonSchema`].
+You need to derive both [`kube::CustomResource`] and [`schemars::JsonSchema`][1].
 
 ```
 # use stackable_versioned_macros::versioned;
@@ -730,7 +730,7 @@ println!("{}", serde_yaml::to_string(&merged_crd).unwrap());
 # }
 ```
 
-The generated `merged_crd` method is a wrapper around [kube's `merge_crds`][1]
+The generated `merged_crd` method is a wrapper around [kube's `merge_crds`][2]
 function. It automatically calls the `crd` methods of the CRD in all of its
 versions and additionally provides a strongly typed selector for the stored
 API version.
@@ -846,6 +846,9 @@ mod v1 {
 It is possible to include structs and enums which are not CRDs. They are instead
 versioned as expected (without adding the `#[kube]` derive macro and generating
 code to merge CRD versions).
+
+[1]: https://docs.rs/schemars/latest/schemars/derive.JsonSchema.html
+[2]: https://docs.rs/kube/latest/kube/core/crd/fn.merge_crds.html
 "#
 )]
 #[proc_macro_attribute]