Open nightkr opened 4 months ago
Currently, op-rs embeds a lot of product-specific knowledge. For example, there are several configuration bits that are only relevant to our specific deployment of OPA that are always embedded in the configuration (https://github.com/stackabletech/operator-rs/blob/3548b01e34c8e1b021b6ac6a2e3b91cc8d9ce2c8/crates/stackable-operator/src/product_logging/framework.rs#L755-L805).
It makes sense to offer a few defaults ("this is how we typically configure log4j to behave"), but the final say should be up to the operator and we definitely shouldn't have single-product configurations in the framework crate.
Currently, op-rs embeds a lot of product-specific knowledge. For example, there are several configuration bits that are only relevant to our specific deployment of OPA that are always embedded in the configuration (https://github.com/stackabletech/operator-rs/blob/3548b01e34c8e1b021b6ac6a2e3b91cc8d9ce2c8/crates/stackable-operator/src/product_logging/framework.rs#L755-L805).
It makes sense to offer a few defaults ("this is how we typically configure log4j to behave"), but the final say should be up to the operator and we definitely shouldn't have single-product configurations in the framework crate.