SERVER-11995 Have authSchemaUpgrade sent to a mongos upgrade auth schema everywhere.

In particular, sends the commands to each shard, as well as performing the upgrade on the
config servers.

Also, allow user to specify maximum number of upgrade steps to take on any given shard.
Defaults to "as many as necessary".

To achieve these changes, separate implementations of the upgrade command are provided to
mongos and mognod.

1 files changed, 7 insertions, 2 deletions

diff --git a/src/mongo/db/auth/user_management_commands_parser.h b/src/mongo/db/auth/user_management_commands_parser.h
index befeb2731ba..0f0a9696251 100644
--- a/src/mongo/db/auth/user_management_commands_parser.h
+++ b/src/mongo/db/auth/user_management_commands_parser.h
@@ -26,6 +26,8 @@
 *    it in the license file.
 */
 
+#pragma once
+
 #include <string>
 #include <vector>
 
@@ -180,11 +182,14 @@ namespace auth {
                                                 BSONObj* parsedWriteConcern);
 
     /**
-     * Takes a command object describing an invocation of the "authSchemaUpgradeStep" command and
-     * parses out the write concern.
+     * Takes a command object describing an invocation of the "authSchemaUpgrade" command and
+     * parses out the write concern, maximum steps to take and whether or not shard servers should
+     * also be upgraded, in the sharded deployment case.
      */
     Status parseAuthSchemaUpgradeStepCommand(const BSONObj& cmdObj,
                                              const std::string& dbname,
+                                             int* maxSteps,
+                                             bool* shouldUpgradeShards,
                                              BSONObj* parsedWriteConcern);
     /**
      * Parses the privileges described in "privileges" into a vector of Privilege objects.