Revert from Ruby 2.7.4 to 2.7.2

Author: sureshc

.ruby-version

@@ -1 +1 @@
-2.7.4
+2.7.2

README.md

@@ -25,14 +25,14 @@ doc.
   production.
 
 ### Prerequisites
-You need to install Ruby 2.7.4 to build and/or run the Ruby lambda functions
+Use `rbenv` to install Ruby 2.7.2 to build and/or run the Ruby lambda functions
 (`javabuilder-authorizer` and `api-gateway-routes`).
-[rbenv](https://github.com/rbenv/rbenv) is a useful tool for installing Ruby and managing
-multiple versions. Follow the instructions
+[rbenv](https://github.com/rbenv/rbenv) is required for installing Ruby and managing
+multiple versions of Ruby on a single development environment. Follow the instructions
 [here](https://github.com/rbenv/rbenv#installing-ruby-versions) to use rbenv to install a
 new Ruby version. You may need to also install
 [ruby-build](https://github.com/rbenv/ruby-build#readme) to get the latest Ruby versions.
-The `.ruby-version` file sets the local Ruby version for javabuilder to be 2.7.4.
+The `.ruby-version` file sets the local Ruby version for javabuilder to be 2.7.2
 
 ## Deploying Production Javabuilder
 To deploy Javabuilder to production, see the

javabuilder-authorizer/README.md

@@ -5,6 +5,6 @@ This lambda function is an
 It expects a JWT token to be sent in an Authorization header in the standard format 
 `Authorization: Bearer <token>`.
 
-You must be running ruby version 2.7.4 for the upload to work properly. The lambda 
+You must be running ruby version 2.7.2 for the upload to work properly. The lambda 
 expects the gems to be in `vendor\bundle\ruby\2.7.0\*`. You may be able to manually
 rename the `2.7.0` folder to workaround installing a different ruby version.