Skip to content

EventGrid: Updated to use the latest version of the .NET SDK #5367

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

Merged
merged 10 commits into from
Jan 31, 2018

Conversation

kalyanaj
Copy link
Contributor

@kalyanaj kalyanaj commented Jan 25, 2018

Description

EventGrid: Updated to use the latest version of the .NET SDK and re-recorded the tests.


This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.

General Guidelines

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.
  • The pull request does not introduce breaking changes (unless a major version change occurs in the assembly and module).

Testing Guidelines

  • Pull request includes test coverage for the included changes.
  • PowerShell scripts used in tests should do any necessary setup as part of the test or suite setup, and should not use hard-coded values for locations or existing resources.

Cmdlet Signature Guidelines

  • New cmdlets that make changes or have side effects should implement ShouldProcess and have SupportShouldProcess=true specified in the cmdlet attribute. You can find more information on ShouldProcess here.
  • Cmdlet specifies OutputType attribute if any output is produced - if the cmdlet produces no output, it should implement a PassThru parameter.

Cmdlet Parameter Guidelines

  • Parameter types should not expose types from the management library - complex parameter types should be defined in the module.
  • Complex parameter types are discouraged - a parameter type should be simple types as often as possible. If complex types are used, they should be shallow and easily creatable from a constructor or another cmdlet.
  • Cmdlet parameter sets should be mutually exclusive - each parameter set must have at least one mandatory parameter not in other parameter sets.

@cormacpayne
Copy link
Member

@kalyanaj you can revert the version changes that you are making - we will update the versions for you during the release, or if you would like to release this module out-of-band, then we will use our (under construction) versioning tool to determine the proper version bump for the module.

Copy link
Member

@cormacpayne cormacpayne left a comment

Choose a reason for hiding this comment

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

@kalyanaj two comments, otherwise this LGTM


# Write-Debug "Updating eventSubscription $eventSubscriptionName to resource group $resourceGroupName"
# $newLabels = "Marketing", "Sales"
# $updateResult = Update-AzureRmEventGridSubscription -ResourceGroup $resourceGroupName -EventSubscriptionName $eventSubscriptionName -SubjectEndsWith "NewSuffix" -Label $newLabels
Copy link
Member

Choose a reason for hiding this comment

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

@kalyanaj does this mean this scenario is currently broken in the latest version of AzureRM.EventGrid, or that the new API version does not currently support this scenario?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It impacted all API versions. A service fix was deployed yesterday that resolves this issue - I have uncommented out these lines and am re-recording the tests to re-include this change.

@@ -178,7 +178,7 @@ public TopicSharedAccessKeys RegenerateTopicKey(string resourceGroupName, string
eventSubscription.Labels = new List<string>(labels);
}

return this.Client.EventSubscriptions.Create(scope, eventSubscriptionName, eventSubscription);
return this.Client.EventSubscriptions.CreateOrUpdate(scope, eventSubscriptionName, eventSubscription);
Copy link
Member

Choose a reason for hiding this comment

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

@kalyanaj does this affect when users should decide between New-AzureRmEventGridSubscription vs Update-AzureRmEventGridSubscription?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, it shouldn't. Update-AzureRmEventGridSubscription maps to a PATCH request and can be used to perform a partial update of the resource (e.g. in the case of event subscriptions, I want to update only the "filter" and not the "destination"). New-AzureRmEventGridSubscription maps to a PUT request which either creates or replaces the resource.

@kalyanaj kalyanaj assigned cormacpayne and unassigned kalyanaj Jan 30, 2018
@cormacpayne
Copy link
Member

@cormacpayne cormacpayne merged commit dfdafe8 into Azure:preview Jan 31, 2018
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.

4 participants