Skip to content

azurerm_shared_image_version - Adapt upcoming breaking changes for Azure Compute Gallery Image Version - #28954

Merged
catriona-m merged 5 commits into
hashicorp:mainfrom
ms-zhenhua:shared-image-version-breaking-change-860
May 8, 2025
Merged

catriona-m merged 5 commits into
hashicorp:mainfrom
ms-zhenhua:shared-image-version-breaking-change-860

Conversation

@ms-zhenhua

@ms-zhenhua ms-zhenhua commented Mar 5, 2025 •

Copy link
Copy Markdown
Contributor

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

According to the latest MS-DOC and the notice from Azure below, properties.storageProfile.source.Id should be replaced with properties.storageProfile.source.virtualMachineId for VM while properties.storageProfile.[osDiskImage/dataDiskImages].source.Id should be replaced with properties.storageProfile.osDiskImage.source.storageAccountId for blob.

Note: Though it is a breaking change for Azure, the change of the provider is not a breaking change as the provider uses a different schema design which does not expose the API interface.

image

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.
  • (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

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)

--- PASS: TestAccSharedImageVersion_storageAccountTypeLrs (1268.22s)
--- PASS: TestAccSharedImageVersion_replicationMode (843.30s)
--- PASS: TestAccSharedImageVersion_specializedImageVersionByVM (1085.37s)
--- PASS: TestAccSharedImageVersion_replicatedRegionDeletion (1317.87s)
--- PASS: TestAccSharedImageVersion_blobURI (1372.55s)
--- PASS: TestAccSharedImageVersion_storageAccountTypeZrs (1379.28s)
--- PASS: TestAccSharedImageVersion_specializedImageVersionBySnapshot (1516.18s)
--- PASS: TestAccSharedImageVersion_basic (1750.99s)
--- PASS: TestAccSharedImageVersion_requiresImport (1726.90s)
--- PASS: TestAccSharedImageVersion_endOfLifeDate (1757.32s)
--- PASS: TestAccSharedImageVersion_diskEncryptionSetID (1481.81s)

Change Log

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

  • azurerm_shared_image_version - Adapt upcoming breaking changes for Azure Compute Gallery Image Version

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 #0000

Note

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

@ms-zhenhua
ms-zhenhua marked this pull request as ready for review March 5, 2025 08:43
@ms-zhenhua
ms-zhenhua requested a review from a team as a code owner March 5, 2025 08:43
@rcskosir rcskosir linked an issue Apr 24, 2025 that may be closed by this pull request
1 task done
@catriona-m catriona-m self-assigned this May 7, 2025

@catriona-m catriona-m left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks @ms-zhenhua LGTM!

@catriona-m
catriona-m merged commit c3ab110 into hashicorp:main May 8, 2025
@github-actions github-actions Bot added this to the v4.28.0 milestone May 8, 2025
catriona-m added a commit that referenced this pull request May 8, 2025
jackofallops added a commit that referenced this pull request May 9, 2025
* changelog for 4.28 release

* Update CHANGELOG.md #29410

* Update CHANGELOG.md #29397

* Update CHANGELOG.md #27454

* Update CHANGELOG.md #28919

* Update CHANGELOG.md #29443

* Update CHANGELOG.md #29443

* Update CHANGELOG.md #29456

* Update CHANGELOG.md for #29424

* Update CHANGELOG.md for #29150

* Update CHANGELOG.md #29435

* Update CHANGELOG.md #29431

* Update CHANGELOG.md #29396

* Update CHANGELOG.md #29197

* Update CHANGELOG.md for #28705

* Update CHANGELOG.md #28954

* Update CHANGELOG.md for #29363

* prep for release

---------

Co-authored-by: catriona-m <86247157+catriona-m@users.noreply.github.com>
Co-authored-by: Wodans Son <20408400+WodansSon@users.noreply.github.com>
Co-authored-by: sreallymatt <106555974+sreallymatt@users.noreply.github.com>
Co-authored-by: Matthew Frahry <mbfrahry@gmail.com>
Co-authored-by: jackofallops <ste@hashicorp.com>
@github-actions

github-actions Bot commented Jun 8, 2025

Copy link
Copy Markdown
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 Jun 8, 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.

azurerm_shared_image_version should use storageAccountId before breaking change

2 participants