Updated: June 29, 2015
The Get Package operation retrieves a cloud service package for a deployment and stores the package files in Microsoft Azure Blob storage.
The following package files are placed in storage:
Service configuration file - The cloud service configuration file (.cscfg) provides configuration settings for the cloud service and individual roles, including the number of role instances.
Service package - The service package (.cspkg) contains the application code and the service definition file.
For more information about using the cloud service package, see How to Create and Deploy a Cloud Service.
For more information about using Blob Storage, see How to use the Microsoft Azure Blob Storage Service in .NET and Naming and Referencing Containers, Blobs, and Metadata.
The Get Package request may be specified as follows. Replace <subscription-id> with the subscription ID, <cloudservice-name> with the name of the cloud service, <deployment-slot> with staging or production, or <deployment-name> with the name of the deployment.
You must make sure that the request that is made to the management service is secure. For additional details, see Authenticating Service Management Requests.
Required. Specifies the URI of the container to which the packages will be saved.
Optional. Specifies whether an existing package in the storage container should be overwritten. If true the packages with the same names under the specified storage container will be overwritten; otherwise false.
The following table describes the request headers.
Required. Specifies the version of the operation to use for this request. This header should be set to 2012-03-01 or higher. For more information about versioning headers, see Service Management Versioning.
Required. Must be set to 0.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 202 (Accepted). For information about status codes, see Service Management Status and Error Codes.
The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
A value that uniquely identifies a request made against the management service.