pub fn install_fips_crypto_provider() -> Result<(), CratestackError>Expand description
Crypto provider selection for FIPS-validated deployments.
crypto-aws-lc-rs is not implemented yet. Enabling it is a hard
compile_error!, not a working FIPS mode — this used to return Ok(())
without installing any provider, which is a false assurance in a
compliance-facing API: a service that called this and checked for Ok
got an affirmative return while still running on the non-FIPS ring
backend. See https://github.com/cratestack/cratestack/issues/334.
Making this real requires the TLS backend becoming a genuine choice
across cratestack-sqlx and cratestack-client-rust (both currently
hard-select ring), not just adding aws-lc-rs as a dependency here —
Cargo features are additive, so enabling crypto-aws-lc-rs today would
only add a second provider alongside ring, not replace it. Until that
backend-selection work lands, this function fails to compile under the
feature rather than silently lying about what it installed.