Location Class
A region in which the Azure Cosmos DB database account is deployed.
Variables are only populated by the server, and will be ignored when sending a request.
- Inheritance
-
azure.mgmt.cosmosdb._serialization.ModelLocation
Constructor
Location(*, location_name: str | None = None, failover_priority: int | None = None, is_zone_redundant: bool | None = None, **kwargs: Any)
Keyword-Only Parameters
Name | Description |
---|---|
location_name
|
The name of the region. |
failover_priority
|
The failover priority of the region. A failover priority of 0 indicates a write region. The maximum value for a failover priority = (total number of regions
|
is_zone_redundant
|
Flag to indicate whether or not this region is an AvailabilityZone region. |
Variables
Name | Description |
---|---|
id
|
The unique identifier of the region within the database account. Example: <accountName>-<locationName>. |
location_name
|
The name of the region. |
document_endpoint
|
The connection endpoint for the specific region. Example: https://<accountName>-<locationName>.documents.azure.com:443/. |
provisioning_state
|
The status of the Cosmos DB account at the time the operation was called. The status can be one of following. 'Creating' – the Cosmos DB account is being created. When an account is in Creating state, only properties that are specified as input for the Create Cosmos DB account operation are returned. 'Succeeded' – the Cosmos DB account is active for use. 'Updating' – the Cosmos DB account is being updated. 'Deleting' – the Cosmos DB account is being deleted. 'Failed' – the Cosmos DB account failed creation. 'DeletionFailed' – the Cosmos DB account deletion failed. |
failover_priority
|
The failover priority of the region. A failover priority of 0 indicates a write region. The maximum value for a failover priority = (total number of regions
|
is_zone_redundant
|
Flag to indicate whether or not this region is an AvailabilityZone region. |
Azure SDK for Python
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for