RUBY-2175 Change all instances of "FLE/Field-Level Encryption" to say "Client-Side Encryption" (#1785)

Co-authored-by: Oleg Pudeyev <[email protected]>

Author: 2 people

docs/tutorials/client-side-encryption.txt

@@ -17,8 +17,8 @@ to encrypt specific fields in MongoDB documents before inserting them into the
 database.
 
 With client-side encryption, developers can encrypt fields client-side without
-any server-side configuration or directives. Client-side field-level encryption
-supports workloads where applications must guarantee that unauthorized parties,
+any server-side configuration or directives. Client-side encryption supports
+workloads where applications must guarantee that unauthorized parties,
 including server administrators, cannot read the encrypted data.
 
 .. warning::

lib/mongo/error/crypt_error.rb

@@ -1,3 +1,7 @@
+# Copyright (C) 2020 MongoDB Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
 #   http://www.apache.org/licenses/LICENSE-2.0
@@ -11,7 +15,7 @@
 module Mongo
   class Error
 
-    # An error related to field-level encryption
+    # An error related to client-side encryption.
     class CryptError < Mongo::Error
       # Create a new CryptError
       #

lib/mongo/error/kms_error.rb

@@ -1,3 +1,7 @@
+# Copyright (C) 2020 MongoDB Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
 #   http://www.apache.org/licenses/LICENSE-2.0
@@ -11,7 +15,8 @@
 module Mongo
   class Error
 
-    # A KMS-related error during field-level encryption
-    class KmsError < CryptError; end
+    # A KMS-related error during client-side encryption.
+    class KmsError < CryptError
+    end
   end
 end

lib/mongo/error/mongocryptd_spawn_error.rb

@@ -1,3 +1,7 @@
+# Copyright (C) 2020 MongoDB Inc.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
 #   http://www.apache.org/licenses/LICENSE-2.0
@@ -11,14 +15,8 @@
 module Mongo
   class Error
 
-    # An error related to spawning mongocryptd for field-level encrpytion
+    # An error related to spawning mongocryptd for client-side encryption.
     class MongocryptdSpawnError < CryptError
-      # Create a new MongocryptdSpawnError
-      #
-      # @param [ String ] message The error message
-      def initialize(message)
-        super(message)
-      end
     end
   end
 end

spec/README.md

@@ -286,7 +286,7 @@ possible to run just the Kerberos-related unit tests without provisioning a
 MongoDB deployment; consult .evergreen/run-tests-kerberos-unit.sh for the
 full list of relevant test files.
 
-## Field-Level Encryption
+## Client-Side Encryption
 
 Install libmongocrypt on your machine:
 
@@ -305,7 +305,7 @@ Option 2: Build from source
 - To build libmongocrypt from source, follow the instructions in the README on the libmongocrypt GitHub repo: https://github.com/mongodb/libmongocrypt
 
 Create AWS KMS keys
-Many of the Field-Level Encryption tests require that you have an encryption
+Many of the Client-Side Encryption tests require that you have an encryption
 master key hosted on AWS's Key Management Service. Set up a master key by following
 these steps:
 
@@ -320,7 +320,7 @@ in environment variables on your local machine. Create an access key by followin
 "Managing Access Keys (Console)" instructions in this guide:
 https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey
 Once an access key has been created, store the access key id and the access key
-secret in environment variables. If you plan to frequently run Field-Level
+secret in environment variables. If you plan to frequently run Client-Side
 Encryption tests, it may be a good idea to put these lines in your .bash_profile
 or .bashrc file. Otherwise, you can run them in the terminal window where you
 plan to run your tests.
@@ -342,7 +342,7 @@ section of this guide: https://docs.aws.amazon.com/kms/latest/developerguide/cre
         and how to view your key's ARN: https://docs.aws.amazon.com/kms/latest/developerguide/viewing-keys-console.html
 
     Store these two pieces of information in environment variables. If you plan
-    to frequently run Field-Level Encryption tests, it may be a good idea to put
+    to frequently run Client-Side Encryption tests, it may be a good idea to put
     these lines in your .bash_profile or .bashrc file. Otherwise, you can run
     them in the terminal window where you plan to run your tests.