Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

azurerm_role_management_policy - fix a crash #27731

Merged
merged 3 commits into from
Oct 29, 2024

Conversation

ziyeqf
Copy link
Contributor

@ziyeqf ziyeqf commented Oct 23, 2024

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

Since the go-azure-sdk was updated on v4.6.0, which will unmarshal the policy into specific type instead of RawRoleManagementPolicyRuleImpl the provider crashed..

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 relevent 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)
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 #27710

Note

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

@magodo
Copy link
Collaborator

magodo commented Oct 23, 2024

LGTM 👍

@ziyeqf ziyeqf marked this pull request as ready for review October 23, 2024 09:25
@ziyeqf ziyeqf requested review from katbyte and a team as code owners October 23, 2024 09:25
@rcskosir rcskosir added the bug label Oct 24, 2024
@WodansSon
Copy link
Collaborator

image

@WodansSon WodansSon merged commit ab25d65 into hashicorp:main Oct 29, 2024
29 checks passed
@github-actions github-actions bot added this to the v4.8.0 milestone Oct 29, 2024
WodansSon added a commit that referenced this pull request Oct 29, 2024
@ziyeqf ziyeqf deleted the role_management_policy_crash branch October 30, 2024 00:58
Copy link

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 Nov 29, 2024
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.

4 participants