-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Adding Network security perimeter common types [v5] #28958
Conversation
…oked pretty clean.
…e/type/id from that). I've left 'location' property on it for now but I'm not sure if it should actually be there. Get rid of x-ms-client-flatten. Remove parameters that wouldn't be needed for implementing NSP.
…-manager/Microsoft.BotService/preview/2023-09-15-preview /networksecurityperimeter.json
Next Steps to Merge✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge. |
Swagger Validation Report
|
Compared specs (v0.10.8) | new version | base version |
---|---|---|
networksecurityperimeter.json | 0000-00-00(cda181f) | 0000-00-00(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
LintDiff succeeded [Detail] [Expand]
Validation passes for LintDiff.
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
SwaggerAPIView: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
Failed to generate swagger APIView. The readme file format is invalid and the tag is not defined. Use the provided readme template for guidance readme template. For more details, please check the detail log. |
"How to fix":"Check the readme file and make sure the readme file format is valid and the tag is defined. Use the provided readme template" |
️️✔️
TypeSpecAPIView succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️
Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran the Spectral linter on this file and it flagged some structural an Azure style issues.
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
…-level Definition so it can more easily be reused.
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
specification/common-types/resource-management/v5/networksecurityperimeter.json
Outdated
Show resolved
Hide resolved
/azp run |
Azure Pipelines successfully started running 5 pipeline(s). |
Adding network security perimeter type definitions to common-types.
"$ref": "#/definitions/ResourceAssociation" | ||
}, | ||
"profile": { | ||
"$ref": "#/definitions/NetworkSecurityProfile" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's better to use "NetworkSecurityPerimeterProfile" or "PerimeterProfile", "Profile" or "NspProfile". We never use NetworkSecurityProfile and don't recommend to use it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Profile" would be best recommended to make it consistent with other keys like "ResourceAssociation", "AccessRule"
specification/common-types/resource-management/v5/networksecurityperimeter.json
Show resolved
Hide resolved
Adding network security perimeter type definitions to common-types.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PR
andDue diligence checklist
.Next Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.