gcloud: Wed Mar 6 09:53:10 UTC 2024

gcloud/transfer/agents/install

@@ -8,7 +8,14 @@ SYNOPSIS
         [--logs-directory=LOGS_DIRECTORY; default="/tmp"]
         [--memlock-limit=MEMLOCK_LIMIT; default=64000000]
         [--mount-directories=[MOUNT-DIRECTORIES,...]] [--proxy=PROXY]
-        [--s3-compatible-mode] [GCLOUD_WIDE_FLAG ...]
+        [--s3-compatible-mode]
+        [--hdfs-namenode-uri=HDFS_NAMENODE_URI --hdfs-username=HDFS_USERNAME
+          --hdfs-data-transfer-protection=HDFS_DATA_TRANSFER_PROTECTION]
+        [--kerberos-config-file=KERBEROS_CONFIG_FILE
+          --kerberos-keytab-file=KERBEROS_KEYTAB_FILE
+          --kerberos-user-principal=KERBEROS_USER_PRINCIPAL
+          --kerberos-service-principal=KERBEROS_SERVICE_PRINCIPAL]
+        [GCLOUD_WIDE_FLAG ...]
 
 DESCRIPTION
     Install Transfer Service agents to enable you to transfer data to or from
@@ -39,7 +46,7 @@ REQUIRED FLAGS
         creating transfer jobs, the agent pool parameter will determine which
         agents are activated.
 
-OPTIONAL FLAGS
+FLAGS
      --count=COUNT
         Specify the number of agents to install on your current machine. System
         requirements: 8 GB of memory and 4 CPUs per agent.
@@ -120,6 +127,43 @@ OPTIONAL FLAGS
 
             AWS_ACCESS_KEY_ID="id" AWS_SECRET_ACCESS_KEY="secret" gcloud transfer agents install --s3-compatible-mode
 
+HDFS FLAGS
+     --hdfs-namenode-uri=HDFS_NAMENODE_URI
+        A URI representing an HDFS cluster including a schema, namenode, and
+        port. Examples: "rpc://my-namenode:8020", "http://my-namenode:9870".
+
+        Use "http" or "https" for WebHDFS. If no schema is provided, the CLI
+        assumes native "rpc". If no port is provided, the default is 8020 for
+        RPC, 9870 for HTTP, and 9871 for HTTPS. For example, the input
+        "my-namenode" becomes "rpc://my-namenode:8020".
+
+     --hdfs-username=HDFS_USERNAME
+        Username for connecting to an HDFS cluster with simple auth.
+
+     --hdfs-data-transfer-protection=HDFS_DATA_TRANSFER_PROTECTION
+        Client-side quality of protection setting for Kerberized clusters.
+        Client-side QOP value cannot be more restrictive than the server-side
+        QOP value. HDFS_DATA_TRANSFER_PROTECTION must be one of:
+        authentication, integrity, privacy.
+
+Kerberos FLAGS
+     --kerberos-config-file=KERBEROS_CONFIG_FILE
+        Path to Kerberos config file.
+
+     --kerberos-keytab-file=KERBEROS_KEYTAB_FILE
+        Path to a Keytab file containing the user principal specified with the
+        --kerberos-user-principal flag.
+
+     --kerberos-user-principal=KERBEROS_USER_PRINCIPAL
+        Kerberos user principal to use when connecting to an HDFS cluster via
+        Kerberos auth.
+
+     --kerberos-service-principal=KERBEROS_SERVICE_PRINCIPAL
+        Kerberos service principal to use, of the form "<primary>/<instance>".
+        Realm is mapped from your Kerberos config. Any supplied realm is
+        ignored. If not passed in, it will default to "hdfs/<namenode_fqdn>"
+        (fqdn = fully qualified domain name).
+
 GCLOUD WIDE FLAGS
     These flags are available to all commands: --access-token-file, --account,
     --billing-project, --configuration, --flags-file, --flatten, --format,