Skip to content

Adding support for security provider integration in cortex cmdlets. #7261

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 18 commits into from
Sep 21, 2018
Merged

Adding support for security provider integration in cortex cmdlets. #7261

merged 18 commits into from
Sep 21, 2018

Conversation

nalinrajgupta
Copy link

@nalinrajgupta nalinrajgupta commented Sep 14, 2018

Description

Adding support for security provider integration in cortext.
Customer can provide SecurityProviderName and Offic365LocalBreakoutCategory when creating/updating VirtualWan object.
Customer can also provide/update EnbleInternetSecurity flag in VpnConnection and VirtualHubVnetConnection.

Checklist

@nalinrajgupta nalinrajgupta changed the title Cortex: Adding support for security provider integration. Adding support for security provider integration in cortex cmdlets. Sep 14, 2018
@nalinrajgupta
Copy link
Author

@adxsdkps
Copy link
Collaborator

Can one of the admins verify this patch?

@maddieclayton
Copy link
Contributor

@azuresdkci Add to whitelist


[Alias("VirtualHubName", "ParentVirtualHubName")]
[Parameter(
Mandatory = false,
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be mandatory

public override void Execute()
{
base.Execute();
WriteWarning("The output object type of this cmdlet will be modified in a future release.");
Copy link
Contributor

Choose a reason for hiding this comment

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

Please remove this line

@maddieclayton
Copy link
Contributor

@nalinrajgupta Please ping me when you are ready for me to take another look.

@nalinrajgupta
Copy link
Author

@maddieclayton : I've resolved all comments, can you please take a look ?

@maddieclayton
Copy link
Contributor

@nalinrajgupta One small comment, then once the test is rerecorded we can merge.

@maddieclayton
Copy link
Contributor

@nalinrajgupta Please ping me when you get this test recording in, and I'll take a final look.

@nalinrajgupta
Copy link
Author

@maddieclayton : I've resolved all comments and recorded tests also. Can you please take a look ?

Copy link
Contributor

@maddieclayton maddieclayton left a comment

Choose a reason for hiding this comment

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

Two very small comment I didn't catch next time, then this is ready to go.

@nalinrajgupta
Copy link
Author

@maddieclayton : Can you please approve the PR ? All validations has passed now.

@maddieclayton
Copy link
Contributor

@nalinrajgupta Can you regenerate the help files one more time? It looks like the Update-AzureRmVirtualHubVnetConnection parameter sets are wrong (InputObject is optional, ResourceId is optional), but it's correct in the actual cs file. That's my only remaining comment.

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