Skip to content

policy_definition_resource: Force recreation when policy definition parameter names change#31986

Open
jiaweitao001 wants to merge 2 commits intohashicorp:mainfrom
jiaweitao001:issue-31965
Open

policy_definition_resource: Force recreation when policy definition parameter names change#31986
jiaweitao001 wants to merge 2 commits intohashicorp:mainfrom
jiaweitao001:issue-31965

Conversation

@jiaweitao001
Copy link
Collaborator

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

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: TestAccAzureRMPolicyDefinition_requiresImport (155.91s)
--- PASS: TestAccAzureRMPolicyDefinition_metadata (170.05s)
--- PASS: TestAccAzureRMPolicyDefinition_computedMetadata (170.50s)
--- PASS: TestAccAzureRMPolicyDefinition_basic (181.00s)
--- PASS: TestAccAzureRMPolicyDefinition_basicWithDetail (188.89s)
--- PASS: TestAccAzureRMPolicyDefinition_renameParameter (300.44s)
--- PASS: TestAccAzureRMPolicyDefinition_removeParameter (418.16s)
--- PASS: TestAccAzureRMPolicyDefinition_modeUpdate (433.70s)
PASS

Change Log

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

  • azurerm_resource - support for the thing1 property [GH-00000]

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

AI Assistance Disclosure

  • AI Assisted - This contribution was made by, or with the assistance of, AI/LLMs

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.

Note

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

jiaweitao001 and others added 2 commits March 18, 2026 10:07
…r names change

The CustomizeDiff logic previously only handled parameter count decreases,
but did not detect parameter renames (where count stays the same but names
change). Azure API does not allow parameter name changes during update.

This change iterates through old parameter names and forces recreation if
any are missing from the new parameters, handling both removal and rename.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The parameter names can not be changed (on rename)

2 participants