CLOUDP-195428: merge descriptions of oneOf fields (#166)

Author: wtrocki

admin/model_cloud_provider_access_role.go

@@ -17,9 +17,9 @@ type CloudProviderAccessRole struct {
 	AtlasAssumedRoleExternalId *string `json:"atlasAssumedRoleExternalId,omitempty"`
 	// Date and time when someone authorized this role for the specified cloud service provider. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
 	AuthorizedDate *time.Time `json:"authorizedDate,omitempty"`
-	// Date and time when this Azure Service Principal was created. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
+	// Date and time when someone created this role for the specified cloud service provider. This parameter expresses its value in the ISO 8601 timestamp format in UTC.  Alternatively: Date and time when this Azure Service Principal was created. This parameter expresses its value in the ISO 8601 timestamp format in UTC.
 	CreatedDate *time.Time `json:"createdDate,omitempty"`
-	// List that contains application features associated with this Azure Service Principal.
+	// List that contains application features associated with this Amazon Web Services (AWS) Identity and Access Management (IAM) role.  Alternatively: List that contains application features associated with this Azure Service Principal.
 	FeatureUsages []CloudProviderAccessFeatureUsage `json:"featureUsages,omitempty"`
 	// Amazon Resource Name (ARN) that identifies the Amazon Web Services (AWS) Identity and Access Management (IAM) role that MongoDB Cloud assumes when it accesses resources in your AWS account.
 	IamAssumedRoleArn *string `json:"iamAssumedRoleArn,omitempty"`

admin/model_cloud_provider_container.go

@@ -14,7 +14,7 @@ type CloudProviderContainer struct {
 	ProviderName *string `json:"providerName,omitempty"`
 	// Flag that indicates whether MongoDB Cloud clusters exist in the specified network peering container.
 	Provisioned *bool `json:"provisioned,omitempty"`
-	// IP addresses expressed in Classless Inter-Domain Routing (CIDR) notation that MongoDB Cloud uses for the network peering containers in your project. MongoDB Cloud assigns all of the project's clusters deployed to this cloud provider an IP address from this range. MongoDB Cloud locks this value if an M10 or greater cluster or a network peering connection exists in this project.  These CIDR blocks must fall within the ranges reserved per RFC 1918. AWS and Azure further limit the block to between the `/24` and  `/21` ranges.  To modify the CIDR block, the target project cannot have:  - Any M10 or greater clusters - Any other VPC peering connections   You can also create a new project and create a network peering connection to set the desired MongoDB Cloud network peering container CIDR block for that project. MongoDB Cloud limits the number of MongoDB nodes per network peering connection based on the CIDR block and the region selected for the project.   **Example:** A project in an Amazon Web Services (AWS) region supporting three availability zones and an MongoDB CIDR network peering container block of limit of `/24` equals 27 three-node replica sets.
+	// IP addresses expressed in Classless Inter-Domain Routing (CIDR) notation that MongoDB Cloud uses for the network peering containers in your project. MongoDB Cloud assigns all of the project's clusters deployed to this cloud provider an IP address from this range. MongoDB Cloud locks this value if an M10 or greater cluster or a network peering connection exists in this project.  These CIDR blocks must fall within the ranges reserved per RFC 1918. AWS and Azure further limit the block to between the `/24` and  `/21` ranges.  To modify the CIDR block, the target project cannot have:  - Any M10 or greater clusters - Any other VPC peering connections   You can also create a new project and create a network peering connection to set the desired MongoDB Cloud network peering container CIDR block for that project. MongoDB Cloud limits the number of MongoDB nodes per network peering connection based on the CIDR block and the region selected for the project.   **Example:** A project in an Amazon Web Services (AWS) region supporting three availability zones and an MongoDB CIDR network peering container block of limit of `/24` equals 27 three-node replica sets.  Alternatively: IP addresses expressed in Classless Inter-Domain Routing (CIDR) notation that MongoDB Cloud uses for the network peering containers in your project. MongoDB Cloud assigns all of the project's clusters deployed to this cloud provider an IP address from this range. MongoDB Cloud locks this value if an M10 or greater cluster or a network peering connection exists in this project.  These CIDR blocks must fall within the ranges reserved per RFC 1918. GCP further limits the block to a lower bound of the `/18` range.  To modify the CIDR block, the target project cannot have:  - Any M10 or greater clusters - Any other VPC peering connections   You can also create a new project and create a network peering connection to set the desired MongoDB Cloud network peering container CIDR block for that project. MongoDB Cloud limits the number of MongoDB nodes per network peering connection based on the CIDR block and the region selected for the project.   **Example:** A project in an Google Cloud (GCP) region supporting three availability zones and an MongoDB CIDR network peering container block of limit of `/24` equals 27 three-node replica sets.  Alternatively: IP addresses expressed in Classless Inter-Domain Routing (CIDR) notation that MongoDB Cloud uses for the network peering containers in your project. MongoDB Cloud assigns all of the project's clusters deployed to this cloud provider an IP address from this range. MongoDB Cloud locks this value if an M10 or greater cluster or a network peering connection exists in this project.  These CIDR blocks must fall within the ranges reserved per RFC 1918. AWS and Azure further limit the block to between the `/24` and  `/21` ranges.  To modify the CIDR block, the target project cannot have:  - Any M10 or greater clusters - Any other VPC peering connections   You can also create a new project and create a network peering connection to set the desired MongoDB Cloud network peering container CIDR block for that project. MongoDB Cloud limits the number of MongoDB nodes per network peering connection based on the CIDR block and the region selected for the project.   **Example:** A project in an Amazon Web Services (AWS) region supporting three availability zones and an MongoDB CIDR network peering container block of limit of `/24` equals 27 three-node replica sets.
 	AtlasCidrBlock *string `json:"atlasCidrBlock,omitempty"`
 	// Unique string that identifies the Azure subscription in which the MongoDB Cloud VNet resides.
 	AzureSubscriptionId *string `json:"azureSubscriptionId,omitempty"`

admin/model_cluster_provider_settings.go

@@ -15,9 +15,9 @@ type ClusterProviderSettings struct {
 	// Flag that indicates whether the Amazon Elastic Block Store (EBS) encryption feature encrypts the host's root volume for both data at rest within the volume and for data moving between the volume and the cluster. Clusters always have this setting enabled.
 	// Deprecated
 	EncryptEBSVolume *bool `json:"encryptEBSVolume,omitempty"`
-	// Cluster tier, with a default storage and memory capacity, that applies to all the data-bearing hosts in your cluster. You must set **providerSettings.providerName** to `TENANT` and specify the cloud service provider in **providerSettings.backingProviderName**.
+	// Cluster tier, with a default storage and memory capacity, that applies to all the data-bearing hosts in your cluster.  Alternatively: Cluster tier, with a default storage and memory capacity, that applies to all the data-bearing hosts in your cluster. You must set **providerSettings.providerName** to `TENANT` and specify the cloud service provider in **providerSettings.backingProviderName**.
 	InstanceSizeName *string `json:"instanceSizeName,omitempty"`
-	// Human-readable label that identifies the geographic location of your MongoDB cluster. The region you choose can affect network latency for clients accessing your databases. For a complete list of region names, see [AWS](https://docs.atlas.mongodb.com/reference/amazon-aws/#std-label-amazon-aws), [GCP](https://docs.atlas.mongodb.com/reference/google-gcp/), and [Azure](https://docs.atlas.mongodb.com/reference/microsoft-azure/). For multi-region clusters, see **replicationSpec.{region}**.
+	// Physical location where MongoDB Cloud deploys your AWS-hosted MongoDB cluster nodes. The region you choose can affect network latency for clients accessing your databases. When MongoDB Cloud deploys a dedicated cluster, it checks if a VPC or VPC connection exists for that provider and region. If not, MongoDB Cloud creates them as part of the deployment. MongoDB Cloud assigns the VPC a CIDR block. To limit a new VPC peering connection to one CIDR block and region, create the connection first. Deploy the cluster after the connection starts.  Alternatively: Microsoft Azure Regions.  Alternatively: Google Compute Regions.  Alternatively: Human-readable label that identifies the geographic location of your MongoDB cluster. The region you choose can affect network latency for clients accessing your databases. For a complete list of region names, see [AWS](https://docs.atlas.mongodb.com/reference/amazon-aws/#std-label-amazon-aws), [GCP](https://docs.atlas.mongodb.com/reference/google-gcp/), and [Azure](https://docs.atlas.mongodb.com/reference/microsoft-azure/). For multi-region clusters, see **replicationSpec.{region}**.
 	RegionName *string `json:"regionName,omitempty"`
 	// Disk Input/Output Operations per Second (IOPS) setting for Amazon Web Services (AWS) storage that you configure only for abbr title=\"Amazon Web Services\">AWS</abbr>. Specify whether Disk Input/Output Operations per Second (IOPS) must not exceed the default Input/Output Operations per Second (IOPS) rate for the selected volume size (`STANDARD`), or must fall within the allowable Input/Output Operations per Second (IOPS) range for the selected volume size (`PROVISIONED`).
 	VolumeType *string `json:"volumeType,omitempty"`

admin/model_data_lake_store_settings.go

@@ -27,9 +27,9 @@ type DataLakeStoreSettings struct {
 	Region *string `json:"region,omitempty"`
 	// ID of the Cluster the Online Archive belongs to.
 	ClusterId *string `json:"clusterId,omitempty"`
-	// Human-readable label of the MongoDB Cloud cluster on which the store is based.
+	// Name of the Cluster the Online Archive belongs to.  Alternatively: Human-readable label of the MongoDB Cloud cluster on which the store is based.
 	ClusterName *string `json:"clusterName,omitempty"`
-	// Unique 24-hexadecimal digit string that identifies the project.
+	// ID of the Project the Online Archive belongs to.  Alternatively: Unique 24-hexadecimal digit string that identifies the project.
 	ProjectId      *string                           `json:"projectId,omitempty"`
 	ReadPreference *DataLakeAtlasStoreReadPreference `json:"readPreference,omitempty"`
 	// Flag that validates the scheme in the specified URLs. If `true`, allows insecure `HTTP` scheme, doesn't verify the server's certificate chain and hostname, and accepts any certificate with any hostname presented by the server. If `false`, allows secure `HTTPS` scheme only.

admin/model_group_alerts_config.go

@@ -21,7 +21,7 @@ type GroupAlertsConfig struct {
 	Id *string `json:"id,omitempty"`
 	// List of one or more Uniform Resource Locators (URLs) that point to API sub-resources, related API resources, or both. RFC 5988 outlines these relationships.
 	Links []Link `json:"links,omitempty"`
-	// No matchers are available for these alert types. The list is always empty.
+	// No matchers are available for these alert types. The list is always empty.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: No matchers are available for these alert types. The list is always empty.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: No matchers are available for these alert types. The list is always empty.  Alternatively: No matchers are available for these alert types. The list is always empty.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: No matchers are available for these alert types. The list is always empty.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: List of rules that determine whether MongoDB Cloud checks an object for the alert configuration. You can filter using the matchers array if the **eventTypeName** specifies an event for a host, replica set, or sharded cluster.  Alternatively: No matchers are available for these alert types. The list is always empty.
 	Matchers []map[string]interface{} `json:"matchers,omitempty"`
 	// List that contains the targets that MongoDB Cloud sends notifications.
 	Notifications []AlertsNotificationRootForGroup `json:"notifications,omitempty"`

admin/model_private_link_endpoint.go

@@ -22,7 +22,7 @@ type PrivateLinkEndpoint struct {
 	EndpointGroupName *string `json:"endpointGroupName,omitempty"`
 	// List of individual private endpoints that comprise this endpoint group.
 	Endpoints []GCPConsumerForwardingRule `json:"endpoints,omitempty"`
-	// State of the Azure Private Link Service connection when MongoDB Cloud received this request.
+	// State of the Google Cloud network endpoint group when MongoDB Cloud received this request.  Alternatively: State of the Azure Private Link Service connection when MongoDB Cloud received this request.
 	Status *string `json:"status,omitempty"`
 	// Human-readable label that MongoDB Cloud generates that identifies the private endpoint connection.
 	PrivateEndpointConnectionName *string `json:"privateEndpointConnectionName,omitempty"`

admin/model_serverless_tenant_endpoint.go

@@ -10,11 +10,11 @@ import (
 type ServerlessTenantEndpoint struct {
 	// Unique 24-hexadecimal digit string that identifies the private endpoint.
 	Id *string `json:"_id,omitempty"`
-	// Unique string that identifies the Azure private endpoint's network interface that someone added to this private endpoint service.
+	// Unique string that identifies the private endpoint's network interface.  Alternatively: Unique string that identifies the Azure private endpoint's network interface that someone added to this private endpoint service.
 	CloudProviderEndpointId *string `json:"cloudProviderEndpointId,omitempty"`
 	// Human-readable comment associated with the private endpoint.
 	Comment *string `json:"comment,omitempty"`
-	// Unique string that identifies the Azure private endpoint service. MongoDB Cloud returns null while it creates the endpoint service.
+	// Unique string that identifies the PrivateLink endpoint service. MongoDB Cloud returns null while it creates the endpoint service.  Alternatively: Unique string that identifies the Amazon Web Services (AWS) PrivateLink endpoint service. MongoDB Cloud returns null while it creates the endpoint service.  Alternatively: Unique string that identifies the Azure private endpoint service. MongoDB Cloud returns null while it creates the endpoint service.
 	EndpointServiceName *string `json:"endpointServiceName,omitempty"`
 	// Human-readable error message that indicates error condition associated with establishing the private endpoint connection.
 	ErrorMessage *string `json:"errorMessage,omitempty"`

admin/model_serverless_tenant_endpoint_update.go

@@ -11,7 +11,7 @@ type ServerlessTenantEndpointUpdate struct {
 	// Human-readable comment associated with the private endpoint.
 	Comment      *string `json:"comment,omitempty"`
 	ProviderName string  `json:"providerName"`
-	// Unique string that identifies the Azure private endpoint's network interface for this private endpoint service.
+	// Unique string that identifies the private endpoint's network interface.  Alternatively: Unique string that identifies the Azure private endpoint's network interface for this private endpoint service.
 	CloudProviderEndpointId *string `json:"cloudProviderEndpointId,omitempty"`
 	// IPv4 address of the private endpoint in your Azure VNet that someone added to this private endpoint service.
 	PrivateEndpointIpAddress *string `json:"privateEndpointIpAddress,omitempty"`