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_new_relic_monitor - Support identity #26115

Merged
merged 2 commits into from
May 29, 2024

Conversation

ms-zhenhua
Copy link
Contributor

@ms-zhenhua ms-zhenhua commented May 28, 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 "+1" or "me too" comments, they generate extra noise for PR followers and do not help prioritize for review

Description

Support identity for azurerm_new_relic_monitor to enable metrics flow like data dog

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.

  • azurerm_new_relic_monitor - Support identity

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 May 28, 2024 07:45
Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

Thanks @ms-zhenhua. It looks like there are some fundamental issues with the identity property for this resource that should be raised with the Service Team, could you please open a swagger issue regarding the comments I left in-line and then link those in the code?

@@ -520,3 +532,34 @@ func flattenUserInfoModel(input *monitors.UserInfo) []UserInfoModel {

return append(outputList, output)
}

// Currently the API only supports `SystemAssigned` type.
Copy link
Member

Choose a reason for hiding this comment

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

If the Swagger spec specifies that System and User assigned should be supported but the API in reality only supported SystemAssigned then we should raise an issue on the Rest API specs repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

created a issue to track this problem: Azure/azure-rest-api-specs#29256

Comment on lines +272 to +274
if identityValue.Type != identity.TypeNone {
properties.Identity = identityValue
}
Copy link
Member

Choose a reason for hiding this comment

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

This isn't how the Type field in Identity is usually handled which would imply a bug, this should also be raised as an issue on the Rest API specs repo.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

created a issue to track this problem: Azure/azure-rest-api-specs#29257

Copy link
Contributor

Choose a reason for hiding this comment

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

In the future: can we also update the API Definition to expose the Identity field correctly too? We've spent a considerable amount of time standardising the behaviours (and methods) for the Identity types, so we should lean on them where possible - as such I've opened hashicorp/pandora#4171 which'll allow this.

@ms-zhenhua
Copy link
Contributor Author

Hi @stephybun, thank you for your review. I have created the issues and added them to the comments. Please take another review.

Copy link
Member

@stephybun stephybun left a comment

Choose a reason for hiding this comment

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

Thanks @ms-zhenhua LGTM 👍

@stephybun stephybun merged commit 8eb8df5 into hashicorp:main May 29, 2024
35 checks passed
@github-actions github-actions bot added this to the v3.106.0 milestone May 29, 2024
stephybun added a commit that referenced this pull request May 29, 2024
Copy link

github-actions bot commented Jul 1, 2024

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 1, 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.

3 participants