Repository navigation
Bump Azure.ResourceManager.Resources from 1.0.0-preview.1 to 1.12.0 - #19
Open
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: Azure.ResourceManager.Resources dependency-version: 1.12.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Azure.ResourceManager.Resources from 1.0.0-preview.1 to 1.12.0.
Release notes
Sourced from Azure.ResourceManager.Resources's releases.
1.10.0
1.10.0 (2026-10-05)
Features Added
Azure.Monitor.OpenTelemetry.Exporter.StorageSubDirectoryAppContext value, settable withAppContext.SetDataor aruntimeconfig.jsonconfigProperty, so that the processes or entry points of one application can share a persistent storage directory. By default the directory name is derived from the process name andAppContext.BaseDirectory, which splits storage when components of one application differ in either, and a component that runs rarely never drains its backlog. When set, the value replaces those two inputs; the instrumentation key and user name still contribute, so different users and resources stay isolated. Behaviour is unchanged when the value is not set.(#62997)
Bugs Fixed
Azure.Monitor.OpenTelemetry.Exporter.RouteSdkStatsToDistroEndpointAppContext switch) now carry the same region-matched SDK statistics instrumentation key as the existing SDK statistics endpoint, instead of an all-zero placeholder. Only the destination differs on the distro path.(#63342)
1.10.0-beta.1
1.10.0-beta.1 (2026-09-16)
Features Added
Enable AOT compatibility validation for Azure Monitor OpenTelemetry Exporter
(#62850)
Multi-endpoint routing now maps the
microsoft.multi_endpoint_cloud_roleattribute toai.cloud.rolefor traces and logs. Missing or invalid values useunknown_service, whileai.cloud.roleInstanceremains host-derived. The attribute is read from Activity tags for traces andLogRecord.Attributesfor logs, and only affects cloud role when multi-endpoint routing is enabled.(#62909)
Added multi-endpoint routing for traces, off by default and enabled with the
Azure.Monitor.OpenTelemetry.EnableMultiEndpointRoutingAppContext switch. When enabled, an Activity carrying themicrosoft.instrumentation_keyandmicrosoft.ingestion_endpointattributes is sent to that endpoint instead of the exporter's own; Activities without both attributes are dropped. Live Metrics is disabled while the switch is on, and sampling defaults to fixed-rate rather than rate-limited because a per-process rate limit would be shared across every destination the process carries. The switch cannot be combined with Microsoft Entra ID authentication, because the credential is scoped to the exporter's own audience and would be sent to endpoints supplied by telemetry.(#62707)
Extended multi-endpoint routing to logs, off by default and enabled with the same
Azure.Monitor.OpenTelemetry.EnableMultiEndpointRoutingAppContext switch used for traces. When enabled, aLogRecordcarrying themicrosoft.instrumentation_keyandmicrosoft.ingestion_endpointattributes is sent to that endpoint instead of the exporter's own; log records without both attributes are dropped. The two routing attributes are consumed for routing and are not emitted as custom properties. Routing reads onlyLogRecord.Attributes, not logging scopes. Live Metrics disablement and the Microsoft Entra ID restriction that apply to multi-endpoint traces apply to logs as well, since both are enforced on the shared transmitter.(#62885)
Extended multi-endpoint routing to metrics, off by default and enabled with the same
Azure.Monitor.OpenTelemetry.EnableMultiEndpointRoutingAppContext switch used for traces and logs. A measurement carrying themicrosoft.instrumentation_keyandmicrosoft.ingestion_endpointdimensions is sent to that endpoint instead of the exporter's own; measurements without both are dropped. Unlike traces and logs, the routing values are supplied as dimensions at measurement time rather than stamped afterwards, because a metric's dimensions are part of its aggregation key: each destination becomes its own time series, and one instrument can feed several endpoints. Routing is applied perMetricPoint, the three routing dimensions are consumed rather than emitted as custom properties, andmicrosoft.multi_endpoint_cloud_rolesetsai.cloud.roleas it does for traces and logs. Standard metrics and performance counters are not collected while the switch is on: routed destinations are not sent standard metrics, and a process-scoped performance counter has no single owner among the destinations a routed process carries.(#62957)
A connection string is no longer required when multi-endpoint routing is enabled. Routing takes every destination from the telemetry itself, so a process that only routes has no component of its own to name, and previously had to nominate one that received nothing. Telemetry carrying valid routing attributes is still sent to the endpoint it names; telemetry without them is dropped, as it already was. SDK statistics are not collected in this configuration, because they identify a component by instrumentation key and select their region from its ingestion endpoint, neither of which exists without a connection string. Behaviour is unchanged when a connection string is configured, and unchanged when the switch is off: a missing connection string is still an error.
(#63004)
Other Changes
(#62925)
1.9.0
1.9.0 (2026-09-04)
Features Added
Add support for project id attributes propagation
(#62052)
Shutting down a provider (including
Dispose()) now writes pending telemetry to offline storage and uploads it in the background instead of blocking on ingestion. Short-lived applications such as CLI tools previously lost this telemetry, because they exit before a transmission completes; the telemetry is now durable before exit, and delivery is completed by a background drain in this or a subsequent run.ForceFlushis unchanged by default and can be opted in with theAzure.Monitor.OpenTelemetry.Exporter.PersistOnForceFlushAppContext switch, which applies to traces and logs only: a metric reader cannot distinguish a caller's flush from its periodic collection, so metricForceFlushalways transmits. The previous behavior can be restored with theAzure.Monitor.OpenTelemetry.Exporter.DisablePersistOnShutdownAppContext switch.(#61818)
How long shutdown waits for that background drain can now be set through the
Azure.Monitor.OpenTelemetry.Exporter.ShutdownDrainBudgetMillisecondsAppContext data value, using eitherAppContext.SetDataor aruntimeconfig.jsonconfigProperty.Dispose()passes a finite timeout, so by default part of that window is spent delivering telemetry and process exit tracks ingestion latency. Short-lived applications should set this to0, which makes exit cost only the file write: measured at 2.7 ms regardless of ingestion latency, against 2011 ms with a two second ingestion delay. The default is unchanged, so long-running services keep delivering their final batch within the windowDispose()allows. A single-run CI job, where no later run exists to drain storage, should not raise this value but set theAzure.Monitor.OpenTelemetry.Exporter.DisablePersistOnShutdownswitch with a boundedRetry.NetworkTimeout: raising the budget cannot guarantee delivery, becauseShutdown()waits on the drain for no time at all andDispose()is capped by the five second grace period OpenTelemetry allows it.(#62340)
Bugs Fixed
Telemetry left in offline storage by a process that exited during a transmission is no longer stranded permanently. A leased blob is renamed so that it matches neither the storage provider's blob enumeration nor its retention sweep, and the provider only reclaims those leases on a two minute maintenance timer that a short-lived process never reaches. Expired leases are now reclaimed when storage is drained.
(#61818)
Offline storage is now drained shortly after startup rather than only after the process has been running for two minutes, so telemetry persisted by a previous run is uploaded even when no single run is long-lived.
(#61818)
Telemetry is no longer dropped when the offline storage directory reaches its size cap. The oldest stored telemetry is evicted to make room.
(#61818)
Statsbeat no longer holds up process exit. It exports once more as its meter provider is disposed, which put an ingestion round trip on the exit path; that final export now runs in the background, and its network timeout is bounded at five seconds rather than the pipeline default of 100 seconds. The customer SDK stats meter provider is instead left to live for the process lifetime, so it never exports on the exit path at all; its stats are delivered by its own periodic reader.
(#62340)
Log fields are now culture-invariant. (#61996)
Added the
telemetrySuccessdimension toItem_Dropped_Countfor request and dependency telemetry.(#62081)
Other Changes
Updated OpenTelemetry dependencies to 1.18.0 and
OpenTelemetry.PersistentStorage.FileSystemto 1.1.1.(#62698)
Improved activity conversion performance by reading recognized attributes from a fixed index instead of scanning the tag list for each one. Every span shape converts faster, by about a third for spans carrying Application Insights override attributes, and each conversion rents fewer pooled buffers. Standard metrics no longer collect the tags they never read.
(#62614)
http.server_nameandserver.socket.addressare still exported as custom properties, unchanged.1.8.0
1.8.0 (2026-09-23)
Features Added
2025-08-01to2026-06-01. Tag details available at https://github.com/Azure/azure-rest-api-specs/tree/302730db231ef7b679967f94db3bb492cba291f7/specification/storage/Storage.Management.AdvancedPlatformMetricsRuleResourcefor managing advanced platform metrics rules on storage accounts.ContextCacheResourceandContextCacheContainerResourcefor managing context caches and their containers.AllowCrossTenantDelegationSasproperty on storage account create/update.IsUserBoundUserDelegationSasRequiredandRequireUserBoundUserDelegationSasActionproperties onStorageAccountSasPolicy.GuardrailIOScalarandGuardrailBandwidthScalarproperties onFileShareLimits.Bugs Fixed
StorageAccountResourceAccessRule.TenantIddeserialization to handle empty or invalid string values returned by the service (#59323).1.7.0
1.7.0 (2026-09-17)
Features Added
2026-03-01.1.6.1
1.6.1 (2026-09-29)
Bugs Fixed
1.6.0
1.6.0 (2026-09-02)
Features Added
1.5.0
1.5.0 (2026-09-10)
Features Added
Other Changes
1.5.0-beta.4
1.5.0-beta.4 (2026-09-17)
Features Added
IdentitytoConnectedRegistryDataandConnectedRegistryPatchfor user-assigned managed identity synchronization usingAuthType.ManagedIdentity.AuthTypetoConnectedRegistrySyncPropertiesandConnectedRegistrySyncUpdateProperties, supportingSyncTokenandManagedIdentity.TotalGibandAvailableGibproperties toConnectedRegistryStatusDetailfor disk space in gibibytes.ArmContainerRegistryModelFactoryparameters for mocking the new properties.Breaking Changes
ConnectedRegistrySyncProperties.TokenIdoptional and added a constructor accepting onlymessageTtl. Existing constructor calls remain compatible, but nulltokenIdvalues no longer throwArgumentNullException, and unsetTokenIdvalues are omitted from requests.ArmContainerRegistryModelFactorysignatures forConnectedRegistryData(theregistrySyncResultoverload),ConnectedRegistryPatch, andConnectedRegistrySyncUpdateProperties. Recompile callers and update method-group delegates matching the previous signatures.1.4.0
1.4.0 (2026-09-04)
Features Added
2026-07-01.Other Changes
1.4.0-beta.3
1.4.0-beta.3 (2026-09-18)
Other Changes
1.4.0-beta.2
1.4.0-beta.2 (2026-09-14)
Features Added
2025-08-01-previewto2026-06-01-preview, incorporating the2026-02-01-previewand2026-05-01-previewAPI updates.NotifyKeyspaceEventsto database create, update, and response models for configuring Redis keyspace event notifications, introduced in2026-02-01-preview.AccessStringto access policy assignments for configuring custom Redis ACL permissions, introduced in2026-05-01-preview.AccessPolicyAssignmentProvisioningErrorand theProvisioningErrorresponse property to expose access-string provisioning failure details, introduced in2026-05-01-preview.AccessPolicyNameoptional and deprecated it in favor ofAccessString, as introduced in2026-05-01-preview.Breaking Changes
IsForceMigrateproperty fromRedisEnterpriseMigrationValidationRequestContent.IsForceMigrateremains available when starting a migration.1.4.0-beta.1
1.4.0-beta.1 (2026-09-03)
Features Added
2026-05-01-preview.ScaleInModeandProxyAgentSettingstoServiceFabricManagedNodeTypeData.Breaking Changes
ServiceFabricManagedDataDiskTypevalues to match .NET naming guidelines and their wire values:PremiumV2LRStoPremiumV2Lrs,PremiumZRStoPremiumZrs, and the previousPremiumZrsvalue toStandardSsdZrs.1.3.0
1.3.0 (2026-09-04)
Features Added
Bugs Fixed
MachineLearnin*typo in registry component container and version resource and collection type names. The misspelled types remain available as hidden, obsolete compatibility shims.Other Changes
1.3.0-beta.2
1.3.0-beta.2 (2026-09-04)
Features Added
Other Changes
1.3.0-beta.1
1.3.0-beta.1 (2026-09-11)
Features Added
2026-06-02-preview.SecurityPatchauto-upgrade channel and additional trigger status details.1.3.0-alpha.20260917.2
[Missing change log entry]
1.2.0
1.2.0 (2026-09-03)
Features Added
2026-07-01.Other Changes
1.2.0-beta.3
1.2.0-beta.3 (2026-09-15)
Features Added
LocationBasedBulkCreateResource,LocationBasedBulkCreateData, andLocationBasedBulkCreateCollection, along with theGetLocationBasedBulkCreate,GetLocationBasedBulkCreates, andGetLocationBasedBulkCreateResourceaccessors.BulkCreatePropertiesandBulkCreateVmSizeProfilemodels.GetBulkCreateAsyncOperationStatusfor polling the status of a bulk create operation.Other Changes
2026-09-06-preview.1.2.0-beta.2
1.2.0-beta.2 (2026-09-09)
Other Changes
1.2.0-beta.1
1.2.0-beta.1 (2026-09-09)
Features Added
2025-11-15-preview.Other Changes
1.1.0-beta.4
1.1.0-beta.4 (2026-09-22)
Features Added
1.1.0-beta.1
1.1.0-beta.1 (2026-09-09)
Features Added
Other Changes
Azure.Coreto 1.61.0.1.0.3-beta.6920743
1.0.3-beta.6920743 (2026-10-06)
Features Added
WidgetAnalyticsClientSettingsto support creating aWidgetAnalyticsClientfromIConfiguration, including configuration-based credential resolution and dependency injection registration.1.0.3-beta.6920528
1.0.3-beta.6920528 (2026-10-06)
Features Added
WidgetAnalyticsClientSettingsto support creating aWidgetAnalyticsClientfromIConfiguration, including configuration-based credential resolution and dependency injection registration.1.0.3-beta.6840534
1.0.3-beta.6840534 (2026-09-15)
Features Added
WidgetAnalyticsClientSettingsto support creating aWidgetAnalyticsClientfromIConfiguration, including configuration-based credential resolution and dependency injection registration.1.0.0
1.0.0 (2026-09-11)
Breaking Changes
CodeTransparencyClientOptionsconstructor parameter with separate endpoint-only and endpoint-plus-options constructors.CreateEntry(WaitUntil, BinaryData, CancellationToken)overloads andCreateEntryOperation; use theCreateEntryoverloads with the optionalwaitForCommitparameter instead. Leaving it unset omits the query parameter for compatibility with older ledger deployments.RunTransparentStatementVerificationoverload; use the staticVerifyTransparentStatementmethod with verification options instead.GetOperationandGetOperationAsyncaliases for the operation-status endpoint removed from the latest SCITT draft.CreateEntryV09,GetEntryV09, andGetEntryStatementV09method families toCreateEntry,GetEntry, andGetEntryStatement, respectively.GetOperationV09andGetOperationV09Asyncare no longer public because the operation-status endpoint is deprecated; clients should pollGetEntryinstead.CodeTransparencyClientOptions.CacheTTLSecondswith theTimeSpan-valuedCacheTimeToLiveproperty and changedIdentityClientEndpointfromstringtoUri.ServiceIdentityResult.CreatedAttoCreatedOnand changed its type fromDateTimetoDateTimeOffset.CodeTransparencyVerificationOptions.AuthorizedDomainsget-only, changedCcfReceiptto a static class with get-only properties for its protocol values, and removed the unusedCodeTransparencyOperationStatusenum andCodeTransparencyClient.UnknownIssuerPrefixfield.CborUtilswire-format parsing helper; service-specific CBOR parsing is now handled internally.CodeTransparencyVerificationKeyandCodeTransparencyVerificationKeySet, which store only public asymmetric key material. The/jwks(GetPublicKeys), COSE_Key_Set (GetScittKeys), and single-key (GetScittKey) operations now exposeCancellationTokenconvenience overloads returning these normalized types, alongside the exact-wireRequestContextprotocol overloads.CcfReceiptVerifier.Verifyoverloads that accept aCodeTransparencyVerificationKey, astringkey ID plus a caller-ownedECDsa, or aCodeTransparencyVerificationKeySet.CodeTransparencyOfflineKeysandOfflineKeysBehaviorwithCodeTransparencyTrustStoreandCodeTransparencyKeyResolutionMode, using an SDK-owned, versioned, public-only serialization format.CodeTransparencyVerificationOptions.OfflineKeys/OfflineKeysBehaviorare nowTrustStore/KeyResolutionMode.Bugs Fixed
ToECDsaon .NET Framework 4.6.2.Other Changes
Azure.Security.KeyVault.Keys.Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)