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

EventHub: 2018-preview - added new API for NetworkRuleSet #4748

Merged
merged 6 commits into from
Dec 14, 2018

Conversation

v-Ajnava
Copy link
Member

@v-Ajnava v-Ajnava commented Dec 4, 2018

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@openapi-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2153

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#3729

@AutorestCI
Copy link

AutorestCI commented Dec 4, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@praries880 praries880 added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Dec 5, 2018
"$ref": "#/parameters/ResourceGroupNameParameter"
},
{
"$ref": "#/parameters/NamespaceNameParamet
Copy link
Contributor

Choose a reason for hiding this comment

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

For hygiene, resource type name should be lowerCamelCase

Copy link
Member Author

Choose a reason for hiding this comment

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

resolved

"$ref": "#/parameters/ResourceGroupNameParameter"
},
{
"$ref": "#/parameters/NamespaceNameParamet
Copy link
Contributor

Choose a reason for hiding this comment

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

Same comment on lowerCamelCasing for hygien

Copy link
Member Author

Choose a reason for hiding this comment

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

resolved

"$ref": "#/parameters/ResourceGroupNameParameter"
},
{
"$ref": "#/parameters/NamespaceNameParamet
Copy link
Contributor

Choose a reason for hiding this comment

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

The resource type name should be plural: networkRulesets. I'm not sure what the distinction is between virtualNetworkRules and networkRulsets, but could an improved resource type name help make that distinction?

Copy link
Member Author

Choose a reason for hiding this comment

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

as this is the preview version, we will be will be deprecated virtualNetworkRules API and will be going ahead with only networkruleset API.
for plural: networkRulesets, Correct me if I am wrong. each namespace will be having only one networkRuleset which will consist of ipRule list and virtualNetworkRule list.
so should we make plural: networkRulesets or singular : networkRuleset ?

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah, today we do pluralize the resourceType names even though for that type there may be just a single instance possible.

Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

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

Please see comment about pluralization of resource type name

@KrisBash KrisBash added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label Dec 6, 2018
@v-Ajnava
Copy link
Member Author

v-Ajnava commented Dec 7, 2018

@KrisBash can you please see the comment for pluralization. changing the definition name of NetworkRuleset to loweCamelCase will change class name to lowerCamelCase which Autorest generates.

Copy link
Contributor

@nschonni nschonni left a comment

Choose a reason for hiding this comment

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

minor typos

}
},
"200": {
"description": "Namespace successfuly created.",
Copy link
Contributor

Choose a reason for hiding this comment

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

successfuly -> successfully

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed

}
},
"200": {
"description": "Namespace successfuly updated.",
Copy link
Contributor

Choose a reason for hiding this comment

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

successfuly -> successfully

"$ref": "#/parameters/resourceGroupNameParameter"
},
{
"$ref": "#/parameters/namespaceNameParamet
Copy link
Contributor

Choose a reason for hiding this comment

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

vaule -> value

"$ref": "#/parameters/resourceGroupNameParameter"
},
{
"$ref": "#/parameters/namespaceNameParamet
Copy link
Contributor

Choose a reason for hiding this comment

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

NameSpaceVirtualNetworkRuleSetget -> NameSpaceVirtualNetworkRuleSetGet
Or change it to a sentence

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed, changed the example filenames from NameSpaceVirtualNetworkRuleSetget to NameSpaceNetworkRuleSetGet

@ravbhatnagar
Copy link
Contributor

@v-Ajnava - You have updated the model names to be plural, which was not needed. The resource type name in the URL of the API needs to be pluralized.

@v-Ajnava
Copy link
Member Author

@ravbhatnagar updated resource type name in url with plural and lowerCamelCase and reverted plural model names

@ravbhatnagar
Copy link
Contributor

cool, signing off from ARM side.

@ravbhatnagar ravbhatnagar added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Dec 12, 2018
@ravbhatnagar ravbhatnagar removed ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Dec 12, 2018
@praries880
Copy link

@KrisBash You need to approve the changes here. I can not merge the changes in without your approval.

Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

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

Thanks for the changes

@praries880 praries880 merged commit 7ec8852 into Azure:master Dec 14, 2018
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
* added new NetworkRule APIs

* updated lowerCamelCase for Parameters

* pluralize NetworkRuleSets

* fixed lint errors

* fixed typo and updated examples files names for NetworkRuleSets

* updated resource type name in url with plural and lowerCamelCase
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
)

* Swagger for HybridAKS provisioned clusters (#4697)

Added swagger for HybridAKS provisioned clusters

* Swagger fix validation errors and added examples (#4744)

* added examples and fixed some validation errors

* fixed more validation errors and warnings

* Added x-ms-secret flag for passwords

* fixing liniting issues in swagger (#4748)

* Fixes for prettier, spell checks and go-sdk generation (#4767)

* Fixes for prettier, spell checks and go-sdk generation

* changed default network plugin to calico

* formatting fix

* added enums, defaults and moved nodepool config to a common definition

* changed go-sdk to track2

* Added cluster prefix to name and location
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants