revisit rules for arm tenant resource

[jianyexi]

Since tenant resources have different linting requirements, we need to revisit the below rules to as they apply to arm resources

For all resources:

AllResourcesMustHaveDelete : should be a warning

AllResourcesMustHaveGetOperation :

AzureResourceTagsSchemaValidation: it checks if the 'tags' property is same with common types

NestedResourcesMustHaveListOperation: nested resource list by the immediate parent resource

TopLevelResourcesListByResourceGroup:

TopLevelResourcesListBySubscription:

CreateOperationAsyncResponseValidation:

PathForPutOperation: The path for 'put' operation must be under a subscription and resource group.

PutGetPatchResponseSchema: put get, patch have same response schema

PutRequestResponseScheme: put request and response schema should be the same one

RepeatedPathInfo: path info should not repeated in the resourcec model

RequiredPropertiesMissingInResourceModel: 'id','name','type' should be present in the resource model

PatchSkuProperty: sku should be present when a resource has the 'sku'

PatchIdentityProperty: identity should be present when resource has the 'identity'

PatchBodyParametersSchema: patch properties must not have properties flagged with required or default or 'x-ms-mutability:"create"'

ConsistentPatchProperties: patch properties should be present in the resource model

For tracked resource only

TrackedResourceBeyondsThirdLevel

TrackedResourcePatchOperation

TrackedResourceGetOperation

TrackedResourcesMustHavePut

XmsPageableListByRGAndSubscriptions

[rkmanda]

The 4 tracked resource related rules MUST not be applied to tenant level resources.

Comments on the rest of the rules

AllResourcesMustHaveDelete :
[RM] Should be a warning for tenant and proxy resources. Error for Tracked

AllResourcesMustHaveGetOperation :
[RM] If this is point GET, it should be warning for all types (tracked, proxy, tenant) if the resource does not have PUT. If the resource has a PUT then it should be an error for all types

AzureResourceTagsSchemaValidation: it checks if the 'tags' property is same with common types
[RM] Applies to all

NestedResourcesMustHaveListOperation: nested resource list by the immediate parent resource
[RM] Applies to all types

TopLevelResourcesListByResourceGroup:
[RM] Applies to RG scoped tracked and proxy resources. Does not apply to tenant level. Doe snot apply to subscription scoped proxy resources.

TopLevelResourcesListBySubscription:
[RM] Applies to RG scoped tracked and proxy resources, subscription scoped proxy resources. Does not apply to tenant level.

CreateOperationAsyncResponseValidation:
There are some resources that are not creatable but only updatable. For these if async is supported, only 200 is an allowed, no need for a 201. Applies to all types.

[rkmanda]

Will review the rest and post

[jianyexi]

CreateOperationAsyncResponseValidation:
There are some resources that are not creatable but only updatable. For these if async is supported, only 200 is an allowed, no need for a 201. Applies to all types.
[JY] Do you know how to find the updatable only resources ?

[jianyexi]

@rkmanda Since some rules should be warning for tenant resources or proxy resources and one linting rule can only have one severity, I am going to split these rules into two: like，ProxyAndTenantResourcesShouldHaveDelete & TrackedResourcesMustHaveDelete，any thought ?