Login if passed a secret on the command line. (#238)

Use exit codes to propagate failure to the shell.

Author: mgreisen

cli/raft.py

@@ -5,6 +5,7 @@
 import os
 import uuid
 import textwrap
+import sys
 
 import raft_sdk.raft_common
 from raft_sdk.raft_service import RaftCLI, RaftJobConfig
@@ -574,5 +575,7 @@ def main():
 if __name__ == "__main__":
     try:
         main()
+        sys.exit(0)
     except Exception as ex:
         print(ex)
+        sys.exit(1)

cli/raft_sdk/raft_deploy.py

@@ -75,10 +75,18 @@ def __init__(self, context, defaults_path, secret=None):
 
         if not secret:
             self.is_logged_in()
+        else:
+            # If we are given a secret on the command line, then we assume that
+            # we are running in some automation context and need
+            # to login this way.
+            az(f'login --service-principal -u {self.context["clientId"]} -p {secret} --tenant {self.context["tenantId"]}')
 
         az(f'account set --subscription {self.definitions.subscription}')
 
     def is_logged_in(self):
+        # If your not logged in this command will throw
+        # an exception and say in the error message
+        # that you need to login.
         az('ad signed-in-user show')
 
     def hash(self, txt):

docs/how-to-use-raft-local.md

@@ -35,7 +35,9 @@ CLI //root folder where you downloaded the CLI
 * The `storage` folder will contain all of the data produced by RAFT job runs. 
 * The `secrets` folder is a user maintained folder. </br>
   The files in this folder are the names of the secret used in the job definition file.
-  These files should not have an extension.
+  These files should not have an extension.</br>
+  **Note:** The contents of the secret file must not contain line breaks. This data is passed
+  on the docker command line. Line breaks will cause the docker command to fail. 
 
   For example if my RAFT job configuration requires a text token. 
   I can store the token in file `MyToken` under `CLI/local/secrets/MyToken` and use `MyToken`