-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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 optional traffic analytics config fields to network watcher config object for enhancing the Network Watcher cmdlets #3023
Adding optional traffic analytics config fields to network watcher config object for enhancing the Network Watcher cmdlets #3023
Conversation
…tched flowlog configuration
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/network/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/network/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/network/resource-manager/readme.md
|
Code | Id | Source | Message |
---|---|---|---|
ListInOperationName | R1003 | Link | Since operation 'ApplicationGateways_BackendHealth' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: '{devicepath}' in:'ExpressRouteCircuits_ListArpTable'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: '{devicepath}' in:'ExpressRouteCircuits_ListRoutesTable'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: '{devicepath}' in:'ExpressRouteCircuits_ListRoutesTableSummary'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: '{devicepath}' in:'ExpressRouteCrossConnections_ListArpTable'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: '{devicepath}' in:'ExpressRouteCrossConnections_ListRoutesTableSummary'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: '{devicepath}' in:'ExpressRouteCrossConnections_ListRoutesTable'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'ipflowverify' in:'NetworkWatchers_VerifyIPFlow'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'securitygroupview' in:'NetworkWatchers_GetVMSecurityRules'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'querystatus' in:'PacketCaptures_GetStatus'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'querytroubleshootresult' in:'NetworkWatchers_GetTroubleshootingResult'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'configureflowlog' in:'NetworkWatchers_SetFlowLogConfiguration'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'queryflowlogstatus' in:'NetworkWatchers_GetFlowLogStatus'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'connectivitycheck' in:'NetworkWatchers_CheckConnectivity'. Consider updating the operationId |
PostOperationIdContainsUrlVerb | R2066 | Link | OperationId should contain the verb: 'availableproviderslist' in:'NetworkWatchers_ListAvailableProviders'. Consider updating the operationId |
DescriptionAndTitleMissing | R4000 | Link | 'RedirectTypeEnum' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'AuthorizationPropertiesFormat' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'ExpressRouteCircuitPeeringPropertiesFormat' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'ExpressRouteCircuitConnectionPropertiesFormat' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'ExpressRouteCircuitReference' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'ExpressRouteCrossConnectionPeeringProperties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'ErrorDetails' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'Error' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'backendAddressPools' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'protocol' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'protocol' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'protocol' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'code' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'target' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'message' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'code' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'message' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'target' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'details' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'innerError' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'error' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'value' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'resources' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'securityRuleAssociations' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'networkInterfaceAssociation' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'subnetAssociation' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'storageLocation' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'filters' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'etag' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'retentionPolicy' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'flowAnalyticsConfiguration' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'networkWatcherFlowAnalyticsConfiguration' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'source' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'destination' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'protocolConfiguration' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'HTTPConfiguration' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'providerLocation' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'providerLocation' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'source' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'destination' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'etag' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
DescriptionAndTitleMissing | R4000 | Link | 'properties' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. |
GetInOperationName | R1005 | Link | 'GET' operation 'CheckDnsNameAvailability' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ListInOperationName | R1003 | Link | Since operation 'NetworkInterfaces_GetEffectiveRouteTable' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ListInOperationName | R1003 | Link | Since operation 'NetworkWatchers_GetVMSecurityRules' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ListInOperationName | R1003 | Link | Since operation 'ConnectionMonitors_Query' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
PutRequestResponseScheme | R2017 | Link | A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'ConnectionMonitors_CreateOrUpdate' Request Model: 'ConnectionMonitor' Response Model: 'ConnectionMonitorResult' |
ListInOperationName | R1003 | Link | Since operation 'VirtualNetworks_CheckIPAddressAvailability' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
GetInOperationName | R1005 | Link | 'GET' operation 'VirtualNetworks_CheckIPAddressAvailability' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ListInOperationName | R1003 | Link | Since operation 'VirtualNetworkGateways_GetBgpPeerStatus' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ListInOperationName | R1003 | Link | Since operation 'VirtualNetworkGateways_GetLearnedRoutes' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ListInOperationName | R1003 | Link | Since operation 'VirtualNetworkGateways_GetAdvertisedRoutes' response has model definition 'array', it should be of the form "_list". Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
PutInOperationName | R1006 | Link | 'PUT' operation 'VirtualNetworkGatewayConnections_SetSharedKey' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
OperationIdNounVerb | R1001 | Link | Per the Noun_Verb convention for Operation Ids, the noun 'NetworkInterfaces' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
OperationIdNounVerb | R1001 | Link | Per the Noun_Verb convention for Operation Ids, the noun 'NetworkInterfaces' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
OperationIdNounVerb | R1001 | Link | Per the Noun_Verb convention for Operation Ids, the noun 'NetworkInterfaces' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ParameterNotDefinedInGlobalParameters | R2015 | Link | Parameter "api-version" is referenced but not defined in the global parameters section of Service Definition |
OperationIdNounVerb | R1001 | Link | Per the Noun_Verb convention for Operation Ids, the noun 'PublicIPAddresses' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
OperationIdNounVerb | R1001 | Link | Per the Noun_Verb convention for Operation Ids, the noun 'PublicIPAddresses' should not appear after the underscore. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. |
ParameterNotDefinedInGlobalParameters | R2015 | Link | Parameter "api-version" is referenced but not defined in the global parameters section of Service Definition |
❌0 new Errors.(0 total)
AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback
Thanks for your co-operation.
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/network/resource-manager/readme.md
|
Code | Id | Source | Message |
---|---|---|---|
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pickHostNameFromBackendAddress |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: probeEnabled |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requireServerNameIndication |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: pickHostNameFromBackendHttpSettings |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: includePath |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: includeQueryString |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableHttp2 |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: requestBodyCheck |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disableBgpRoutePropagation |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: primary |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableAcceleratedNetworking |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableIPForwarding |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableFloatingIP |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: primary |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: available |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: allowClassicOperations |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableFloatingIP |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: disableOutboundSnat |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableFloatingIP |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enabled |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: autoStart |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableRegionalMdmAccount |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: fillGapWithZero |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isInternal |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAuthorizedToUse |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: allowVirtualNetworkAccess |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: allowForwardedTraffic |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: allowGatewayTransit |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: useRemoteGateways |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableDdosProtection |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableVmProtection |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: available |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableBgp |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: activeActive |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableBgp |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: usePolicyBasedTrafficSelectors |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: enableBgp |
EnumInsteadOfBoolean | R3018 | Link | Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: usePolicyBasedTrafficSelectors |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
NonApplicationJsonType | R2004 | Link | Only 'application/json' content-type is supported by ARM. |
❌0 new Errors.(81 total)
AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback
Thanks for your co-operation.
@ravbhatnagar changes in a stable API. |
@sayghosh - Do these changes exist on the service side in this api-version already and are only getting added to swagger now? If yes, @sergey-shandar - feel free to merge. |
@ravbhatnagar Yes, the changes exist on service side. |
@ravbhatnagar @sergey-shandar Are there any more comments which need to be addressed? |
AutoRest linter results for ARM Related Validation Errors/WarningsThese errors are reported by the ARM team's validation tools, reachout to ARM RP API Review directly for any questions or concerns. File: specification/network/resource-manager/readme.md
|
AutoRest linter results for SDK Related Validation Errors/WarningsThese errors are reported by the SDK team's validation tools, reachout to ADX Swagger Reviewers directly for any questions or concerns. File: specification/network/resource-manager/readme.md
|
* Added 2018-05-01 version. Common fixes (#3025) * Created May folder. Updated version for exampls, commands * Updated package to May version * Returned NW examples * Fixed API version; Fixed NetworkWatcher examples * Fixed VPN Gateway/Connection examples * Add changes from PR#2975 https://github.com/Azure/azure-rest-api-specs/pull/2975/files * Adding optional traffic analytics config fields to network watcher config object for enhancing the Network Watcher cmdlets (#3023) * Adding optional traffic analytics parameters with existing network watched flowlog configuration * Updating the version * Updating latest versoin in readme.md * #AppGw Fundamentals Clean Up (#3046) * Network 2018 05 01 (#3068) * Adding optional traffic analytics parameters with existing network watched flowlog configuration * Updating the version * Updating latest versoin in readme.md * Adding optional traffic analytics parameters with flowlog parameters * Reverting old chnages * Expose new SKUs for VMSS VPN and ER gateways (#3069) Expose new SKUs for VMSS VPN and ER gateways * Initial network error fixes and suppressions (#3051) * Initial network error fixes and suppressions * reworked exception to specified code blocks only * Added express route fixes
…dk-assistant Testing with spec change
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger