Skip to content

Commit 160c287

Browse files
feat(androiddeviceprovisioning): update the api
#### androiddeviceprovisioning:v1 The following keys were added: - schemas.ClaimDeviceRequest.properties.configurationId (Total Keys: 2) - schemas.PartnerClaim.properties.configurationId (Total Keys: 2)
1 parent 5779a44 commit 160c287

File tree

2 files changed

+17
-5
lines changed

2 files changed

+17
-5
lines changed

‎docs/dyn/androiddeviceprovisioning_v1.partners.devices.html‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -124,6 +124,7 @@ <h3>Method Details</h3>
124124
The object takes the form of:
125125

126126
{ # Request message to claim a device on behalf of a customer.
127+
&quot;configurationId&quot;: &quot;A String&quot;, # Optional. The unique identifier of the configuration (internally known as profile) to set for the section.
127128
&quot;customerId&quot;: &quot;A String&quot;, # The ID of the customer for whom the device is being claimed.
128129
&quot;deviceIdentifier&quot;: { # Encapsulates hardware and product IDs to identify a manufactured device. To understand requirements on identifier sets, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. Required. The device identifier of the device to claim.
129130
&quot;chromeOsAttestedDeviceId&quot;: &quot;A String&quot;, # An identifier provided by OEMs, carried through the production and sales process. Only applicable to Chrome OS devices.
@@ -142,7 +143,7 @@ <h3>Method Details</h3>
142143
&quot;googleWorkspaceCustomerId&quot;: &quot;A String&quot;, # The Google Workspace customer ID.
143144
&quot;preProvisioningToken&quot;: &quot;A String&quot;, # Optional. Must and can only be set for Chrome OS devices.
144145
&quot;sectionType&quot;: &quot;A String&quot;, # Required. The section type of the device&#x27;s provisioning record.
145-
&quot;simlockProfileId&quot;: &quot;A String&quot;, # Optional. Must and can only be set when DeviceProvisioningSectionType is SECTION_TYPE_SIM_LOCK. The unique identifier of the SimLock profile.
146+
&quot;simlockProfileId&quot;: &quot;A String&quot;, # Optional.
146147
}
147148

148149
x__xgafv: string, V1 error format.
@@ -171,6 +172,7 @@ <h3>Method Details</h3>
171172
{ # Request to claim devices asynchronously in batch. Claiming a device adds the device to zero-touch enrollment and shows the device in the customer&#x27;s view of the portal.
172173
&quot;claims&quot;: [ # Required. A list of device claims.
173174
{ # Identifies one claim request.
175+
&quot;configurationId&quot;: &quot;A String&quot;, # Optional. The unique identifier of the configuration (internally known as profile) to set for the section.
174176
&quot;customerId&quot;: &quot;A String&quot;, # The ID of the customer for whom the device is being claimed.
175177
&quot;deviceIdentifier&quot;: { # Encapsulates hardware and product IDs to identify a manufactured device. To understand requirements on identifier sets, read [Identifiers](https://developers.google.com/zero-touch/guides/identifiers). # Required. Required. Device identifier of the device.
176178
&quot;chromeOsAttestedDeviceId&quot;: &quot;A String&quot;, # An identifier provided by OEMs, carried through the production and sales process. Only applicable to Chrome OS devices.
@@ -189,7 +191,7 @@ <h3>Method Details</h3>
189191
&quot;googleWorkspaceCustomerId&quot;: &quot;A String&quot;, # The Google Workspace customer ID.
190192
&quot;preProvisioningToken&quot;: &quot;A String&quot;, # Optional. Must and can only be set for Chrome OS devices.
191193
&quot;sectionType&quot;: &quot;A String&quot;, # Required. The section type of the device&#x27;s provisioning record.
192-
&quot;simlockProfileId&quot;: &quot;A String&quot;, # Optional. Must and can only be set when DeviceProvisioningSectionType is SECTION_TYPE_SIM_LOCK. The unique identifier of the SimLock profile.
194+
&quot;simlockProfileId&quot;: &quot;A String&quot;, # Optional.
193195
},
194196
],
195197
}

‎googleapiclient/discovery_cache/documents/androiddeviceprovisioning.v1.json‎

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -851,13 +851,18 @@
851851
}
852852
}
853853
},
854-
"revision": "20231021",
854+
"revision": "20231029",
855855
"rootUrl": "https://androiddeviceprovisioning.googleapis.com/",
856856
"schemas": {
857857
"ClaimDeviceRequest": {
858858
"description": "Request message to claim a device on behalf of a customer.",
859859
"id": "ClaimDeviceRequest",
860860
"properties": {
861+
"configurationId": {
862+
"description": "Optional. The unique identifier of the configuration (internally known as profile) to set for the section.",
863+
"format": "int64",
864+
"type": "string"
865+
},
861866
"customerId": {
862867
"description": "The ID of the customer for whom the device is being claimed.",
863868
"format": "int64",
@@ -894,7 +899,7 @@
894899
"type": "string"
895900
},
896901
"simlockProfileId": {
897-
"description": "Optional. Must and can only be set when DeviceProvisioningSectionType is SECTION_TYPE_SIM_LOCK. The unique identifier of the SimLock profile.",
902+
"description": "Optional. ",
898903
"format": "int64",
899904
"type": "string"
900905
}
@@ -1709,6 +1714,11 @@
17091714
"description": "Identifies one claim request.",
17101715
"id": "PartnerClaim",
17111716
"properties": {
1717+
"configurationId": {
1718+
"description": "Optional. The unique identifier of the configuration (internally known as profile) to set for the section.",
1719+
"format": "int64",
1720+
"type": "string"
1721+
},
17121722
"customerId": {
17131723
"description": "The ID of the customer for whom the device is being claimed.",
17141724
"format": "int64",
@@ -1745,7 +1755,7 @@
17451755
"type": "string"
17461756
},
17471757
"simlockProfileId": {
1748-
"description": "Optional. Must and can only be set when DeviceProvisioningSectionType is SECTION_TYPE_SIM_LOCK. The unique identifier of the SimLock profile.",
1758+
"description": "Optional. ",
17491759
"format": "int64",
17501760
"type": "string"
17511761
}

0 commit comments

Comments
 (0)