You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We will use dotnet project template [Azure.Template](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/template/Azure.Template) to automatically create the project.
64
64
65
-
You can run `eng\scripts\automation\Invoke-DataPlaneGenerateSDKPackage.ps1` to generate the starting SDK client library package directly as following:
65
+
You can run `eng\scripts\automation\Invoke-AutorestDataPlaneGenerateSDKPackage.ps1` to generate the starting SDK client library package directly as following:
-`<package name>` - Should be the name of the shipping package, or an abbreviation that distinguishes the given shipping artifact for the given service. It will be `Azure.<group>.<service>`, e.g. Azure.IoT.DeviceUpdate
18
18
19
19
## Create sdk package
20
-
21
-
We will use the Azure SDK template [Azure.Template](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/template/Azure.Template) to create the initial project skeleton.
20
+
21
+
We will use the Azure SDK template [Azure.Template](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/template/Azure.Template) to create the initial project skeleton for SDKs generated from TypeSpec.
22
22
23
23
You can run `eng\scripts\automation\Invoke-TypeSpecDataPlaneGenerateSDKPackage.ps1` to generate the starting SDK client library package directly as following:
Copy file name to clipboardExpand all lines: eng/scripts/automation/Invoke-AutorestDataPlaneGenerateSDKPackage.ps1
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
#Requires -Version7.0
2
2
<#
3
3
.SYNOPSIS
4
-
script for creating a getting started project in a branch of `azure-sdk-for-net` repo.
4
+
script for creating a getting started project in a branch of `azure-sdk-for-net` repo for SDKs generated from swagger.
5
5
6
6
.PARAMETERservice
7
7
The Azure client service directory name. ie. purview. It equals to the name of the directory in the specification folder of the azure-rest-api-specs repo that contains the REST API definition file.
@@ -13,7 +13,7 @@ The SDK package namespace. This value will also provide the name for the shipped
13
13
The address of the root directory of sdk repo. e.g. /home/azure-sdk-for-net
14
14
15
15
.PARAMETERinputfiles
16
-
The address of the Open API spec files, separated by semicolon if there is more than one file.
16
+
The address of the Open API spec files, separated by semicolon if there is more than one file.
17
17
The Open API spec file can be local file, or the web address of the file in the `azure-rest-api-specs` repo.
18
18
When pointing to a local file, make sure to use **absolute path**, i.e. /home/swagger/compute.json.
19
19
When pointing to a file in the `azure-rest-api-specs` repo, make sure to include the commit id in the URI, i.e. `https://github.com/Azure/azure-rest-api-specs/blob/73a0fa453a93bdbe8885f87b9e4e9fef4f0452d0/specification/webpubsub/data-plane/WebPubSub/stable/2021-10-01/webpubsub.json`. This ensures that you can choose the time to upgrade to new swagger file versions.
@@ -31,10 +31,10 @@ The key to use if your library supports **Azure Key Credential** authentication.
0 commit comments