feat: Azure monitor autoscale name consistency

[hemalshah-gradientedge]

No description provided.

[Copilot]

Pull request overview

This PR aims to make Azure Monitor autoscale setting naming consistent by explicitly setting the Azure Native autoscaleSettingName input (in addition to the existing name) so the resource’s ARM path/name stays aligned, and updating tests/changeset accordingly.

Changes:

• Set a computed autoscaleSettingName when creating azure-native:monitor:AutoscaleSetting.
• Update Pulumi mocks/tests to read the autoscale name from args.inputs.autoscaleSettingName.
• Add a patch changeset for the Azure package.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
packages/azure/test/services/monitor-manager.test.ts	Updates Pulumi mocks to use autoscaleSettingName for autoscale resources.
packages/azure/src/services/monitor/main.ts	Computes and passes autoscaleSettingName (and aligns it with name) when creating autoscale settings.
.changeset/bumpy-coins-fetch.md	Adds a patch changeset documenting the autoscale naming fix.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

Suppressed comments (1)

packages/azure/test/services/monitor-manager.test.ts:105

• The mock now derives the AutoscaleSetting output name from autoscaleSettingName, but it no longer verifies that the request payload name is kept in sync. Since the production code explicitly sets both to avoid Azure validation failures, the test should fail if they ever diverge (or if name is accidentally removed).

    if (args.type === 'azure-native:monitor:AutoscaleSetting') {
      name = args.inputs.autoscaleSettingName

      return {