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

new resource azurerm_newrelic_monitored_subscription #27891

Closed
wants to merge 19 commits into from

Conversation

teowa
Copy link
Contributor

@teowa teowa commented Nov 5, 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

swagger: https://github.com/Azure/azure-rest-api-specs/blob/a0b2a34b9ff6d324c31e031d6e373fc3ceb38c81/specification/newrelic/resource-manager/NewRelic.Observability/stable/2024-01-01/NewRelic.json#L1372

azure doc: https://learn.microsoft.com/en-us/azure/partner-solutions/new-relic/new-relic-how-to-manage#monitor-multiple-subscriptions

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)

Change Log

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

  • new resource azurerm_newrelic_monitored_subscription

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.

@teowa
Copy link
Contributor Author

teowa commented Nov 18, 2024

image

Copy link
Contributor

@ms-zhenhua ms-zhenhua left a comment

Choose a reason for hiding this comment

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

Hi @teowa ,

Thanks for this PR - I've taken a look through and left some comments inline. If we can fix those up, this should be good to go 👍

@@ -24,6 +26,13 @@ func NewClient(o *common.ClientOptions) (*Client, error) {

o.Configure(monitorsClient.Client, o.Authorizers.ResourceManager)

monitoredSubscriptionsClient, err := monitoredsubscriptions.NewMonitoredSubscriptionsClientWithBaseURI(o.Environment.ResourceManager)
if err != nil {
return nil, fmt.Errorf("building Monitors client: %+v", err)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
return nil, fmt.Errorf("building Monitors client: %+v", err)
return nil, fmt.Errorf("building Monitored Subscriptions client: %+v", err)

return fmt.Errorf("decoding: %+v", err)
}

client := metadata.Client.NewRelic.MonitoredSubscriptionsClient
Copy link
Contributor

Choose a reason for hiding this comment

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

please put client := ... at the beginning of the method


existing := resp.Model
if existing == nil {
return fmt.Errorf("retrieving %s: model was nil", *id)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
return fmt.Errorf("retrieving %s: model was nil", *id)
return fmt.Errorf("retrieving %s: `model` was nil", *id)

}

if existing.Properties == nil {
return fmt.Errorf("retrieving %s: property was nil", *id)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
return fmt.Errorf("retrieving %s: property was nil", *id)
return fmt.Errorf("retrieving %s: `properties` was nil", *id)

if err := client.CreateOrUpdateThenPoll(ctx, monitorId, *existing); err != nil {
return fmt.Errorf("updating %s: %+v", *id, err)
}

Copy link
Contributor

Choose a reason for hiding this comment

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

update does not need resourceMonitoredSubscriptionsWaitForAvailable ?


monitorId := monitoredsubscriptions.NewMonitorID(id.SubscriptionId, id.ResourceGroup, id.MonitorName)

if _, err = client.Delete(ctx, monitorId); err != nil {
Copy link
Contributor

Choose a reason for hiding this comment

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

why delete the parent resource ?

}

// The resource cannot be deleted if the parent NewRelic Monitor exists, the DELETE only clears the monitoredSubscriptionList, so here we add a custom poller
pollerType := &monitoredSubscriptionDeletedPoller{
Copy link
Contributor

Choose a reason for hiding this comment

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

why not use the same style as the create to define a method which may be named as resourceMonitoredSubscriptionsWaitForDeleted

Comment on lines 260 to 264
if input == nil {
return make([]NewRelicMonitoredSubscription, 0)
}

results := make([]NewRelicMonitoredSubscription, 0)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
if input == nil {
return make([]NewRelicMonitoredSubscription, 0)
}
results := make([]NewRelicMonitoredSubscription, 0)
results := make([]NewRelicMonitoredSubscription, 0)
if input == nil {
return results
}

resp.Model.Properties == nil ||
resp.Model.Properties.MonitoredSubscriptionList == nil ||
len(*resp.Model.Properties.MonitoredSubscriptionList) == 0 {
return metadata.MarkAsGone(id)
Copy link
Contributor

Choose a reason for hiding this comment

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

since "monitored_subscription" is defined as optional, it is possible len(*resp.Model.Properties.MonitoredSubscriptionList) == 0 ?

resource "azurerm_new_relic_monitored_subscription" "test" {
monitor_id = azurerm_new_relic_monitor.test.id

monitored_subscription {
Copy link
Contributor

Choose a reason for hiding this comment

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

if monitored_subscription is optional, if should not exist in basic

@teowa
Copy link
Contributor Author

teowa commented Nov 28, 2024

Hi @ms-zhenhua , thanks for reviewing this! However, this resource name can only be default and thus should be inline, following the guidelines. I have submitted #28134 to supersede this. The recommended changes have been incorporated into the new PR.

@teowa teowa closed this Nov 28, 2024
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.

3 participants