merge master

.github/sla.yml

@@ -84,3 +84,18 @@
       subject: "Action Required: Please respond to issue ${URL}"
       to: ${ASSIGNEE}
       cc: vscswagger@microsoft.com
+
+- scheduleTask:	
+    action: sendEmail	
+    scope: pull_request	
+    name: "send email given path change"	
+    trigger:	
+      - path	
+    args:	
+      message: '<p>You have just completed the first step towards onboarding your API change to the Compute Management library.</p><p>We (<a href="mailto:cplatsdkdev@microsoft.com">the CPlatSDK/PowerShell team</a>) manage the Compute library&#39;s API and SDK for the following clients: Swagger (REST api), .NET SDK, and Azure PowerShell.</p><p>You&#39;ve just opened a PR making changes in the Compute Management Library&#39;s path of the Azure REST Api Specs repository.</p><p>What&#39;s next?</p><ol type="1"><li value="1">Your api specs need to be reviewed and approved by us and the ARM team</li><li>Make sure you that can generate the .NET SDK from your API specs using the Autorest tool (<a href="https://dev.azure.com/msazure/AzureWiki/_wiki/wikis/AzureWiki.wiki/73168/SDK-(.NET)?anchor=how-to-generate-the-sdk%3F">NET SDK autogeneration</a>)</li><li>While your specs are getting reviewed, you should be working on the .NET SDK. (<a href="https://github.com/Azure/azure-sdk-for-net/">SDK repo</a>)</li><ol type="a"><li value="1">Once you generate the .NET SDK, you need to create the SDK tests and perform recordings and playbacks. (<a href="https://dev.azure.com/msazure/AzureWiki/_wiki/wikis/AzureWiki.wiki/73168/SDK-(.NET)?anchor=how-to-set-up-testing-and-record-tests%3F">NET SDK testing</a>)</li><li>With the newly generated SDK with tests, you can make a pull request to the SDK repository.<br /> Make sure to add a reference to your Swagger pull request in the comments.</li></ol><li>[If applicable] At this stage, you can get started on the Azure PowerShell part.<ol type="a"><li value="1">All you need to do is send a design doc of any change/new Azure PowerShell cmdlet related to your api by creating an issue with your design <a href="https://github.com/Azure/azure-powershell-cmdlet-review-pr/issues">here</a>.<br>Then, send an email to <a href="mailto:azdevxpsdr@microsoft.com">azdevxpsdr@microsoft.com</a> with the issue number and cc our dl (<a href="mailto:cplatsdkdev@microsoft.com">cplatsdkdev@microsoft.com</a>) on the email, so we can leave comments on your design doc as well.</li><li>Once your PowerShell cmdlet design has been approved, send an email to&nbsp;<a href="mailto:cplatsdkdev@microsoft.com?subject=PowerShell%20Design%20Review%20Approved">our team</a><br /> We will implement and test the PowerShell cmdlet following the approved design. We will then make a pull request to the appropriate repository</li></ol><li>[If applicable] You can also get started on any Azure CLI module or extension for your API change. Find more information about next steps on that process <a href="https://github.com/Azure/azure-cli/blob/dev/doc/onboarding_guide.md">here</a>.</li></ol><hr><ul type="disc"><li>To view the full CPlat SDK PowerShell API onboarding wiki, please visit <a href="https://aka.ms/cplatsdk">aka.ms/cplatsdk</a></li></ul><p>This email was automatically sent. Please send an email to&nbsp;<a href="mailto:cplatsdkdev@microsoft.com">cplatsdkdev@microsoft.com</a>&nbsp;if you have any questions.</p>'	
+      targetPaths:	
+        - "specification/compute/resource-manager/Microsoft.Compute/**"	
+      subject: "[Action Required] CPlat Swagger Pull Request opened: Next steps"	
+      to: ${AUTHOR}
+      cc:
+        - cplatsdkdev@microsoft.com

CODEOWNERS

@@ -65,7 +65,7 @@
 /specification/service-map/ @daveirwin1
 /specification/servicebus/ @sazeesha @v-ajnava
 /specification/servicefabric/ @juhacket @samedder
-/specification/sql/ @dnayantara @jaredmoo @nathannfan
+/specification/sql/ @jaredmoo @jamestao
 /specification/storage/ @blueww @jasonyang-msft @xiaonlimsft @kasobol-msft
 /specification/storageimportexport/ @leoz-ms
 /specification/storagesync/ @ankushbindlish2

custom-words.txt

@@ -118,12 +118,14 @@ aspnet
 asyncinfo
 asyncoperation
 atascada
+Auditd
 australiaeast
 australiasoutheast
 authenticatable
 Authenticode
 authorityURL
 authorizationrules
+authpriv
 authprovider
 authproviders
 authsettings
@@ -149,6 +151,7 @@ autoscaling
 Avro
 avrodeflate
 AZFW
+AZNB
 azns
 azpkg
 azureaccounts
@@ -239,6 +242,7 @@ brazilsouth
 browsable
 bruceper
 Bsaling
+Burstable
 BYOC
 BYOK
 BYOL
@@ -277,6 +281,7 @@ CIDR
 CIDRs
 CIFS
 ciphertext
+CISCOASA
 claimCondition
 claimType
 clfs
@@ -1023,6 +1028,7 @@ nopublicipaddresses
 northcentralus
 northeurope
 nostore
+notebookapis
 notificationchannels
 notificationhubs
 notstarted
@@ -1480,6 +1486,7 @@ stateful
 staticsite
 statusdir
 stderror
+stdev
 stopresize
 stopword
 stopwords
@@ -1572,6 +1579,7 @@ testall
 testallroutes
 testnew
 testnewroute
+testpl
 testresultfile
 textanalytics
 TFIDF
@@ -1590,6 +1598,8 @@ tombstoned
 toolchain
 toolset
 tooltips
+topqueries
+topquery
 traceback
 traceroute
 trafficmanager
@@ -1607,6 +1617,7 @@ TSVE
 Turbonomic
 Txns
 Typeless
+typeperf
 UEBA
 Uint
 uksouth
@@ -1681,6 +1692,7 @@ userpreference
 usersetting
 usermanaged
 USQL
+UUCP
 VAIDK
 varbinary
 varchar
@@ -1840,4 +1852,8 @@ azureADMetrics
 sparkr
 ambari
 dotnetspark
-FDID
+FDID
+watchlists
+Watchlists
+watchlist
+Watchlist