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
Copy file name to clipboardExpand all lines: docs/rules.md
+6
Original file line number
Diff line number
Diff line change
@@ -1220,6 +1220,12 @@ Validates that system data is not defined in the properties bag, but rather as a
1220
1220
1221
1221
Please refer to [system-data-in-properties-bag.md](./system-data-in-properties-bag.md) for details.
1222
1222
1223
+
### TagsAreNotAllowedForProxyResources
1224
+
1225
+
`tags` should not be specified in the properties bag for proxy resources. Consider using a Tracked resource instead.
1226
+
1227
+
Please refer to [tags-are-not-allowed-for-proxy-resources.md](./tags-are-not-allowed-for-proxy-resources.md) for details.
1228
+
1223
1229
### TenantLevelAPIsNotAllowed
1224
1230
1225
1231
Tenant level APIs are strongly discouraged and subscription or resource group level APIs are preferred instead. The reason for this guidance is that tenant level APIs have a really broad scope and blast radius. We permit APIs to be at this broad scope under rare conditions. Some ARM feature sets also do not cover tenant level APIs such as the use of AFEC. Additionally, if you intend to bypass the standard RBAC constructs and make the APIs unauthorized, you will need an approval from the PAS team before the open API spec can be merged.
constERROR_MESSAGE$1="A patch request body must only contain properties present in the corresponding put request body, and must contain at least one of the properties.";
2084
+
constERROR_MESSAGE$2="A patch request body must only contain properties present in the corresponding put request body, and must contain at least one of the properties.";
0 commit comments