Gen2EnvironmentCreateOrUpdateParameters Class
Parameters supplied to the Create or Update Environment operation for a Gen2 environment.
All required parameters must be populated in order to send to Azure.
- Inheritance
-
azure.mgmt.timeseriesinsights.models._models_py3.EnvironmentCreateOrUpdateParametersGen2EnvironmentCreateOrUpdateParameters
Constructor
Gen2EnvironmentCreateOrUpdateParameters(*, location: str, sku: Sku, time_series_id_properties: List[TimeSeriesIdProperty], storage_configuration: Gen2StorageConfigurationInput, tags: Dict[str, str] | None = None, warm_store_configuration: WarmStoreConfigurationProperties | None = None, **kwargs)
Parameters
Name | Description |
---|---|
location
Required
|
Required. The location of the resource. |
tags
Required
|
A set of tags. Key-value pairs of additional properties for the resource. |
kind
Required
|
Required. The kind of the environment.Constant filled by server. Possible values include: "Gen1", "Gen2". |
sku
Required
|
Required. The sku determines the type of environment, either Gen1 (S1 or S2) or Gen2 (L1). For Gen1 environments the sku determines the capacity of the environment, the ingress rate, and the billing rate. |
time_series_id_properties
Required
|
Required. The list of event properties which will be used to define the environment's time series id. |
storage_configuration
Required
|
Required. The storage configuration provides the connection details that allows the Time Series Insights service to connect to the customer storage account that is used to store the environment's data. |
warm_store_configuration
Required
|
The warm store configuration provides the details to create a warm store cache that will retain a copy of the environment's data available for faster query. |
Keyword-Only Parameters
Name | Description |
---|---|
location
Required
|
|
sku
Required
|
|
time_series_id_properties
Required
|
|
storage_configuration
Required
|
|
tags
Required
|
|
warm_store_configuration
Required
|
|
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