Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,6 @@
"ApplicationDefinitionKind": "ServiceFabricApplicationDescription"
}
},
"204": {
"headers": {},
"body": ""
}
"204": {}
}
}
Original file line number Diff line number Diff line change
Expand Up @@ -21,9 +21,6 @@
"HealthState": "Ok"
}
},
"204": {
"headers": {},
"body": ""
}
"204": {}
}
}
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,6 @@
"IsServiceGroup": false
}
},
"204": {
"headers": {},
"body": ""
}
"204": {}
}
}
Original file line number Diff line number Diff line change
Expand Up @@ -12989,7 +12989,7 @@
},
"ServicePlacementPreferPrimaryDomainPolicyDescription": {
"x-ms-discriminator-value": "PreferredPrimaryDomain",
"description": "Describes the policy to be used for placement of a Service Fabric service where the service's Primary replicas should optimally be placed in a particular domain.\n\nThis placement policy is usually used with fault domains in scenarios where the Service Fabric cluster is geographically distributed in order to indicate that a services primary replica should be located in a particular fault domain, which in geo-distributed scenarios usually aligns with regional or datacenter boundaries. Note that since this is an optimization it is possible that the Primary replica may not end up located in this domain due to failures, capacity limits, or other constraints.",
"description": "Describes the policy to be used for placement of a Service Fabric service where the service's Primary replicas should optimally be placed in a particular domain.\n\nThis placement policy is usually used with fault domains in scenarios where the Service Fabric cluster is geographically distributed in order to indicate that a service's primary replica should be located in a particular fault domain, which in geo-distributed scenarios usually aligns with regional or datacenter boundaries. Note that since this is an optimization it is possible that the Primary replica may not end up located in this domain due to failures, capacity limits, or other constraints.",
"allOf": [
{
"$ref": "#/definitions/ServicePlacementPolicyDescription"
Expand Down