Enable k2v feature flag in CI
All checks were successful
continuous-integration/drone/tag Build is passing
continuous-integration/drone/pr Build is passing
continuous-integration/drone Build is passing
continuous-integration/drone/push Build is passing

This commit is contained in:
Alex 2022-05-10 13:29:14 +02:00
parent b2a2d3859f
commit eef04d4d59
Signed by: lx
GPG key ID: 0E496D15096376BE

View file

@ -86,13 +86,14 @@ in let
It speeds up the compilation (when the feature is not required) and released crates have less dependency by default (less attack surface, disk space, etc.). It speeds up the compilation (when the feature is not required) and released crates have less dependency by default (less attack surface, disk space, etc.).
But we want to ship these additional features when we release Garage. But we want to ship these additional features when we release Garage.
In the end, we chose to exclude all features from debug builds while putting (all of) them in the release builds. In the end, we chose to exclude all features from debug builds while putting (all of) them in the release builds.
Currently, the only feature of Garage is kubernetes-discovery from the garage_rpc crate. Currently, the only such feature of Garage is kubernetes-discovery from the garage_rpc crate.
The experimental feature k2v is also enabled here in all builds.
*/ */
(pkgs.rustBuilder.rustLib.makeOverride { (pkgs.rustBuilder.rustLib.makeOverride {
name = "garage_rpc"; name = "garage_rpc";
overrideArgs = old: overrideArgs = old:
{ {
features = if release then [ "kubernetes-discovery" ] else []; features = if release then [ "kubernetes-discovery" "k2v" ] else [ "k2v" ];
}; };
}) })
]; ];