cherry-pick e0a8594 from generation

Author: azure-powershell-bot

src/Databricks/Databricks.Autorest/.gitattributes

@@ -0,0 +1 @@
+* text=auto

src/Databricks/Databricks.Autorest/.gitignore

@@ -0,0 +1,16 @@
+bin
+obj
+.vs
+generated
+internal
+exports
+tools
+custom/*.psm1
+custom/autogen-model-cmdlets
+test/*-TestResults.xml
+/*.ps1
+/*.ps1xml
+/*.psm1
+/*.snk
+/*.csproj
+/*.nuspec

src/Databricks/Databricks.Autorest/Az.Databricks.psd1

@@ -0,0 +1,24 @@
+@{
+  GUID = '8b0dec02-8816-4888-a99b-9d013881e523'
+  RootModule = './Az.Databricks.psm1'
+  ModuleVersion = '1.2.0'
+  CompatiblePSEditions = 'Core', 'Desktop'
+  Author = 'Microsoft Corporation'
+  CompanyName = 'Microsoft Corporation'
+  Copyright = 'Microsoft Corporation. All rights reserved.'
+  Description = 'Microsoft Azure PowerShell: Databricks cmdlets'
+  PowerShellVersion = '5.1'
+  DotNetFrameworkVersion = '4.7.2'
+  RequiredAssemblies = './bin/Az.Databricks.private.dll'
+  FormatsToProcess = './Az.Databricks.format.ps1xml'
+  FunctionsToExport = 'Get-AzDatabricksAccessConnector', 'Get-AzDatabricksOutboundNetworkDependenciesEndpoint', 'Get-AzDatabricksVNetPeering', 'Get-AzDatabricksWorkspace', 'New-AzDatabricksAccessConnector', 'New-AzDatabricksVNetPeering', 'New-AzDatabricksWorkspace', 'New-AzDatabricksWorkspaceProviderAuthorizationObject', 'Remove-AzDatabricksAccessConnector', 'Remove-AzDatabricksVNetPeering', 'Remove-AzDatabricksWorkspace', 'Update-AzDatabricksAccessConnector', 'Update-AzDatabricksVNetPeering', 'Update-AzDatabricksWorkspace', '*'
+  AliasesToExport = '*'
+  PrivateData = @{
+    PSData = @{
+      Tags = 'Azure', 'ResourceManager', 'ARM', 'PSModule', 'Databricks'
+      LicenseUri = 'https://aka.ms/azps-license'
+      ProjectUri = 'https://github.com/Azure/azure-powershell'
+      ReleaseNotes = ''
+    }
+  }
+}

src/Databricks/Databricks.Autorest/LiveTests/TestLiveScenarios.ps1

@@ -273,4 +273,4 @@ directive:
           - ManagedResourceGroupId
         labels:
           ManagedResourceGroupId: Managed Resource Group ID
-```
+```

src/Databricks/Databricks.Autorest/Properties/AssemblyInfo.cs

@@ -89,7 +89,7 @@ if(-not $Debugger) {
   $null = Remove-Item -Recurse -ErrorAction SilentlyContinue -Path (Join-Path $binFolder 'Debug'), (Join-Path $binFolder 'Release')
 }
 
-$dll = Join-Path $PSScriptRoot 'bin\Az.Databricks.private.dll'
+$dll = Join-Path $PSScriptRoot 'bin/Az.Databricks.private.dll'
 if(-not (Test-Path $dll)) {
   Write-Error "Unable to find output assembly in '$binFolder'."
 }
@@ -98,7 +98,7 @@ if(-not (Test-Path $dll)) {
 $null = Import-Module -Name $dll
 
 $modulePaths = $dll
-$customPsm1 = Join-Path $PSScriptRoot 'custom\Az.Databricks.custom.psm1'
+$customPsm1 = Join-Path $PSScriptRoot 'custom/Az.Databricks.custom.psm1'
 if(Test-Path $customPsm1) {
   $modulePaths = @($dll, $customPsm1)
 }
@@ -170,8 +170,8 @@ if (Test-Path (Join-Path $PSScriptRoot 'generate-portal-ux.ps1'))
 }
 
 if (-not $DisableAfterBuildTasks){
-  $afterBuildTasksPath = Join-Path $PSScriptRoot ''
-  $afterBuildTasksArgs = ConvertFrom-Json 'true' -AsHashtable
+  $afterBuildTasksPath = Join-Path $PSScriptRoot '../../../tools/BuildScripts/AdaptAutorestModule.ps1'
+  $afterBuildTasksArgs = ConvertFrom-Json '{"SubModuleName":"Databricks","ModuleRootName":"$(root-module-name)"}' -AsHashtable
   if(Test-Path -Path $afterBuildTasksPath -PathType leaf){
     Write-Host -ForegroundColor Green 'Running after build tasks...'
     . $afterBuildTasksPath @afterBuildTasksArgs

src/Databricks/Databricks.Autorest/README.md

@@ -22,8 +22,8 @@ function CreateModelCmdlet {
         return
     }
 
-    $ModelCsPath = Join-Path (Join-Path $PSScriptRoot 'generated\api') 'Models'
-    $OutputDir = Join-Path $PSScriptRoot 'custom\autogen-model-cmdlets'
+    $ModelCsPath = Join-Path (Join-Path $PSScriptRoot 'generated/api') 'Models'
+    $OutputDir = Join-Path $PSScriptRoot 'custom/autogen-model-cmdlets'
     $null = New-Item -ItemType Directory -Force -Path $OutputDir
     if (''.length -gt 0) {
         $ModuleName = ''

src/Databricks/Databricks.Autorest/build-module.ps1

@@ -1,9 +1,9 @@
 # region Generated 
   # Load the private module dll
-  $null = Import-Module -PassThru -Name (Join-Path $PSScriptRoot '..\bin\Az.Databricks.private.dll')
+  $null = Import-Module -PassThru -Name (Join-Path $PSScriptRoot '../bin/Az.Databricks.private.dll')
 
   # Load the internal module
-  $internalModulePath = Join-Path $PSScriptRoot '..\internal\Az.Databricks.internal.psm1'
+  $internalModulePath = Join-Path $PSScriptRoot '../internal/Az.Databricks.internal.psm1'
   if(Test-Path $internalModulePath) {
     $null = Import-Module -Name $internalModulePath
   }

src/Databricks/Databricks.Autorest/create-model-cmdlets.ps1

@@ -1,5 +1,5 @@
 # Custom
-This directory contains custom implementation for non-generated cmdlets for the `Az.Databricks` module. Both scripts (`.ps1`) and C# files (`.cs`) can be implemented here. They will be used during the build process in `build-module.ps1`, and create cmdlets into the `..\exports` folder. The only generated file into this folder is the `Az.Databricks.custom.psm1`. This file should not be modified.
+This directory contains custom implementation for non-generated cmdlets for the `Az.Databricks` module. Both scripts (`.ps1`) and C# files (`.cs`) can be implemented here. They will be used during the build process in `build-module.ps1`, and create cmdlets into the `../exports` folder. The only generated file into this folder is the `Az.Databricks.custom.psm1`. This file should not be modified.
 
 ## Info
 - Modifiable: yes
@@ -15,10 +15,10 @@ For C# cmdlets, they are compiled with the rest of the generated low-level cmdle
 For script cmdlets, these are loaded via the `Az.Databricks.custom.psm1`. Then, during the build process, this module is loaded and processed in the same manner as the C# cmdlets. The fundamental difference is the script cmdlets use the `ParameterSetName` attribute and C# cmdlets do not. To create a script cmdlet variant of a generated cmdlet, simply decorate all parameters in the script with the new `ParameterSetName` in the `Parameter` attribute. This will appropriately treat each parameter set as a separate variant when processed to be exported during the build.
 
 ## Purpose
-This allows the modules to have cmdlets that were not defined in the REST specification. It also allows combining logic using generated cmdlets. This is a level of customization beyond what can be done using the [readme configuration options](https://github.com/Azure/autorest/blob/master/docs/powershell/options.md) that are currently available. These custom cmdlets are then referenced by the cmdlets created at build-time in the `..\exports` folder.
+This allows the modules to have cmdlets that were not defined in the REST specification. It also allows combining logic using generated cmdlets. This is a level of customization beyond what can be done using the [readme configuration options](https://github.com/Azure/autorest/blob/master/docs/powershell/options.md) that are currently available. These custom cmdlets are then referenced by the cmdlets created at build-time in the `../exports` folder.
 
 ## Usage
-The easiest way currently to start developing custom cmdlets is to copy an existing cmdlet. For C# cmdlets, copy one from the `generated/cmdlets` folder. For script cmdlets, build the project using `build-module.ps1` and copy one of the scripts from the `..\exports` folder. After that, if you want to add new parameter sets, follow the guidelines in the `Details` section above. For implementing a new cmdlets, at minimum, please keep these parameters:
+The easiest way currently to start developing custom cmdlets is to copy an existing cmdlet. For C# cmdlets, copy one from the `generated/cmdlets` folder. For script cmdlets, build the project using `build-module.ps1` and copy one of the scripts from the `../exports` folder. After that, if you want to add new parameter sets, follow the guidelines in the `Details` section above. For implementing a new cmdlets, at minimum, please keep these parameters:
 - Break
 - DefaultProfile
 - HttpPipelineAppend
@@ -36,6 +36,6 @@ For processing the cmdlets, we've created some additional attributes:
 - `Microsoft.Azure.PowerShell.Cmdlets.Databricks.DoNotExportAttribute`
   - Used in C# and script cmdlets to suppress creating an exported cmdlet at build-time. These cmdlets will *not be exposed* by `Az.Databricks`.
 - `Microsoft.Azure.PowerShell.Cmdlets.Databricks.InternalExportAttribute`
-  - Used in C# cmdlets to route exported cmdlets to the `..\internal`, which are *not exposed* by `Az.Databricks`. For more information, see [README.md](..\internal/README.md) in the `..\internal` folder.
+  - Used in C# cmdlets to route exported cmdlets to the `../internal`, which are *not exposed* by `Az.Databricks`. For more information, see [README.md](../internal/README.md) in the `../internal` folder.
 - `Microsoft.Azure.PowerShell.Cmdlets.Databricks.ProfileAttribute`
   - Used in C# and script cmdlets to define which Azure profiles the cmdlet supports. This is only supported for Azure (`--azure`) modules.

src/Databricks/Databricks.Autorest/custom/Az.Databricks.custom.psm1

@@ -490,6 +490,18 @@ function Update-AzDatabricksWorkspace {
             {
                 $workspace.DefaultStorageFirewall = $DefaultStorageFirewall
             }
+            if ($hasAccessConnectorId)
+            {
+                $workspace.AccessConnectorId = $AccessConnectorId
+            }
+            if ($hasAccessConnectorIdentityType)
+            {
+                $workspace.AccessConnectorIdentityType = $AccessConnectorIdentityType
+            }
+            if ($hasAccessConnectorUserAssignedIdentityId)
+            {
+                $workspace.AccessConnectorUserAssignedIdentityId = $AccessConnectorUserAssignedIdentityId
+            }
             if ($hasAsJob) {
                 $PSBoundParameters.Add('AsJob', $true)
             }

src/Databricks/Databricks.Autorest/custom/README.md

@@ -1,6 +1,6 @@
 ---
 Module Name: Az.Databricks
-Module Guid: b453c0c1-7867-4fa1-9fd0-0cf8f6c6959c
+Module Guid: 8b0dec02-8816-4888-a99b-9d013881e523
 Download Help Link: https://learn.microsoft.com/powershell/module/az.databricks
 Help Version: 1.0.0.0
 Locale: en-US

src/Databricks/Databricks.Autorest/custom/Update-AzDatabricksWorkspace.ps1

@@ -1,5 +1,5 @@
 # Docs
-This directory contains the documentation of the cmdlets for the `Az.Databricks` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overridden on regeneration*. To update documentation examples, please use the `..\examples` folder.
+This directory contains the documentation of the cmdlets for the `Az.Databricks` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overridden on regeneration*. To update documentation examples, please use the `../examples` folder.
 
 ## Info
 - Modifiable: no
@@ -8,4 +8,4 @@ This directory contains the documentation of the cmdlets for the `Az.Databricks`
 - Packaged: yes
 
 ## Details
-The process of documentation generation loads `Az.Databricks` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
+The process of documentation generation loads `Az.Databricks` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `../exports` folder. Additionally, when writing custom cmdlets in the `../custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `../examples` folder.

src/Databricks/Databricks.Autorest/help/Az.Databricks.md renamed to src/Databricks/Databricks.Autorest/docs/Az.Databricks.md

@@ -22,7 +22,7 @@ if(-not $Isolated) {
   return
 }
 
-$dll = Join-Path $PSScriptRoot 'bin\Az.Databricks.private.dll'
+$dll = Join-Path $PSScriptRoot 'bin/Az.Databricks.private.dll'
 if(-not (Test-Path $dll)) {
   Write-Error "Unable to find output assembly in '$binFolder'."
 }

src/Databricks/Databricks.Autorest/help/Get-AzDatabricksAccessConnector.md renamed to src/Databricks/Databricks.Autorest/docs/Get-AzDatabricksAccessConnector.md

@@ -1,3 +1,3 @@
 {
-  "generate_Id": "398839ec-04a9-4252-a411-806dd21f8804"
+  "generate_Id": "6f7c2bf0-9645-4005-9477-66b1bedbec46"
 }