fapifta opened a new pull request, #6771:
URL: https://github.com/apache/ozone/pull/6771
## What changes were proposed in this pull request?
This PR adds the crypto-default module, that will serve as the home of the
default (unrestricted) crypto implementation code, that does not have any
compliance restrictions, and serves as the default used implementation in our
codebase.
On the naming let me add some reasoning.
The {{hdds.crypto.compliance.mode}} configuration property has a default
value of "unrestricted" which may possibly implies that this module should be
called hdds-crypto-unrestricted, but as I learned unrestricted may be a
confusing term.
As a configuration option, it sounds reasonable, as it marks that the crypto
compliance mode is not restricted by any law or ruleset by default. When it
comes to module naming though, I think it is much more reasonable to express
that this module contains the default implementation, instead of trying to
express the intension and some implementation property of the code within, that
is why I propose to name this module as hdds-crypto-default.
This PR is related to #6770 in a sense that this one intends to contain an
implementation for the generic module, and also this PR is part of the effort
defined in the related design under (#6685)
## What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10936
## How was this patch tested?
A local build succeeded with the provided pom.xml, no further test beyond
that is required.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
