-
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
Fix missing property in existing APIs #29383
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.9) | new version | base version |
---|---|---|
policyAssignments.json | 2023-04-01(d829f0a) | 2023-04-01(main) |
policySetDefinitionVersions.json | 2023-04-01(d829f0a) | 2023-04-01(main) |
policySetDefinitions.json | 2023-04-01(d829f0a) | 2023-04-01(main) |
policyAssignments.json | 2024-04-01(d829f0a) | 2024-04-01(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
LintDiff: 0 Warnings warning [Detail]
Compared specs (v2.2.2) | new version | base version |
---|---|---|
package-2024-04 | package-2024-04(d829f0a) | package-2024-04(main) |
package-policy-2023-04 | package-policy-2023-04(d829f0a) | package-policy-2023-04(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
PathForTrackedResourceTypes |
The path must be under a subscription and resource group for tracked resource types. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L37 |
PutResponseCodes |
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L89 |
EvenSegmentedPathForPutOperation |
API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments). Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L529 |
PathForTrackedResourceTypes |
The path must be under a subscription and resource group for tracked resource types. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L529 |
PutResponseCodes |
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L573 |
AvoidAdditionalProperties |
Definitions must not have properties named additionalProperties except for user defined tags or predefined references. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L839 |
TenantLevelAPIsNotAllowed |
/providers/Microsoft.Management/managementGroups/{managementGroupId}/providers/Microsoft.Authorization/policySetDefinitions/{policySetDefinitionName} is a tenant level api. Tenant level APIs are strongly discouraged and subscription or resource group level APIs are preferred instead. If you cannot model your APIs at these levels, you will need to present your design and get an exception from PAS team. Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitions.json#L317 |
TenantLevelAPIsNotAllowed |
/providers/Microsoft.Management/managementGroups/{managementGroupName}/providers/Microsoft.Authorization/policySetDefinitions/{policySetDefinitionName}/versions/{policyDefinitionVersion} is a tenant level api. Tenant level APIs are strongly discouraged and subscription or resource group level APIs are preferred instead. If you cannot model your APIs at these levels, you will need to present your design and get an exception from PAS team. Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitionVersions.json#L414 |
OperationsAPIImplementation |
Operations API must be implemented for 'Microsoft.Authorization'. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L1 |
PathForTrackedResourceTypes |
The path must be under a subscription and resource group for tracked resource types. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L37 |
PutResponseCodes |
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L89 |
EvenSegmentedPathForPutOperation |
API path with PUT operation defined MUST have even number of segments (i.e. end in {resourceType}/{resourceName} segments). Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L529 |
PathForTrackedResourceTypes |
The path must be under a subscription and resource group for tracked resource types. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L529 |
PutResponseCodes |
Synchronous and long-running PUT operations must have responses with 200, 201 and default return codes. They also must not have other response codes. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L573 |
AvoidAdditionalProperties |
Definitions must not have properties named additionalProperties except for user defined tags or predefined references. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L853 |
Not using the common-types defined parameter 'scope'. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L52 |
|
Not using the common-types defined parameter 'scope'. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L121 |
|
Not using the common-types defined parameter 'scope'. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L190 |
|
Not using the common-types defined parameter 'scope'. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L247 |
|
Not using the common-types defined parameter 'resourceGroupName'. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L309 |
|
Not using the common-types defined parameter 'resourceGroupName'. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L366 |
|
Use the latest version v5 of types.json. Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L725 |
|
Property location must have 'x-ms-mutability':['read', 'create'] extension defined.Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L879 |
|
Property location must have 'x-ms-mutability':['read', 'create'] extension defined.Location: Microsoft.Authorization/stable/2023-04-01/policyAssignments.json#L1007 |
|
Use the latest version v5 of types.json. Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitions.json#L519 |
|
OperationId should contain the verb: 'listpolicysetdefinitionversions' in:'PolicySetDefinitionVersions_ListAllBuiltins'. Consider updating the operationId Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitionVersions.json#L42 |
|
OperationId should contain the verb: 'listpolicysetdefinitionversions' in:'PolicySetDefinitionVersions_ListAllAtManagementGroup'. Consider updating the operationId Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitionVersions.json#L76 |
|
OperationId should contain the verb: 'listpolicysetdefinitionversions' in:'PolicySetDefinitionVersions_ListAll'. Consider updating the operationId Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitionVersions.json#L113 |
|
Use the latest version v5 of types.json. Location: Microsoft.Authorization/stable/2023-04-01/policySetDefinitionVersions.json#L607 |
|
Not using the common-types defined parameter 'scope'. Location: Microsoft.Authorization/stable/2024-04-01/policyAssignments.json#L52 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌
SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
️️✔️
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
|
Generated ApiView
|
This was referenced Jun 10, 2024
Closed
Closed
Closed
Closed
Closed
[AutoPR @azure/arm-resources] Fix missing property in existing APIs
azure-sdk/azure-sdk-for-js#10170
Closed
This was referenced Jun 11, 2024
This was referenced Jun 11, 2024
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
ms-bogdan-rotaru
approved these changes
Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
ARMReview
ARMSignedOff
<valid label in PR review process>add this label when ARM approve updates after review
BreakingChange-JavaScript-Sdk
BreakingChange-JavaScript-Sdk-Approved
ReadyForApiTest
<valid label in PR review process>add this label when swagger and service APIs are ready for test
resource-manager
Versioning-Approved-BugFix
https://github.com/Azure/azure-sdk-tools/issues/6374
VersioningReviewRequired
<valid label in PR review process>add this label when versioning review is required
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
.write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext 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.