Skip to content

azurerm_machine_learning_compute_cluster - fix scaling settings and tags to update in-place instead of recreate#29878

Merged
sreallymatt merged 1 commit intohashicorp:mainfrom
ezhong-msft:ezhong/machine_learning_compute_cluster_scaling_inplace
Jun 27, 2025
Merged

azurerm_machine_learning_compute_cluster - fix scaling settings and tags to update in-place instead of recreate#29878
sreallymatt merged 1 commit intohashicorp:mainfrom
ezhong-msft:ezhong/machine_learning_compute_cluster_scaling_inplace

Conversation

@ezhong-msft
Copy link
Contributor

@ezhong-msft ezhong-msft commented Jun 17, 2025

Community Note

  • Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

machine_learning_compute_cluster currently recreates the resource when scaling settings and/or tags are updated. This seems to be a workaround since at the time of implementation there was a bug that prevented it from being updated in place. It seems to have since been fixed with the new sdk version so the ForceNew can be removed from these properties. See #11675

PR Checklist

  • I have followed the guidelines in our Contributing Documentation.
  • I have checked to ensure there aren't other open Pull Requests for the same update/change.
  • I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
  • I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
  • I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
    For example: “resource_name_here - description of change e.g. adding property new_property_name_here

Changes to existing Resource / Data Source

  • I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
  • I have written new tests for my resource or datasource changes & updated any relevant documentation.
  • I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.

Testing

  • My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

image

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

This is a (please select all that apply):

  • Bug Fix
  • New Feature (ie adding a service, resource, or data source)
  • Enhancement
  • Breaking Change

Related Issue(s)

Fixes #29859

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the provider.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

n/a

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

@gerrytan
Copy link
Collaborator

(Internal Microsoft review) This PR looks good to me, nice work!

Teamcity build link: https://hashicorp.teamcity.com/buildConfiguration/TF_AzureRM_AZURERM_SERVICE_PUBLIC_MACHINELEARNING/398381?buildTab=tests

@ezhong-msft ezhong-msft changed the title machine_learning_compute_cluster - fix scaling settings and tags update in-place instead of recreate machine_learning_compute_cluster - fix scaling settings and tags to update in-place instead of recreate Jun 18, 2025
@ezhong-msft ezhong-msft marked this pull request as ready for review June 18, 2025 00:36
@ezhong-msft ezhong-msft requested a review from a team as a code owner June 18, 2025 00:36
@ezhong-msft ezhong-msft force-pushed the ezhong/machine_learning_compute_cluster_scaling_inplace branch from 597dd32 to 0847870 Compare June 18, 2025 02:15
@ezhong-msft ezhong-msft force-pushed the ezhong/machine_learning_compute_cluster_scaling_inplace branch from 0847870 to 2287e52 Compare June 20, 2025 04:04
@ezhong-msft ezhong-msft changed the title machine_learning_compute_cluster - fix scaling settings and tags to update in-place instead of recreate azurerm_machine_learning_compute_cluster - fix scaling settings and tags to update in-place instead of recreate Jun 20, 2025
Copy link
Collaborator

@sreallymatt sreallymatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ezhong-msft, LGTM! ✅

@sreallymatt sreallymatt merged commit 4f5aca3 into hashicorp:main Jun 27, 2025
35 checks passed
@github-actions github-actions bot added this to the v4.35.0 milestone Jun 27, 2025
sreallymatt added a commit that referenced this pull request Jun 27, 2025
mbfrahry pushed a commit that referenced this pull request Jul 1, 2025
@github-actions
Copy link
Contributor

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Azure Machine Learning clusters are recreated instead of updating in place.

3 participants