/** * PLEASE DO NOT REMOVE - USED FOR CONVERTER METRICS * Generated by package: @autorest/openapi-to-typespec * Parameters used: * isFullCompatible: false * guessResourceKey: false * Version: 0.11.14 * Date: 2026-04-29T21:30:26.110Z */ import "@typespec/rest"; import "@typespec/http"; import "@typespec/openapi"; import "@azure-tools/typespec-azure-core"; import "./routes.tsp"; using TypeSpec.Http; using TypeSpec.Versioning; using TypeSpec.OpenAPI; using Azure.Core; /** * Device Update for IoT Hub is an Azure service that enables customers to publish updates for their IoT devices to the cloud, and then deploy that update to their devices (approve updates to groups of devices managed and provisioned in IoT Hub). It leverages the proven security and reliability of the Windows Update platform, optimized for IoT devices. It works globally and knows when and how to update devices, enabling customers to focus on their business goals and let Device Update for IoT Hub handle the updates. */ @useAuth(AzureAuth) @service(#{ title: "DeviceUpdateClient" }) @versioned(Versions) @server( "https://{endpoint}", "Device Update for IoT Hub is an Azure service that enables customers to publish updates for their IoT devices to the cloud, and then deploy that update to their devices (approve updates to groups of devices managed and provisioned in IoT Hub). It leverages the proven security and reliability of the Windows Update platform, optimized for IoT devices. It works globally and knows when and how to update devices, enabling customers to focus on their business goals and let Device Update for IoT Hub handle the updates.", { /** * The Device Update for IoT Hub account endpoint (hostname only, no protocol). */ @extension("x-ms-parameter-grouping", #{ name: "account-options" }) @extension("x-ms-parameter-location", "client") @format("url") endpoint: string, } ) namespace DeviceUpdateClient; /** * Azure Active Directory OAuth2 Flow. * * Defined as an `alias` (not a `model`) so the `@azure-tools/typespec-autorest` * emitter does not emit it under `definitions/` (which would trigger LintDiff * `XmsEnumValidation` (R2018) on the synthetic inner `type: ["oauth2"]` enum * the OAuth2Auth template produces). The flow itself is still emitted under * `securityDefinitions/`, just under the template-derived key `OAuth2Auth` * instead of `azure_auth`. This is a cosmetic, swagger-only change with no * impact on the OAuth2 wire flow, scopes, or authorization URL. */ alias AzureAuth = OAuth2Auth<[ { type: OAuth2FlowType.implicit; authorizationUrl: "https://login.microsoftonline.com/common/oauth2/authorize"; scopes: ["https://api.adu.microsoft.com/.default"]; } ]>; /** * The available API versions. */ enum Versions { /** * The 2022-10-01 API version. */ v2022_10_01: "2022-10-01", }