Merge with Dev branch

.azure-devops/create-release.yml

@@ -32,7 +32,7 @@ stages:
 
     - job: 'Build_Publish_Azure_IoT_CLI_Extension'
       pool:
-        vmImage: 'ubuntu-latest'
+        vmImage: 'Ubuntu-16.04'
 
       steps:
       - task: UsePythonVersion@0
@@ -46,7 +46,7 @@ stages:
 
     - job: 'Build_Publish_Azure_CLI_Test_SDK'
       pool:
-        vmImage: 'ubuntu-latest'
+        vmImage: 'Ubuntu-16.04'
 
       steps:
       - task: UsePythonVersion@0
@@ -72,7 +72,7 @@ stages:
   - stage: 'test'
     displayName: 'Run tests'
     pool:
-      vmImage: 'ubuntu-latest'
+      vmImage: 'Ubuntu-16.04'
     dependsOn: build
     jobs:
     - job: 'testCentral'
@@ -171,7 +171,7 @@ stages:
 
       - task: GitHubRelease@0
         inputs:
-          gitHubConnection: AzIoTCLIGitHub
+          gitHubConnection: $(GithubReleaseConnection)
           repositoryName: $(Build.Repository.Name)
           action: 'create'
           target: '$(Build.SourceVersion)'

.azure-devops/merge.yml

@@ -18,7 +18,7 @@ jobs:
 
 - job: 'build_and_publish_azure_iot_cli_ext'
   pool:
-    vmImage: 'ubuntu-latest'
+    vmImage: 'Ubuntu-16.04'
 
   steps:
   - task: UsePythonVersion@0
@@ -31,7 +31,7 @@ jobs:
 
 - job: 'build_and_publish_azure_cli_test_sdk'
   pool:
-    vmImage: 'ubuntu-latest'
+    vmImage: 'Ubuntu-16.04'
 
   steps:
   - task: UsePythonVersion@0
@@ -45,7 +45,7 @@ jobs:
 - job: 'run_unit_tests_ubuntu'
   dependsOn: [ 'build_and_publish_azure_iot_cli_ext', 'build_and_publish_azure_cli_test_sdk']
   pool:
-    vmImage: 'ubuntu-latest'
+    vmImage: 'Ubuntu-16.04'
   strategy:
     matrix:
       Python36:
@@ -99,7 +99,7 @@ jobs:
 - job: 'run_style_check'
   dependsOn: ['build_and_publish_azure_iot_cli_ext', 'build_and_publish_azure_cli_test_sdk']
   pool:
-    vmImage: 'ubuntu-latest'
+    vmImage: 'Ubuntu-16.04'
 
   steps:
   - task: UsePythonVersion@0
@@ -124,7 +124,7 @@ jobs:
   dependsOn: ['build_and_publish_azure_iot_cli_ext']
   displayName: 'Evaluate IoT extension command table'
   pool:
-    vmImage: 'ubuntu-latest'
+    vmImage: 'Ubuntu-16.04'
 
   steps:
   - task: UsePythonVersion@0

.azure-devops/nightly.yml

@@ -17,7 +17,7 @@ stages:
 
     - job: 'Build_Publish_Azure_IoT_CLI_Extension'
       pool:
-        vmImage: 'ubuntu-latest'
+        vmImage: 'Ubuntu-16.04'
 
       steps:
       - task: UsePythonVersion@0
@@ -31,7 +31,7 @@ stages:
 
     - job: 'Build_Publish_Azure_CLI_Test_SDK'
       pool:
-        vmImage: 'ubuntu-latest'
+        vmImage: 'Ubuntu-16.04'
 
       steps:
       - task: UsePythonVersion@0
@@ -57,7 +57,7 @@ stages:
   - stage: 'test'
     displayName: 'Run all tests'
     pool:
-      vmImage: 'ubuntu-latest'
+      vmImage: 'Ubuntu-16.04'
     dependsOn: build
     jobs:
     - job: 'azEdge'

.pylintrc

@@ -281,7 +281,8 @@ disable=import-outside-toplevel,
         comprehension-escape,
         not-callable,
         raise-missing-from,
-        super-with-arguments
+        super-with-arguments,
+        consider-using-dict-items,
 
 # Enable the message, report, category or checker with the given id(s). You can
 # either give multiple identifier separated by comma (,) or put this option

HISTORY.rst

@@ -6,17 +6,30 @@ Release History
 0.10.14
 +++++++++++++++
 
+**IoT Central updates**
+
+* Adds support to run root/interface level device commands.
+* Adds support to get command history for root/interface level device commands.
+* The --interface-id parameter for commands "device command run" , "device command history" changed to optional.
+
 **IoT Hub updates**
 
 * Fix for "az iot hub c2d-message receive" - the command will use the "ContentEncoding" header value (which indicates the message body encoding)
   or fallback to utf-8 to decode the received message body.
 
+* Addition for "az iot hub generate-sas-token" - the command will allow offline generation of a SAS Token using a connection string.
+
+* Changes to Edge validation for set-modules and edge deployment creation:
+
+  By default only properties of system modules $edgeAgent and $edgeHub are validated against schemas installed with the IoT extension.
+  This can be disabled by using the --no-validation switch.
+
 **Azure Digital Twins updates**
 
 * Addition of the following commands
 
   * az dt reset - Preview command which deletes all data entities from the target instance (models, twins, twin relationships).
-  
+
 
 0.10.13
 +++++++++++++++
@@ -34,7 +47,7 @@ Release History
 * Public API GA update
 
   * Remove preview tag for  api-token, device, device-template, user routes. Default routes use central GA API's.
-  * Add support for preview and 1.0 routes. 
+  * Add support for preview and 1.0 routes.
   * Addition of the optional '--av' argument to specify the version of API for the requested operation.
 
 **IoT Hub updates**
@@ -102,7 +115,7 @@ For more information about IoT Hub support for AAD visit: https://docs.microsoft
 
 * Addition of the following commands
 
-  * az iot central device manual-failover - Execute a manual failover of device across multiple IoT Hubs 
+  * az iot central device manual-failover - Execute a manual failover of device across multiple IoT Hubs
   * az iot central device manual-failback - Reverts the previously executed failover command by moving the device back to it's original IoT Hub
 
 For more information about device high availability visit https://github.com/iot-for-all/iot-central-high-availability-clients#readme
@@ -138,7 +151,7 @@ For more information about device high availability visit https://github.com/iot
 **IoT Hub updates**
 
 * Improve http debug logging.
-* Fix bug related to issue #296. Adds a clause to device-identity update that allows user to update primary-key / secondary-key 
+* Fix bug related to issue #296. Adds a clause to device-identity update that allows user to update primary-key / secondary-key
   and primary-thumbprint / secondary-thumbprint values (respectively, per auth method) without needing to specify the auth_method in the update command.
 
 

azext_iot/_help.py

@@ -577,6 +577,18 @@
       text: >
         az iot hub generate-sas-token -d {device_id}
         --login 'HostName=myhub.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=12345'
+    - name: Generate an Iot Hub SAS token using an IoT Hub connection string
+      text: >
+        az iot hub generate-sas-token
+        --connection-string 'HostName=myhub.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=12345'
+    - name: Generate a Device SAS token using a Device connection string
+      text: >
+        az iot hub generate-sas-token --connection-string
+        'HostName=myhub.azure-devices.net;DeviceId=mydevice;SharedAccessKeyName=iothubowner;SharedAccessKey=12345'
+    - name: Generate a Module SAS token using a Module connection string
+      text: >
+        az iot hub generate-sas-token --connection-string
+        'HostName=myhub.azure-devices.net;DeviceId=mydevice;ModuleId=mymodule;SharedAccessKeyName=iothubowner;SharedAccessKey=12345'
 """
 
 helps[
@@ -928,6 +940,9 @@
     long-summary: |
                   Modules content is json and in the form of {"modulesContent":{...}} or {"content":{"modulesContent":{...}}}.
 
+                  By default properties of system modules $edgeAgent and $edgeHub are validated against schemas installed with the IoT extension.
+                  This can be disabled by using the --no-validation switch.
+
                   Note: Upon execution the command will output the collection of modules applied to the device.
     examples:
     - name: Test edge modules while in development by setting modules on a target device.
@@ -950,6 +965,9 @@
     long-summary: |
                   Deployment content is json and in the form of {"modulesContent":{...}} or {"content":{"modulesContent":{...}}}.
 
+                  By default properties of system modules $edgeAgent and $edgeHub are validated against schemas installed with the IoT extension.
+                  This can be disabled by using the --no-validation switch.
+
                   Edge deployments can be created with user defined metrics for on demand evaluation.
                   User metrics are json and in the form of {"queries":{...}} or {"metrics":{"queries":{...}}}.
     examples:

azext_iot/_params.py

@@ -220,6 +220,13 @@ def load_arguments(self, _):
             arg_type=get_three_state_flag(),
             help="Flag indicating edge enablement.",
         )
+        context.argument(
+            "connection_string",
+            options_list=["--connection-string", "--cs"],
+            help="Target connection string. This bypasses the IoT Hub registry and generates the SAS token directly"
+            " from the supplied symmetric key without further validation. All other command parameters aside from"
+            " duration will be ignored. Supported connection string types: Iot Hub, Device, Module."
+        )
 
     with self.argument_context("iot hub") as context:
         context.argument(

azext_iot/_validators.py

@@ -16,6 +16,7 @@ def mode2_iot_login_handler(cmd, namespace):
             login_value = args['login']
             iot_cmd_type = None
             entity_value = None
+            offline = None
 
             if 'hub_name' in args:
                 iot_cmd_type = 'IoT Hub'
@@ -24,5 +25,8 @@ def mode2_iot_login_handler(cmd, namespace):
                 iot_cmd_type = 'DPS'
                 entity_value = args['dps_name']
 
-            if not any([login_value, entity_value]):
+            if 'connection_string' in args:
+                offline = args['connection_string']
+
+            if not any([login_value, entity_value, offline]):
                 raise CLIError(error_no_hub_or_login_on_input(iot_cmd_type))