You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the following error is given out -
"WARNING: TrackedResourceValidation - Tracked Resource failing validation is: Application. Validation Failed: 2.
Tracked Resource must have:
1. A Get Operation
2. A ListByResourceGroup operation with x-ms-pageable extension and
3. A ListBySubscriptionId operation with x-ms-pageable extension.
4. Type, Location, Tags should not be used in the properties."
IMO, there are already rules for each individual items listed above. So the violation message should be given separately for each of the above.
The text was updated successfully, but these errors were encountered:
Let's remove #1, because we already have rule M3027, rest need to be split in separate rules #2 and #3, should be applied to models only from responses. #4 should be applied to all tracked resources, not just the ones in responses, the rule should just be applied in the first/top level of "properties".
For the list case, we should be looking to see if the model definition is being used by another model which builds the list, and that list "model" is returned by any operations, example having "Model1" and Model1_ListResult", so "Model1_ListResult" is the model returned by the list operation, which lists all "Model1" objects.
Currently the following error is given out -
"WARNING: TrackedResourceValidation - Tracked Resource failing validation is: Application. Validation Failed: 2.
Tracked Resource must have:
1. A Get Operation
2. A ListByResourceGroup operation with x-ms-pageable extension and
3. A ListBySubscriptionId operation with x-ms-pageable extension.
4. Type, Location, Tags should not be used in the properties."
IMO, there are already rules for each individual items listed above. So the violation message should be given separately for each of the above.
The text was updated successfully, but these errors were encountered: