Docs 菜单

API 变更日志

(2.0~cb78d7fa646)

2025 年 3 月 12 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 'results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types] ' 响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
  • 已将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 中添加了新的 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID'枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'OUTSIDE_STREAM_PROCESSOR_METRIC_THRESHOLD'枚举值
  • 已将新的“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto] Scaling Audit Types/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types]/' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
  • 已将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 中添加了新的 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID'枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'OUTSIDE_STREAM_PROCESSOR_METRIC_THRESHOLD'枚举值
  • 已将新的“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto] Scaling Audit Types/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 将新的枚举值“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 将新的枚举值“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE”、“PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 '/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types]/'属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #2: Cluster Alerts]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 '/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: NDS Auto Scaling Audit Types]/'属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
已交
  • 将“#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName”响应属性
  • 将新的“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值添加到“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/”响应属性
  • 已将新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值添加到 'results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #12: NDS Auto Scaling Audit Types] ' 响应属性
GET /api/atlas/v2/groups/{groupId}/clusters
已交
  • 添加了可选属性 'results/items/advancedConfiguration、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled、results/items/replicationSpecs /items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items /regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema # 3： GCP区域复制规范]/autoScaling/compute/predictiveEnabled' 到响应
POST /api/atlas/v2/groups/{groupId}/clusters
已交
  • 添加了可选属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs /items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/predictiveEnabled、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/predictiveEnabled' 到响应SE
  • 添加了新的可选请求属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items /regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute /predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/predictiveEnabled'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
已交
  • 在响应中添加了可选属性“advancedConfiguration, autoScaling/compute/predictiveEnabled”
  • 添加了新的可选请求属性“advancedConfiguration, autoScaling/compute/predictiveEnabled”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 添加了可选属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs /items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/predictiveEnabled、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/predictiveEnabled' 到响应SE
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 添加了可选属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled，replicationSpecs/items/regionConfigs /items/oneOf[subschema #2： Azure区域复制规范]/autoScaling/compute/predictiveEnabled、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/predictiveEnabled' 到响应SE
  • 添加了新的可选请求属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items /regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute /predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/predictiveEnabled'
GET / API/ Atlas/v2/groups/{groupId}/clusters/{clusterName}/autoScalingConfiguration
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 更新当不存在节点时API的返回，端点返回带有空JSON ({}) 的 200，而不是 400。
GET /api/atlas/v2/groups/{groupId}/events
已交
  • 将“#/components/schemas/ChartsAudit”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“results/items/oneOf[subschema #9: Cluster Events]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_IS_VALID、ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在“results/items/oneOf[subschema #16: NDS Auto Scaling Audits]/eventTypeName”响应属性中添加了新的“PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
已交
  • 将“#/components/schemas/ChartsAudit”添加到响应的响应正文“oneOf”列表中
  • 将新的“CLUSTER_AGENT_IN_CRASH_LOOP”枚举值添加到“/oneOf[subschema #9: Cluster Events]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/”响应属性中添加了新的“ENCRYPTION_AT_REST_CONFIG_IS_VALID”、“ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID”枚举值
  • 在 '/oneOf[subschema #16: NDS Auto Scaling Audits]/eventTypeName' 响应属性中添加了新的 'PREDICTIVE_COMPUTE_AUTO_SCALE_INITIATED_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE、PREDICTIVE_COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE'枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
已交
  • 添加了新的可选请求属性 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsAutoScaling/compute/predictiveEnabled, replicationSpecs/items /regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/autoScaling/compute/predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsAutoScaling/compute /predictiveEnabled, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/autoScaling/compute/predictiveEnabled'
GET /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“S3”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“results/items/dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“results/items/dataProcessRegion/ 地区/”响应属性中
  • 在响应中添加了可选属性'results/items/connections/items/ Amazon Web Services/testBucket'
POST /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“S3”鉴别器映射键添加到“connections/items/”请求属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/StreamsS3Connection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 将新的“OHIO_USA”枚举值添加到请求属性“dataProcessRegion/ 地区/”
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
  • 添加了新的可选请求属性“connections/items/ Amazon Web Services/testBucket”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到“地区”请求属性“oneOf”列表
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 将新的“OHIO_USA”枚举值添加到请求属性“地区/”
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 将“S3”鉴别器映射键添加到“results/items/”响应属性
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“results/items/ Amazon Web Services/testBucket”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 为请求鉴别器添加了“S3”映射键
  • 将“#/components/schemas/StreamsS3Connection”添加到请求正文“oneOf”列表
  • 将“S3”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/ Amazon Web Services/testBucket”
  • 添加了新的可选请求属性'/ Amazon Web Services/testBucket'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 将“S3”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/ Amazon Web Services/testBucket”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 为请求鉴别器添加了“S3”映射键
  • 将“#/components/schemas/StreamsS3Connection”添加到请求正文“oneOf”列表
  • 将“S3”映射键添加到响应状态“200”的响应鉴别器
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/ Amazon Web Services/testBucket”
  • 添加了新的可选请求属性'/ Amazon Web Services/testBucket'
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
已交
  • 将“S3”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/ApiStreamsGCPRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将“#/components/schemas/StreamsS3Connection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 将新的“OHIO_USA”枚举值添加到“dataProcessRegion/ 地区/”响应属性中
  • 在响应中添加了可选属性“connections/items/ Amazon Web Services/testBucket”
GET /api/atlas/v2/orgs/{orgId}/events
已交
  • 将新的“GROUP_MOVED_FROM_ORG”枚举值添加到“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
已交
  • 将新的“GROUP_MOVED_FROM_ORG”枚举值添加到“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
已交
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S40_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_STORAGE_NVME' 枚举 values to the 'results/items/lineItems/items/sku' response属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
已交
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S40_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_STORAGE_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_STORAGE_NVME' 枚举 values to the 'lineItems/items/sku' response 属性

2025 年 2 月 25 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf [subschema #3: GCP Regions]/' 响应属性
  • 将新的“AFRICA_SOUTH_1”、“NORTH_AMERICA_SOUTH_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/regionName/oneOf[subschema” #3: GCP Regions]/' 响应属性
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在“results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范”中]/regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 571在'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema1 #: Amazon Web Services Regions ]/' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/ oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/”响应中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值属性
  • 11在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf[subschema3 #: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/” '
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/regionName”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 在“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/regionName”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
  • 在请求属性“providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/regionName”中添加了新的“AFRICA_SOUTH_1”、“NORTH_AMERICA_SOUTH_1”枚举值
  • 在请求属性“providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/regionName”中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/ oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/”响应中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/regionName/oneOf[subschema #3: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值: GCP Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/regionName/ oneOf[subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional ReplicationSpecifications]/regionName/oneOf[ subschema #1: Amazon Web Services Regions]/' 响应属性
  • 在“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/”响应中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值属性
  • 11在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf[subschema3 #: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/” '
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在“results/items/oneOf[subschema #2: GCP]/regions/items/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 在“results/items/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在 '/oneOf[subschema #2: GCP]/regions/items/' 响应属性中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性
  • 在请求属性'/oneOf[subschema #2: GCP ]/regions/items/' 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“/oneOf[subschema #3: Amazon Web Services]/regionName”
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 在“results/items/oneOf[subschema #2: GCP]/regions/items/”响应属性中添加了新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值
  • 在“results/items/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[subschema #2: GCP]/regions/items/' 响应属性中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[subschema #2: GCP]/regions/items/' 响应属性中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #3: Amazon Web Services]/regionName”响应属性
  • 在请求属性'/oneOf[subschema #2: GCP ]/regions/items/' 中添加了新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“/oneOf[subschema #3: Amazon Web Services]/regionName”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“awsKms/ 地区”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“awsKms/ 地区”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“awsKms/ 地区”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema # 2： Amazon Web Services Regions]/' 响应属性
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“results/items/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 响应属性
  • 在“results/items/regionName/oneOf[subschema #2: Amazon Web Services Regions]/”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #2” : Amazon Web Services Regions]/' 响应属性
  • 将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 响应属性
  • 在“regionName/oneOf[subschema #2: Amazon Web Services Regions]/”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性'/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性'/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema # 2： Amazon Web Services地区]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“regionName/oneOf[subschema #2: Amazon Web Services Regions]/”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName/oneOf[subschema #2” : Amazon Web Services Regions]/' 响应属性
  • 将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 响应属性
  • 在“regionName/oneOf[subschema #2: Amazon Web Services Regions]/”响应属性中添加了新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 11在请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/regionName/oneOf[subschema3 #: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的 'AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1'枚举值添加到请求属性'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/oneOf[subschema #3: GCP地区]/'
  • 已将新的“AFRICA_SOUTH_1、NORTH_AMERICA_SOUTH_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/”
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/” regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/regionName/” oneOf[subschema #1: Amazon Web Services Regions]/'
  • 已将新的“AP_SOUTHEAST_5、AP_SOUTHEAST_7、MX_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services Regions]/” '

2025 年 2 月 20 日发布

PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roleMappings/items/roleAssignments/items/ 角色”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roleAssignments/items/ 角色”
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roleAssignments/items/ 角色”
POST /api/atlas/v2/groups/{groupId}/access
已交
  • 端点已弃用
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“results/items/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 中添加了新的 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY'枚举值
  • 在请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #3: 群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #11: 枚举 Set Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #:12 枚举 Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema :3 Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3：群组通知]/roles/items/'
  • 已将新的 'GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER'枚举值添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #6: Cps 备份枚举值警报配置]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles /items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #7: 组织通知]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 在请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 中添加了新的 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY'枚举值
  • 在请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #3: 群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #11: 枚举 Set Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #:12 枚举 Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema :3 Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3：群组通知]/roles/items/'
  • 已将新的 'GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_READ_ONLY、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER'枚举值添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #6: Cps 备份枚举值警报配置]/ 通知/items/oneOf[subschema #3 : Group notification]/roles/items/'
  • 在请求属性'/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group通知]/roles/items/'
  • 在请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3:群组通知]/roles/items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles /items/'
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #7: 组织通知]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/roles/items/”
  • 在请求属性“/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/' 中添加了新的 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
已交
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
已交
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
已交
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 将新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值添加到“results/items/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName”响应属性
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND”枚举值
POST /api/atlas/v2/groups/{groupId}/apiKeys
已交
  • 在请求属性“roles/items/”中添加了新的“GROUP_DATABASE_ACCESS_ADMIN, ORG_BILLING_READ_ONLY”枚举值
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
已交
  • 已将新的“GROUP_BACKUP_MANAGER”、“GROUP_DATABASE_ACCESS_ADMIN”、“GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
已交
  • 将新的 'GROUP_DATABASE_ACCESS_ADMIN'枚举值添加到请求属性'/items/roles/items/'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
已交
  • 请求可选属性“isCustomShardKeyHashed”变为非只写属性
  • 请求可选属性“isShardKeyUnique”变为非只写属性
  • 请求可选属性“numInitialChunks”变为非只写属性
  • 请求可选属性“presplitHashedZones”变为非只写属性
  • 请求所需属性“customShardKey”变为非只读属性
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
已交
  • 在响应中添加了可选属性“results/items/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName”
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
已交
  • 在响应中添加了可选属性“/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
已交
  • 在响应中添加了可选属性“/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName”
GET /api/atlas/v2/groups/{groupId}/events
已交
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #34: Version Audit Types]/”响应属性中添加了新的“ACME_PROVIDER_FIXED、ACME_PROVIDER_UNFIXED”枚举值
  • 在“results/items/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_AGENT_API_KEY_ROTATED、MONGOT_LOGS_DOWNLOADED”枚举值
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT”枚举值
  • 在“results/items/oneOf[subschema #25: Stream Processor Events]/eventTypeName”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
已交
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #34: Version Audit Types]/”响应属性中添加了新的“ACME_PROVIDER_FIXED、ACME_PROVIDER_UNFIXED”枚举值
  • 在“/oneOf[subschema #15: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_AGENT_API_KEY_ROTATED、MONGOT_LOGS_DOWNLOADED”枚举值
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types]/”响应属性中添加了新的“CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/”响应属性中添加了新的“STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT”枚举值
  • 在 '/oneOf[subschema #25: Stream Processor Events]/eventTypeName' 响应属性中添加了新的 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND、STREAM_PROCESSOR_KAFKA_LAG_CURRENT'枚举值
PATCH /api/atlas/v2/groups/{groupId}/invites
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/invites
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
已交
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
已交
  • 已将新的“GROUP_DATABASE_ACCESS_ADMIN”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
已交
  • 已将新的“GROUP_DATABASE_ACCESS_ADMIN”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
已交
  • 将新的 'GROUP_DATABASE_ACCESS_ADMIN'枚举值添加到请求属性'/items/roles/items/'
GET /api/atlas/v2/groups/{groupId}/settings
已交
  • 在响应中添加了可选属性“isDataExplorerGenAIFeaturesEnabled、isDataExplorerGenAISampleDocumentPassingEnabled”
PATCH /api/atlas/v2/groups/{groupId}/settings
已交
  • 在响应中添加了可选属性“isDataExplorerGenAIFeaturesEnabled、isDataExplorerGenAISampleDocumentPassingEnabled”
  • 添加了新的可选请求属性“isDataExplorerGenAIFeaturesEnabled、isDataExplorerGenAISampleDocumentPassingEnabled”
GET /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“AWSLambda”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 将新的“AWSLambda”枚举值添加到“results/items/connections/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/streams
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”请求属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
  • 已将新的“AWSLambda”枚举值添加到请求属性“connections/items/type”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
已交
  • 在响应中添加了可选属性“results/items/interfaceEndpointName”
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
已交
  • 在响应中添加了可选属性“interfaceEndpointName”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
已交
  • 在响应中添加了可选属性“interfaceEndpointName”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 将“AWSLambda”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“results/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 将“AWSLambda”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到请求正文“oneOf”列表
  • 已将“AWSLambda”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“AWSLambda”枚举值
  • 已将新的“AWSLambda”枚举值添加到请求属性“/type”
  • 已将新的“AWSLambda”枚举值添加到请求属性“type”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 已将“AWSLambda”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“AWSLambda”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 将“AWSLambda”映射键添加到请求鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到请求正文“oneOf”列表
  • 已将“AWSLambda”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“AWSLambda”枚举值
  • 已将新的“AWSLambda”枚举值添加到请求属性“/type”
  • 已将新的“AWSLambda”枚举值添加到请求属性“type”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
已交
  • 将“AWSLambda”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsAWSLambdaConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“AWSLambda”枚举值添加到“connections/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/teams
已交
  • Added the new 'GROUP_BACKUP_MANAGER, GROUP_CLUSTER_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_ONLY, GROUP_DATA_ACCESS_READ_WRITE, GROUP_OBSERVABILITY_VIEWER, GROUP_OWNER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 枚举 values to the 请求 属性 '/items/roleNames'
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
已交
  • Added the new 'GROUP_BACKUP_MANAGER, GROUP_CLUSTER_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_ONLY, GROUP_DATA_ACCESS_READ_WRITE, GROUP_OBSERVABILITY_VIEWER, GROUP_OWNER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 枚举 values to the 请求 属性 'roleNames'
GET /api/atlas/v2/groups/{groupId}/users
已交
  • 针对状态“200”，“results/items/roles/items/”响应的属性类型/格式从“对象'/'' 更改为 'string'/''
  • 添加了API标签“MongoDB Cloud Users”
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
  • 添加了新的可选“查询”请求参数“用户名”
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • Added the new 'GROUP_BACKUP_MANAGER, GROUP_CLUSTER_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_DATA_ACCESS_ADMIN, GROUP_DATA_ACCESS_READ_ONLY, GROUP_DATA_ACCESS_READ_WRITE, GROUP_OBSERVABILITY_VIEWER, GROUP_OWNER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 枚举 values to the 'results/items/roles/items/' response 属性
  • 在响应中添加了必需的属性“results/items/orgMembershipStatus”
  • 从响应中删除了必需属性“results/items/country、results/items/emailAddress、results/items/firstName、results/items/lastName、results/items/mobileNumber、results/items/password”
  • 删除了可选属性 'results/items/createdAt、results/items/lastAuth、results/items/links、results/items/roles/items/groupId、results/items/roles/items/orgId、results/items/roles/items /roleName, results/items/teamIds' 来自响应
  • 响应属性 'results/items/ ID, results/items/roles' 变为必填项
POST /api/atlas/v2/groups/{groupId}/users
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
已交
  • 添加了API标签“MongoDB Cloud Users”
GET /api/atlas/v2/groups/{groupId}/users/{userId}
已交
  • 已添加端点
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
已交
  • 端点已弃用
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“groupRoles/items/”
POST /api/atlas/v2/groups/{groupId}/users/{userId}:addRole
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/users/{userId}:removeRole
已交
  • 已添加端点
POST /api/atlas/v2/orgs
已交
  • 将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“apiKey/roles/items/”
POST /api/atlas/v2/orgs/{orgId}/apiKeys
已交
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
已交
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/invites
已交
  • 端点已弃用
PATCH /api/atlas/v2/orgs/{orgId}/invites
已交
  • 端点已弃用
  • 在请求属性“groupRoleAssignments/items/roles/items/”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/orgs/{orgId}/invites
已交
  • 端点已弃用
  • 在请求属性“groupRoleAssignments/items/roles/items/”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
已交
  • 端点已弃用
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
已交
  • 端点已弃用
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
已交
  • 端点已弃用
  • 在请求属性“groupRoleAssignments/items/roles/items/”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、GROUP_SEARCH_INDEX_EDITOR、GROUP_STREAM_PROCESSING_OWNER”枚举值
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
已交
  • 针对状态“200”，“results/items/roles”响应的属性类型/格式从“大量”/“更改为”对象“/”
  • 添加了API标签“MongoDB Cloud Users”
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
  • 添加了新的可选“查询”请求参数“用户名”
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 在响应中添加了必需的属性“results/items/orgMembershipStatus”
  • 从响应中删除了必需属性“results/items/country、results/items/emailAddress、results/items/firstName、results/items/lastName、results/items/mobileNumber、results/items/password”
  • 在响应中添加了可选属性“results/items/roles/groupRoleAssignments, results/items/roles/orgRoles”
  • 从响应中删除了可选属性“results/items/createdAt, results/items/lastAuth, results/items/links”
  • 响应属性 'results/items/ ID, results/items/roles' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
已交
  • 端点已弃用
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
已交
  • 端点已弃用
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:addUser
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}:removeUser
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/users
已交
  • 针对状态“200”，“results/items/roles”响应的属性类型/格式从“大量”/“更改为”对象“/”
  • 添加了API标签“MongoDB Cloud Users”
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
  • 添加了新的可选“查询”请求参数“用户名”
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 在响应中添加了必需的属性“results/items/orgMembershipStatus”
  • 从响应中删除了必需属性“results/items/country、results/items/emailAddress、results/items/firstName、results/items/lastName、results/items/mobileNumber、results/items/password”
  • 在响应中添加了可选属性“results/items/roles/groupRoleAssignments, results/items/roles/orgRoles”
  • 从响应中删除了可选属性“results/items/createdAt, results/items/lastAuth, results/items/links”
  • 响应属性 'results/items/ ID, results/items/roles' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/users
已交
  • 已添加端点
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
已交
  • 添加了API标签“MongoDB Cloud Users”
GET /api/atlas/v2/orgs/{orgId}/users/{userId}
已交
  • 已添加端点
PATCH /api/atlas/v2/orgs/{orgId}/users/{userId}
已交
  • 已添加端点
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
已交
  • 端点已弃用
  • 已将新的“ORG_BILLING_READ_ONLY”枚举值添加到请求属性“orgRoles/items/”
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:addRole
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/users/{userId}:removeRole
已交
  • 已添加端点
POST /api/atlas/v2/users
已交
  • 端点已弃用
  • 在请求属性“roles/items/roleName”中添加了新的“GROUP_BACKUP_MANAGER、GROUP_DATABASE_ACCESS_ADMIN、GROUP_OBSERVABILITY_VIEWER、ORG_BILLING_READ_ONLY”枚举值
GET /api/atlas/v2/users/byName/{userName}
已交
  • 端点已弃用
GET /api/atlas/v2/users/{userId}
已交
  • 端点已弃用

2025 年 2 月 18 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/dropIndexSuggestions
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/schemaAdvice
已交
  • 已添加端点

2025 年 2 月 06 日发布

GET /api/atlas/v2/clusters
Updated
  • “results/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
  • “results/items/orgId”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • “results/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “dataAccessIdentityProviderIds/items/”请求属性的 minLength 从“24”减少到“0”
  • “identityProviderId”请求属性的 minLength 从“20”减少到“0”
  • “orgId”请求属性的 minLength 从“24”减少到“0”
  • “roleMappings/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “roleMappings/items/roleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “roleMappings/items/roleAssignments/items/orgId”请求属性的 minLength 从“24”减少到“0”
  • “userConflicts/items/federationSettingsId”请求属性的 minLength 从“24”减少到“0”
  • “userConflicts/items/userId”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“dataAccessIdentityProviderIds/items/”中删除了模式“^([af0-9]{24})$”
  • “dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “roleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “roleAssignments/items/orgId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“ID”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“ID”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“ID”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “roleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “roleAssignments/items/orgId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • “results/items/associatedOrgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
  • “results/items/oneOf[subschema #1: SAML]/关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式'^([af0-9]{24}) $' 已删除
  • “results/items/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24}” )$' 已删除
  • “results/items/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24}” )$' 已删除
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • '/oneOf[subschema #2: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • “关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: SAML]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$' 为已删除
  • '/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • '/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • “关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: SAML]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$' 为已删除
  • '/oneOf[subschema #2: OIDC WORKFORCE]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • '/oneOf[subschema #3: OIDC WORKLOAD]/关联Orgs/items/dataAccessIdentityProviderIds/items/' 响应的属性模式'^([af0-9]{24})$'已删除
  • “关联Orgs/items/dataAccessIdentityProviderIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 对于“path”请求参数“federationSettingsId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“identityProviderId”，minLength 从“20”减少到“0”
POST /api/atlas/v2/groups
Updated
  • 对于“查询”请求参数“projectOwnerId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “orgId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/items/groupId”请求属性的 minLength 已从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}/status
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24 ' 改为 '0'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #11: Replica Set Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #12: 副本集阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #13: Serverless Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #14: Flex Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #14: Flex Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #15: Stream Processor Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Any other Alert Configurations]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “/oneOf[subschema #1: Any other Alert Configurations]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: App Services Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #2: App Services Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #3: App Services Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #4: Billing Threshold Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #5: Cluster Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24' 减少到 '0'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #7: Encryption Key Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #8: Host Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #8: Host Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #9: Host Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • 已将新的“HOST_EXPOSED、HOST_SECURITY_CHECKUP_NOT_MET、HOST_SSL_CERTIFICATE_STALE、HOST_VERSION_BEHIND、VERSION_BEHIND”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
  • 在请求属性“/oneOf[subschema #12：副本集阈值警报配置]/eventTypeName”中添加了新的“TOO_FEW_HEALTHY_MEMBERS、TOO_MANY_UNHEALTHY_MEMBERS”枚举值
DELETE /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24 ' 改为 '0'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #11: Replica Set Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #12: 副本集阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #13: Serverless Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #14: Flex Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #14: Flex Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #14: Flex Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #15: Stream Processor Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #15: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Any other Alert Configurations]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “/oneOf[subschema #1: Any other Alert Configurations]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: App Services Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #2: App Services Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #3: App Services Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #4: Billing Threshold Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #5: Cluster Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 已从 '24' 减少到 '0'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #7: Encryption Key Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #8: Host Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #8: Host Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0 '
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/groupId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #9: Host Metric Alert Configuration]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/teamId'请求属性的 minLength 从 '24' 减少到 '0'
  • 已将新的“HOST_EXPOSED、HOST_SECURITY_CHECKUP_NOT_MET、HOST_SSL_CERTIFICATE_STALE、HOST_VERSION_BEHIND、VERSION_BEHIND”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
  • 在请求属性“/oneOf[subschema #12：副本集阈值警报配置]/eventTypeName”中添加了新的“TOO_FEW_HEALTHY_MEMBERS、TOO_MANY_UNHEALTHY_MEMBERS”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 对于“path”请求参数“alertConfigId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 对于“path”请求参数“alertId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 对于“path”请求参数“alertId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 对于“path”请求参数“alertId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/items/userId”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/iamRoleId”请求属性的 minLength 从“24”减少到“0”
  • “/roleId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 对于“path”请求参数“exportBucketId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 对于“path”请求参数“exportBucketId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “onDemandPolicyItem/ ID”请求属性的 minLength 从“24”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “scheduledPolicyItems/items/ ID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/roleId”请求属性的 minLength 从“24”减少到“0”
  • “/ _id”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{cloudProvider}/{roleId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“roleId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“roleId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“roleId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “replicationSpecs/items/zoneId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “replicationSpecs/items/zoneId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “exportBucketId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“exportId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “components/items/privateDownloadDeliveryUrls/items/endpointId”请求属性的 minLength 从“22”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “privateDownloadDeliveryUrls/items/endpointId”请求属性的 minLength 从“22”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetClusterName”请求属性的 minLength 从“1”减少到“0”
  • “targetGroupId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “export/exportBucketId”请求属性的 minLength 从“24”减少到“0”
  • “policies/items/ ID”请求属性的 minLength 已从“24”减少到“0”
  • “policies/items/policyItems/items/ ID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在“results/items/snapshotType”响应属性中添加了新的“fallback”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在“results/items/snapshotType”响应属性中添加了新的“fallback”枚举值
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • 已将新的 'fallback'枚举值添加到 'snapshotType' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetDeploymentItemName”请求属性的 minLength 从“1”减少到“0”
  • “targetProjectId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetDeploymentItemName”请求属性的 minLength 从“1”减少到“0”
  • “targetProjectId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • 对于“path”请求参数“checkpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “indexID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
  • “indexID”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 对于“path”请求参数“archiveId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 对于“path”请求参数“archiveId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 对于“path”请求参数“archiveId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “suggestedIndexes/items/ 影响/items/”响应的属性模式“^([af0-9]{24})$”已被删除
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“查询”请求参数“batchId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “batchId”请求属性的 minLength 从“24”减少到“0”
  • “checkpointId”请求属性的 minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “clusterName”请求属性的 minLength 从“1”减少到“0”
  • “delivery/targetClusterId”请求属性的 minLength 已从“24”减少到“0”
  • “delivery/targetClusterName”请求属性的 minLength 从“1”减少到“0”
  • “delivery/targetGroupId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“jobId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“indexId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
  • “clusterId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “parts/items/clusterId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/clusters/{hostName}/logs/{logName}.gz
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/oneOf[subschema #1: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$”更改为“^([-\w._()])+$”。 _()])$'
  • 在“results/items/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #1: Azure]/vnetName'请求属性的 minLength 从 '38' 减少到 '0'
  • '/oneOf[subschema #2: GCP]/gcpProjectId'请求属性的 minLength 从 '26' 减少到 '0'
  • “/oneOf[subschema #2: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: GCP]/networkName'请求属性的 minLength 从 '36' 减少到 '0'
  • “/oneOf[subschema #3: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
  • 在“/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
  • 在请求属性“/oneOf[subschema #1: Azure]/ 地区 ”中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/oneOf[subschema #1: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$”更改为“^([-\w._()])+$”。 _()])$'
  • 在“results/items/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
DELETE /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 对于“path”请求参数“containerId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 对于“path”请求参数“containerId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
  • 在“/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 对于“path”请求参数“containerId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #1: Azure]/vnetName'请求属性的 minLength 从 '38' 减少到 '0'
  • '/oneOf[subschema #2: GCP]/gcpProjectId'请求属性的 minLength 从 '26' 减少到 '0'
  • “/oneOf[subschema #2: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: GCP]/networkName'请求属性的 minLength 从 '36' 减少到 '0'
  • “/oneOf[subschema #3: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #1: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
  • 在“/oneOf[subschema #1: Azure]/ 地区”响应属性中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
  • 在请求属性“/oneOf[subschema #1: Azure]/ 地区 ”中添加了新的“MEXICO_CENTRAL、NEW_ZEALAND_NORTH、SPAIN_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/queryLogs.gz
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “scopes/items/name”请求属性的 minLength 从“1”减少到“0”
  • 已从请求属性“groupId”中删除模式“^([af0-9]{24})$”
  • “groupId”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “scopes/items/name”请求属性的 minLength 从“1”减少到“0”
  • 已从请求属性“groupId”中删除模式“^([af0-9]{24})$”
  • “groupId”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “accessLogs/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “accessLogs/items/groupId”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“awsKms/requirePrivateNetworking”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “awsKms/roleId”请求属性的 minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“awsKms/requirePrivateNetworking”
  • 添加了新的可选请求属性“awsKms/requirePrivateNetworking”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“results/items/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”响应属性“oneOf”列表中
  • 将“subschema #2: Amazon Web Services Regions”添加到“results/items/regionName”响应属性“oneOf”列表中
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到请求正文 'oneOf' 列表
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/ ID”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • 将“subschema #2: Amazon Web Services Regions”添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”请求属性“oneOf”列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“regionName”请求属性“oneOf”列表中
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到响应的响应正文 'oneOf' 列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”响应属性“oneOf”列表中
  • 将“subschema #2: Amazon Web Services Regions”添加到该响应的“regionName”响应属性“oneOf”列表中
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
  • 将新的“Amazon Web Services”枚举值添加到请求属性“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/cloudProvider”
  • 已将新的“Amazon Web Services”枚举值添加到请求属性“cloudProvider”
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将 '#/components/schemas/AWSKMSEARPrivateEndpoint' 添加到响应的响应正文 'oneOf' 列表
  • 将“subschema #2: Amazon Web Services Regions”添加到“/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/regionName”响应属性“oneOf”列表中
  • 将“subschema #2: Amazon Web Services Regions”添加到该响应的“regionName”响应属性“oneOf”列表中
  • 将新的枚举值“Amazon Web Services”添加到“path”请求参数“cloudProvider”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将“#/components/schemas/DataExplorerEvent”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 对于“path”请求参数“eventId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 将“#/components/schemas/DataExplorerEvent”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
POST /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
DELETE /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
PATCH /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/download
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “instanceName”请求属性的 minLength 从“1”减少到“0”
  • “projectId”请求属性的 minLength 从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetDeploymentItemName”请求属性的 minLength 从“1”减少到“0”
  • “targetProjectId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/analyticsAutoScaling/compute/minInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/maxInstanceSize”变为只读
  • 请求可选属性“replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/autoScaling/compute/minInstanceSize”变为只读
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “replicationSpecs/items/ ID”请求属性的 minLength 从“24”减少到“0”
  • “replicationSpecs/items/zoneId”请求属性的 minLength 从“24”减少到“0”
  • 已添加“clusterType”响应的属性默认值“REPLICASET”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “indexIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “indexIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/invites
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/invites
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/invites
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “destination/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/groupId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “destination/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/liveMigrations/validate/{validationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“validationId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“liveMigrationId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}/cutover
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“liveMigrationId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/autoDefer
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/defer
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/managedSlowMs/disable
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/managedSlowMs/enable
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “results/items/oneOf[subschema #2: Azure]/vnetName”响应的属性模式已从“^([-\w._()])+$”更改为“^([-\w._()])+$”。 _()])$'
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/awsAccountId'请求属性的 minLength 从 '12' 减少到 '0'
  • '/oneOf[subschema #1: Amazon Web Services]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/gcpProjectId'请求属性的 minLength 从 '6' 减少到 '0'
  • “/oneOf[subschema #3: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: GCP]/networkName'请求属性的 minLength 从 '1' 减少到 '0'
  • “containerId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #2: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
DELETE /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“peerId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“peerId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #2: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“peerId”，minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/awsAccountId'请求属性的 minLength 从 '12' 减少到 '0'
  • '/oneOf[subschema #1: Amazon Web Services]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • “/oneOf[subschema #1: Amazon Web Services]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #1: Amazon Web Services]/vpcId'请求属性的 minLength 从 '5' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/ ID'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/containerId'请求属性的 minLength 从 '24' 减少到 '0'
  • '/oneOf[subschema #3: GCP]/gcpProjectId'请求属性的 minLength 从 '6' 减少到 '0'
  • “/oneOf[subschema #3: GCP]/ ID”请求属性的 minLength 从“24”减少到“0”
  • '/oneOf[subschema #3: GCP]/networkName'请求属性的 minLength 从 '1' 减少到 '0'
  • “containerId”请求属性的 minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • '/oneOf[subschema #2: Azure]/vnetName' 响应的属性模式已从 '^([-\w._()])+$' 更改为 '^([-\w._() ])$'
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #1: On-Demand Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2:Periodic Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2: 定期云提供商快照源]/policyItemId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #1: On-Demand Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2:Periodic Cloud Provider Snapshot Source]/groupId”请求属性的 minLength 从“24”减少到“0”
  • “source/oneOf[subschema #2: 定期云提供商快照源]/policyItemId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • 在“results/items/snapshotType”响应属性中添加了新的“fallback”枚举值
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“pipelineRunId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“pipelineRunId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“pipelineName”，minLength 从“1”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 对于“path”请求参数“endpointServiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “endpointId”请求属性的 minLength 从“22”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“22”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 对于“path”请求参数“endpointId”，minLength 从“22”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/namespaces
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/suggestedIndexes
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “suggestedIndexes/items/ 影响/items/”响应的属性模式“^([af0-9]{24})$”已被删除
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“sampleDatasetId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性 'results/items/providerSettings/forcedDiskSizeGBLimit、results/items/providerSettings/forcedInstanceSizeName、results/items/providerSettings/forcedProviderName'
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “snapshotId”请求属性的 minLength 从“24”减少到“0”
  • “targetClusterName”请求属性的 minLength 从“1”减少到“0”
  • “targetGroupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“restoreJobId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“snapshotId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 对于“path”请求参数“clusterName”，minLength 从“1”减少到“0”
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“name”，minLength 从“1”减少到“0”
  • 在响应中添加了可选属性 'providerSettings/forcedDiskSizeGBLimit、providerSettings/forcedInstanceSizeName、providerSettings/forcedProviderName'
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
  • “connections/items/networking/ 访问权限/connectionId”请求属性的 minLength 从“24”减少到“0”
  • “groupId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/accountDetails
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性 'results/items/arn、results/items/errorMessage、results/items/providerAccountId'
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 请求可选属性“_id”变为只读
  • 请求可选属性“interfaceEndpointId”变为只读
  • 请求可选属性“state”变为只读
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 向响应添加了可选属性“arn、errorMessage、providerAccountId”
  • 添加了新的可选请求属性“arn”
DELETE /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 向响应添加了可选属性“arn、errorMessage、providerAccountId”
GET /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:accept
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:reject
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/networking/ 访问权限/connectionId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/networking/ 访问权限/connectionId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “_id”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:start
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:stop
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “/items/teamId”请求属性的 minLength 已从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
  • “teamId”请求属性的 minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/customerX509
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/ldap/userToDNMapping
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify/{requestId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“requestId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 对于“path”请求参数“groupId”，minLength 从“24”减少到“0”
  • “destinationOrgId”请求属性的 minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs
Updated
  • “federationSettingsId”请求属性的 minLength 从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
  • “orgOwnerId”请求属性的 minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
  • “名称”请求属性的 minLength 从“1”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“apiUserId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage/{token}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 对于“path”请求参数“eventId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “/items/teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “groupRoleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“teamIds/items/”中删除了模式“^([af0-9]{24})$”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “groupRoleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“teamIds/items/”中删除了模式“^([af0-9]{24})$”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 对于“path”请求参数“invitationId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “groupRoleAssignments/items/groupId”请求属性的 minLength 从“24”减少到“0”
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”
  • 从请求属性“teamIds/items/”中删除了模式“^([af0-9]{24})$”
  • “teamIds/items/”响应的属性模式“^([af0-9]{24})$”已删除
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 对于“path”请求参数“invoiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 对于“path”请求参数“invoiceId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“/items/description”
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“resourcePolicyId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“resourcePolicyId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“resourcePolicyId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList/{ipAddress}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets/{secretId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • “ID”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams/byName/{teamName}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
  • “/items/ ID”请求属性的 minLength 已从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“teamId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
Updated
  • 对于“path”请求参数“orgId”，minLength 从“24”减少到“0”
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”
POST /api/atlas/v2/users
Updated
  • “ID”请求属性的 minLength 已从“24”减少到“0”
GET /api/atlas/v2/users/{userId}
Updated
  • 对于“path”请求参数“userId”，minLength 从“24”减少到“0”

2025 年 2 月 05 日发布

POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 已将新的“GCP”枚举值添加到请求属性“dataProcessRegion/cloudProvider”中

2025 年 1 月 24 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
  • 已将新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 响应属性
  • 已将新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值添加到请求属性“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 已将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 响应属性
  • 将新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值添加到 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中添加了新的“PUSH_BASED_LOG_EXPORT_DROPPED_LOG”、“PUSH_BASED_LOG_EXPORT_RESUMED”和“PUSH_BASED_LOG_EXPORT_STOPPED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #12: Host Events]/eventTypeName' 响应属性中添加了新的 'PUSH_BASED_LOG_EXPORT_DROPPED_LOG、PUSH_BASED_LOG_EXPORT_RESUMED、PUSH_BASED_LOG_EXPORT_STOPPED'枚举值

2025 年 1 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #14: NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_IP_MIGRATED_FINAL_ROUND、CLUSTER_IP_MIGRATED_FIRST_ROUND、CLUSTER_IP_MIGRATED_SECOND_ROUND、CLUSTER_IP_ROLLED_BACK”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema #14: NDS Audits]/eventTypeName' 响应属性中添加了新的 'CLUSTER_IP_MIGRATED_FINAL_ROUND、CLUSTER_IP_MIGRATED_FIRST_ROUND、CLUSTER_IP_MIGRATED_SECOND_ROUND、CLUSTER_IP_ROLLED_BACK'枚举值

2025 年 1 月 21 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的 'CLUSTER_MIGRATE_BACK_TO_AWS_MANAGED_IP_REQUESTED'枚举值添加到 'results/items/oneOf[subschema #14: NDS Audits]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的 'CLUSTER_MIGRATE_BACK_TO_AWS_MANAGED_IP_REQUESTED'枚举值添加到 '/oneOf[subschema #14: NDS Audits]/eventTypeName' 响应属性

2025 年 1 月 13 日发布

GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 端点已重新激活

2025 年 1 月 10 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • “results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式已从将状态 '200' 的 'string'/'password' 更改为 'string'/''
  • “results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'状态为“200”的响应的属性类型/格式从“字符串”/“密码”更改为“字符串”/“”
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • “results/items/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已从请求正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string' 变更/'password' to 'string'/''
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更to 'string'/''
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/format 从 'string'/'password' 更改为 'string'/''
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更为to 'string'/''
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”请求属性类型/格式从“string”/“password”更改为to 'string'/''
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已从请求正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string' 变更/'password' to 'string'/''
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更to 'string'/''
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/format 从 'string'/'password' 更改为 'string'/''
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 变更为to 'string'/''
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • “/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”请求属性类型/格式从“string”/“password”更改为to 'string'/''
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为 ' string'/''
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret'请求属性类型/格式从 'string'/'password' 更改为'string'/''
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string' 变更/'password' to 'string'/'' for status '200'
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/format 已从 'string'/'password' 更改为 'string'/''（状态为 '200'）
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 'string'/'password'为 'string'/'' 以获取状态 '200'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为 ' string'/'' for status '200'
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/'password' 更改为'string'/'' for status '200'
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 从响应的“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 从响应的“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 从响应的“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 从响应的“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #11: Flex Metric Event Types”
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • “results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式已从将状态 '200' 的 'string'/'password' 更改为 'string'/''
  • “results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #15: Stream Processor Alert Configuration -> subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret'状态为“200”的响应的属性类型/格式从“字符串”/“密码”更改为“字符串”/“”
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • “results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • “results/items/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/ 'password' to 'string'/'' for status '200'
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/ 更改为针对状态“200”，将“password”更改为“string”/“
  • “results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: WebhookNotification]/webhookSecret”响应的属性类型/格式从“string”/“password”更改为' 为 'string'/'' 以获取状态 '200'
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/webhookSecret' 响应的属性类型/格式从 'string'/' 更改为针对状态“200”，将“password”更改为“string”/“
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 删除了请求属性“roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 删除了请求属性“/items/roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 删除了“specs/items/instanceSize”响应属性中的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 删除了“specs/items/instanceSize”响应属性中的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 删除了请求属性“specs/items/instanceSize”的枚举值“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 删除了“specs/items/instanceSize”响应属性中的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 删除了请求属性“specs/items/instanceSize”的枚举值“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”
  • 在“specs/items/instanceSize”响应属性中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 从响应的“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #27: Flex Metric Event Types”
  • 从“results/items/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中删除了“HOST_X509_CERTIFICATE_CERTIFICATE_GENERATED_FOR_SUPPORT_ACCESS”枚举值
  • 将“subschema #27: Flex Metric Event Types”添加到“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 从响应的“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中删除了“subschema #27: Flex Metric Event Types”
  • 从“/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中删除了“HOST_X509_CERTIFICATE_CERTIFICATE_GENERATED_FOR_SUPPORT_ACCESS”枚举值
  • 将“subschema #27: Flex Metric Event Types”添加到“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 删除了“results/items/roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 在 'results/items/roles/items/' 响应属性中添加了新的 'GROUP_BACKUP_MANAGER, GROUP_OBSERVABILITY_VIEWER'枚举值
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 删除了请求属性“roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 删除了请求属性“roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 删除了“roles/items/”响应属性中的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 删除了请求属性“/items/roles/items/”的枚举值“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
已交
  • API路径已删除但未弃用
  • 已添加端点

2025 年 1 月 08 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #11: Flex Metric Event Types”添加到“/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“#/components/schemas/FlexMetricAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
  • 在请求属性“specs/items/instanceSize”中添加了新的“S40_STORAGE_NVME、S50_STORAGE_NVME、S60_STORAGE_NVME、S80_STORAGE_NVME、S90_STORAGE_NVME”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #27: Flex Metric Event Types”添加到“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #27: Flex Metric Event Types”添加到“/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 在 'results/items/roles/items/' 响应属性中添加了新的 'GROUP_BACKUP_MANAGER, GROUP_OBSERVABILITY_VIEWER'枚举值
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • 在“roles/items/”响应属性中添加了新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值
  • 已将新的“GROUP_BACKUP_MANAGER、GROUP_OBSERVABILITY_VIEWER”枚举值添加到请求属性“/items/roles/items/”
GET /api/atlas/v2/groups/{groupId}/streams/activeVpcPeeringConnections
已交
  • 已添加端点

2025 年 1 月 03 日发布

GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 在响应中添加了可选属性“services/clusters/items/futureInbound, services/clusters/items/futureOutbound”

2025 年 1 月 01 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-01-01”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
  • API版本为“2023-01-01”的端点已被删除，因为已到其日落日期“2025-01-01”

2024 年 12 月 19 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId”响应的属性模式'^(已添加 [af0-9]{24})$'
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#10:SMSNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#12:UserNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #13: VictorOpsNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#1:DatadogNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#2:EmailNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#3:GroupNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #4: HipChat notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#7:OrgNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#9: Slack ]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/' 中添加了新的 'CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#10:SMSNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#12:UserNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #13: VictorOpsNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#1:DatadogNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#2:EmailNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#3:GroupNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #4: HipChat notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#7:OrgNotification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #10: NDS X509 用户身份验证警报配置]” / 通知/items/oneOf[subschema#9: Slack ]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #12:副本集阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 已将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #10: 短信通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #13: VictorOps 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #14: Webhook 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #1: Datadog 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #2: 电子邮件通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #3: 群组通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #8: PagerDuty 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items /oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式“^([af0-9]{24})$”添加到请求属性“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #10: 短信通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #11: 团队通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #12: 用户通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #13: VictorOps 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #14: Webhook 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #1: Datadog 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #2: 电子邮件通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #3: 群组通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #5: Microsoft Teams 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #8: PagerDuty 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf [subschema #9: Slack notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #10: SMS notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #11: Team notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #12: User notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #13: VictorOps notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #14: Webhook notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #1: Datadog notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #2: Email notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #3: Group notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #4: HipChat 通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #5: Microsoft Teams notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #6: OpsGenie notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #7: 组织通知]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #8: PagerDuty notification]/notifierId'
  • 将模式'^([af0-9]{24})$' 添加到请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/ oneOf[subschema #9: Slack notification]/notifierId'
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9] {24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9 ]{24})$' 已添加
  • 在“/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/' 中添加了新的 'CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #4: Host Metric Alerts]/”响应属性
  • 在“/oneOf[subschema #7: Any other Alerts]/eventTypeName/oneOf[subschema #15: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold”响应属性
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId”响应的属性模式'^(已添加 [af0-9]{24})$'
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId”响应的属性模式'^([ af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #12: 副本集阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式“^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #12: User notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • “results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId”响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0-9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #10: SMS notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #11: Team notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #12: User notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #13: VictorOps notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #14: Webhook notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #2: Email notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #3: Group notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #4: HipChat notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #5: Microsoft Teams notification]/notifierId' 响应的属性模式'^([af0 -9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #6: OpsGenie notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #7: Org notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #8: PagerDuty notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #9: Slack notification]/notifierId' 响应的属性模式'^([af0- 9]{24})$' 已添加
  • 在“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName/oneOf[subschema #3: Data Protection Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • “results/items/tenantId”响应的属性模式为“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • “/tenantId”请求属性的 minLength 从“36”减少到“0”
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/tenantId”）
  • “/tenantId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • “/tenantId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
DELETE /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在响应中添加了可选属性“deletable”
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在响应中添加了可选属性“deletable”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • “azureServicePrincipals/items/atlasAzureAppId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “azureServicePrincipals/items/servicePrincipalId”响应的属性模式为“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “azureServicePrincipals/items/tenantId”响应的属性模式为“^[0-9a-fA-F]{8}\b-[0-9a-fA-F” ]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“/roleId”
  • “/atlasAzureAppId”请求属性的 minLength 已从“32”减少到“0”
  • “/servicePrincipalId”请求属性的 minLength 已从“32”减少到“0”
  • “/tenantId”请求属性的 minLength 从“32”减少到“0”
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/atlasAzureAppId”）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/servicePrincipalId”）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性“/tenantId”）
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 已添加“copySettings/items/zoneId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“deleteCopiedBackups/items/zoneId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 已添加“copySettings/items/zoneId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“deleteCopiedBackups/items/zoneId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“copySettings/items/zoneId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“deleteCopiedBackups/items/zoneId”
  • 已添加“copySettings/items/zoneId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“deleteCopiedBackups/items/zoneId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 已添加“clusterId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 已添加“customZoneMapping/additionalProperties/”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 已添加“/items/cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“/items/cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“/items/cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Amazon Web Services/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Azure/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ GCP/roleId”
  • 已添加“cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 已添加“cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Amazon Web Services/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ Azure/roleId”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“cloudProviderConfig/ GCP/roleId”
  • 已添加“cloudProviderConfig/ Amazon Web Services/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ Azure/roleId”响应的属性模式“^([af0-9]{24})$”
  • 已添加“cloudProviderConfig/ GCP/roleId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“results/items/oneOf[subschema #13: Host Metric Events]/”响应属性
  • Added the new 'ATLAS_MAINTENANCE_PROTECTED_HOURS_CREATED, ATLAS_MAINTENANCE_PROTECTED_HOURS_MODIFIED, ATLAS_MAINTENANCE_PROTECTED_HOURS_REMOVED, CLUSTER_CANCELING_SHARD_DRAIN_REQUESTED, PROJECT_SCHEDULED_MAINTENANCE_OUTSIDE_OF_PROTECTED_HOURS' 枚举 values to the 'results/items/oneOf[subschema #14: NDS Audits]/eventTypeName' response 属性
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #6: CPS Backup Compliance Policy Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“QUERY_SPILL_TO_DISK_DURING_SORT”鉴别器映射键添加到“/oneOf[subschema #13: Host Metric Events]/”响应属性
  • Added the new 'ATLAS_MAINTENANCE_PROTECTED_HOURS_CREATED, ATLAS_MAINTENANCE_PROTECTED_HOURS_MODIFIED, ATLAS_MAINTENANCE_PROTECTED_HOURS_REMOVED, CLUSTER_CANCELING_SHARD_DRAIN_REQUESTED, PROJECT_SCHEDULED_MAINTENANCE_OUTSIDE_OF_PROTECTED_HOURS' 枚举 values to the '/oneOf[subschema #14: NDS Audits]/eventTypeName' response 属性
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #6: CPS Backup Compliance Policy Event Types]/”响应属性中添加了新的“CPS_DATA_PROTECTION_APPROVED_FOR_DISABLEMENT”枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 添加了新的可选请求属性“targetProjectId”
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • “results/items/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0 -9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “results/items/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0 -9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • '/oneOf[subschema #2: Azure]/azureDirectoryId'请求属性的 minLength 从 '32' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/azureSubscriptionId'请求属性的 minLength 从 '32' 减少到 '0'
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureDirectoryId'）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureSubscriptionId'）
  • “/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • “/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • '/oneOf[subschema #2: Azure]/azureDirectoryId'请求属性的 minLength 从 '32' 减少到 '0'
  • '/oneOf[subschema #2: Azure]/azureSubscriptionId'请求属性的 minLength 从 '32' 减少到 '0'
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureDirectoryId'）
  • 删除了模式'^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4} \b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b -[0-9a-fA-F]{12}$'（来自请求属性'/oneOf[subschema #2: Azure]/azureSubscriptionId'）
  • “/oneOf[subschema #2: Azure]/azureDirectoryId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
  • “/oneOf[subschema #2: Azure]/azureSubscriptionId”响应的属性模式“^[0-9a-fA-F]{8}\b-[0-” 9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$' 已删除
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 已添加“groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 已添加“iamRoleId”响应的属性模式“^([af0-9]{24})$”
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“iamRoleId”
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“iamRoleId”
GET /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • “results/items/secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
Updated
  • “秘密”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 已添加“results/items/ _id”响应的属性模式“^([af0-9]{24})$”
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
Updated
  • 已将模式“^([af0-9]{24})$”添加到请求属性“_id”
  • 已添加“_id”响应的属性模式'^([af0-9]{24})$'
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
Updated
  • 已添加“_id”响应的属性模式'^([af0-9]{24})$'
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 409 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 添加了状态为“ 409 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 端点已弃用
  • 添加了新的可选“查询”请求参数“orgMembershipStatus”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • “results/items/cidrBlock”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))((%2[fF]|\/)[0-9]{1,3})+$' to ' ^((([0-9]{1,3}\.){3}[0-9]{1,3})|(:{0,2}([0-9af]{1,4}:){0,7}[0-9af]{1,4}[:]{0,2}))((%2[fF] |/)[0-9]{1,3})+$'
  • “results/items/ipAddress”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))$' 为 '^((25[0-5]|(2[0-4]|1\d |[1-9]|)\d)(\.(?!$)|$)){4}|([0-9af]{1,4}:){7}[0-9af]{1,4}$'
  • “results/items/lastUsedAddress”响应的属性模式“^((([0-9]{1,3}\.){3}[0 -9]{1,3})|([\:]{0,2}([0-9af]{1 ,4}\:){0,7}[0-9af]{1,4}[\:]{0 ,2}))$' 已删除
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • “results/items/cidrBlock”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))((%2[fF]|\/)[0-9]{1,3})+$' to ' ^((([0-9]{1,3}\.){3}[0-9]{1,3})|(:{0,2}([0-9af]{1,4}:){0,7}[0-9af]{1,4}[:]{0,2}))((%2[fF] |/)[0-9]{1,3})+$'
  • “results/items/ipAddress”响应的属性模式已从“^((([0-9]{1,3}\.){3}[ 0-9]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))$' 为 '^((25[0-5]|(2[0-4]|1\d |[1-9]|)\d)(\.(?!$)|$)){4}|([0-9af]{1,4}:){7}[0-9af]{1,4}$'
  • “results/items/lastUsedAddress”响应的属性模式“^((([0-9]{1,3}\.){3}[0 -9]{1,3})|([\:]{0,2}([0-9af]{1 ,4}\:){0,7}[0-9af]{1,4}[\:]{0 ,2}))$' 已删除
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • “cidrBlock”响应的属性模式已从 '^((([0-9]{1,3}\.){3}[0- 9]{1,3})|([\:]{0,2}([0-9af]{1, 4}\:){0,7}[0-9af]{1,4}[\:]{0, 2}))((%2[fF]|\/)[0-9]{1,3})+$' to '^((( [0-9]{1,3}\.){3}[0-9]{1,3} )|(:{0,2}([0-9af]{1,4}:){0,7} [0-9af]{1,4}[:]{0,2}))((%2[fF]|/)[ 0-9]{1,3})+$'
  • “ipAddress”响应的属性模式已从 '^((([0-9]{1,3}\.){3}[0- 9]{1,3})|([\:]{0,2}([0-9af]{1, 4}\:){0,7}[0-9af]{1,4}[\:]{0, 2}))$' 为 '^((25[0-5]|(2[0-4]|1\d|[1-9]|)\d)(\.(?!$)|$)){4}|([0-9af]{1,4}:){7}[0-9af]{1,4}$'
  • “lastUsedAddress”响应的属性模式“^((([0-9]{1,3}\.){3}[0-9 ]{1,3})|([\:]{0,2}([0-9af]{1,4}\:){0,7}[0-9af]{1,4}[\:]{0,2}))$' 已删除
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“clusters/items/”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“organizations/items/”
  • 已将模式“^([af0-9]{24})$”添加到请求属性“projects/items/”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AWS_CMK_PRIVATE_NETWORKING、ATLAS_NDS_AZURE_CMK_PRIVATE_NETWORKING”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 在“lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AWS_CMK_PRIVATE_NETWORKING、ATLAS_NDS_AZURE_CMK_PRIVATE_NETWORKING”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 将模式“^([af0-9]{24})$”添加到请求属性“filters/clusterIds/items/”
  • 将模式“^([af0-9]{24})$”添加到请求属性“filters/groupIds/items/”
  • 已添加“results/items/groupId”响应的属性模式“^([af0-9]{24})$”
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • “results/items/secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
Updated
  • “secrets/items/secret”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
Updated
  • “秘密”响应的属性模式“^mdb_sa_sk_[0-9a-zA-Z_-]{40}$”已删除
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • “maxServiceAccountSecretValidityInHours”请求属性的最大值已设立为“8760.00”
  • “maxServiceAccountSecretValidityInHours”请求属性的最小值已设立为“8.00”
POST /api/atlas/v2/users
Updated
  • “teamIds/items/”请求属性的 minLength 从“24”减少到“0”

2024 年 12 月 09 日发布

GET /api/atlas/v2/clusters
Updated
  • “results/items/clusters/items/name”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-] *)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9 -]*$'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • “results/items/oneOf[subschema #2: Cluster Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #3: Host Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #4: Host Metric Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z 0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA -Z0-9-]*$'
  • “results/items/oneOf[subschema #5: ReplicaSet Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • “results/items/oneOf[subschema #2: Cluster Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #3: Host Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
  • “results/items/oneOf[subschema #4: Host Metric Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z 0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA -Z0-9-]*$'
  • “results/items/oneOf[subschema #5: ReplicaSet Alerts]/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA- Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • '/oneOf[subschema #2: Cluster Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #3: Host Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #4: Host Metric Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0 -9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #5: ReplicaSet Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • '/oneOf[subschema #2: Cluster Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #3: Host Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #4: Host Metric Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0 -9-]*)?[a-zA-Z0-9]+$' 为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • '/oneOf[subschema #5: ReplicaSet Alerts]/clusterName' 响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0- 9-]*)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • “results/items/name”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“targetClusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “results/items/delivery/targetClusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)”更改?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-] *$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“clusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“delivery/targetClusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a -zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “results/items/delivery/targetClusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)”更改?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-] *$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “delivery/targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a- zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • “results/items/scopes/items/name”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-] *)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9 -]*$'
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 已将请求属性“scopes/items/name”的模式从“^([a-zA-Z0-9][a-zA-Z0-9-]*)? [a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]* $'
  • “scopes/items/name”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • “scopes/items/name”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 已将请求属性“scopes/items/name”的模式从“^([a-zA-Z0-9][a-zA-Z0-9-]*)? [a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]* $'
  • “scopes/items/name”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • “results/items/name”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/flexClusters
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/flexClusters/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/download
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “instanceName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “results/items/instanceName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • 已将请求属性“instanceName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “instanceName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs/{restoreJobId}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “instanceName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots/{snapshotId}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 已将“path”请求参数“instanceName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 已将“path”请求参数“instanceName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 已将“path”请求参数“instanceName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 已将“path”请求参数“instanceName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 已将“path”请求参数“instanceName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • “clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • “results/items/name”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 已将请求属性“名称”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • 已将请求属性“targetClusterName”的模式从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA -Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “targetClusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “results/items/serverlessInstanceName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
  • “serverlessInstanceName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$' to '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已更改“路径”请求参数“名称”的模式，从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '
  • “名称”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA- Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$'
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • “results/items/lineItems/items/clusterName”响应的属性模式已从“^([a-zA-Z0-9][a-zA-Z0-9-]” *)?[a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9 -]*$'
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • “lineItems/items/clusterName”响应的属性模式已从 '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[ a-zA-Z0-9]+$' 改为 '^[a-zA-Z0-9][a-zA-Z0-9-]*$ '

2024 年 12 月 05 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema #3：数据保护事件类型”添加到“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema #3：数据保护事件类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”请求属性“oneOf”列表
  • 将“subschema #3：数据保护事件类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED”、“SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 已将新的 'SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED'枚举值添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #3：数据保护事件类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED”、“SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #3：数据保护事件类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED”、“SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema #3：数据保护事件类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”请求属性“oneOf”列表
  • 将“subschema #3：数据保护事件类型”添加到“/oneOf[subschema #1：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED”、“SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 已将新的 'SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED'枚举值添加到请求属性'/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“subschema #15：数据保护事件类型”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“subschema #15：数据保护事件类型”添加到“results/items/oneOf[subschema #7: Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 在“results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #15：数据保护事件类型”添加到“/oneOf[subschema #7：任何其他警报]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED”、“SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 在 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性中添加了新的 'SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED'枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema #15：数据保护事件类型”添加到“/oneOf[subschema #7：任何其他警报]/eventTypeName”响应属性“oneOf”列表中
  • 在“/oneOf[subschema #3: Host Alerts]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED”、“SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 在 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 响应属性中添加了新的 'SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED'枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“subschema #3：数据保护事件类型”添加到“results/items/oneOf[subschema #1: Any other Alert Configurations]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName”响应属性中添加了新的“SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了可选属性 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/forcedInstanceSize、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs /有效实例大小, 结果/项目/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/有效实例大小, 结果/项目/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/forcedInstanceSize，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/forcedInstanceSize' 到响应
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/forcedInstanceSize、replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/forcedInstanceSize、replicationSpecs/items/regionConfigs /items/oneOf[subschema #:2 Azure区域复制规范]/electableSpecs/ectiveInstanceSize, replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP区域复制规范]/electableSpecs/forcedInstanceSize, replicationSpecs/items响应4
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在响应中添加了可选属性“providerSettings/oneOf[subschema #4: Cloud Service Provider Settings for a Cluster]/forcedInstanceSizeName”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/forcedInstanceSize、replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/forcedInstanceSize、replicationSpecs/items/regionConfigs /items/oneOf[subschema #:2 Azure区域复制规范]/electableSpecs/ectiveInstanceSize, replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP区域复制规范]/electableSpecs/forcedInstanceSize, replicationSpecs/items响应4
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/forcedInstanceSize、replicationSpecs/items/regionConfigs/items/oneOf[subschema1 #: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/forcedInstanceSize、replicationSpecs/items/regionConfigs /items/oneOf[subschema #:2 Azure区域复制规范]/electableSpecs/ectiveInstanceSize, replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP区域复制规范]/electableSpecs/forcedInstanceSize, replicationSpecs/items响应4
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 在响应中添加了可选属性“results/items/stateReason”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 在响应中添加了可选属性“stateReason”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 在响应中添加了可选属性“stateReason”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 在响应中添加了可选属性“numPartitions”
  • 添加了新的可选请求属性“numPartitions”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 在响应中添加了可选属性“/items/numPartitions”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 在响应中添加了可选属性“numPartitions”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 在响应中添加了可选属性“numPartitions”
  • 添加了新的可选请求属性“numPartitions”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/performanceAdvisor/suggestedIndexes
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“customOpensslCipherConfigTls12, tlsCipherConfigMode”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“customOpensslCipherConfigTls12, tlsCipherConfigMode”
  • 添加了新的可选请求属性“customOpensslCipherConfigTls12, tlsCipherConfigMode”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 在响应中添加了可选属性“/items/latestDefinition/numPartitions、/items/statusDetail/items/mainIndex/definition/numPartitions、/items/statusDetail/items/stagedIndex/definition/numPartitions”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 在响应中添加了可选属性“latestDefinition/numPartitions, statusDetail/items/mainIndex/definition/numPartitions, statusDetail/items/stagedIndex/definition/numPartitions”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 在响应中添加了可选属性“/items/latestDefinition/numPartitions、/items/statusDetail/items/mainIndex/definition/numPartitions、/items/statusDetail/items/stagedIndex/definition/numPartitions”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 在响应中添加了可选属性“latestDefinition/numPartitions, statusDetail/items/mainIndex/definition/numPartitions, statusDetail/items/stagedIndex/definition/numPartitions”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 在响应中添加了可选属性“latestDefinition/numPartitions, statusDetail/items/mainIndex/definition/numPartitions, statusDetail/items/stagedIndex/definition/numPartitions”
  • 添加了新的可选请求属性“definition/oneOf[subschema #1：文本搜索索引定义]/numPartitions、definition/oneOf[subschema #2：向量搜索索引定义]/numPartitions”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 在响应中添加了可选属性“latestDefinition/numPartitions, statusDetail/items/mainIndex/definition/numPartitions, statusDetail/items/stagedIndex/definition/numPartitions”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 在响应中添加了可选属性“latestDefinition/numPartitions, statusDetail/items/mainIndex/definition/numPartitions, statusDetail/items/stagedIndex/definition/numPartitions”
  • 添加了新的可选请求属性“definition/oneOf[subschema #1：文本搜索索引定义]/numPartitions、definition/oneOf[subschema #2：向量搜索索引定义]/numPartitions”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“subschema #34：访问事件类型”添加到“results/items/oneOf[subschema #1: Any other Events]/eventTypeName”响应属性“oneOf”列表中
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/”响应属性中添加了新的“CLUSTER_CONNECTION_SAMPLE_COLLECTION_FIELD_NAMES_AND_TYPES”枚举值
  • 在“results/items/oneOf[subschema #12: Host Events]/eventTypeName”响应属性中添加了新的“HOST_SSH_SESSION_ENDED、SSH_KEY_NDS_HOST_ACCESS_ATTEMPT、SSH_KEY_NDS_HOST_ACCESS_GRANTED、SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED”枚举值
  • 在“results/items/oneOf[subschema #14: NDS Audits]/eventTypeName”响应属性中添加了新的“SERVERLESS_UPGRADE_STARTED、SSL_CERTIFICATE_ISSUED”枚举值
  • 添加了可选属性 'results/items/oneOf[subschema #12: Host Events]/deskLocation, results/items/oneOf[subschema #12: Host Events]/employeeIdentifier, results/items/oneOf[subschema #13: Host Metric Events]/deskLocation, results/items/oneOf[subschema #13: Host Metric Events]/employeeIdentifier' 到响应
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“subschema #34：访问事件类型”添加到“/oneOf[subschema #1：任何其他事件]/eventTypeName”响应属性“oneOf”列表中
  • 将新的 'CLUSTER_CONNECTION_SAMPLE_COLLECTION_FIELD_NAMES_AND_TYPES'枚举值添加到 '/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 响应属性
  • 在 '/oneOf[subschema #12: Host Events]/eventTypeName' 响应属性中添加了新的 'HOST_SSH_SESSION_ENDED、SSH_KEY_NDS_HOST_ACCESS_ATTEMPT、SSH_KEY_NDS_HOST_ACCESS_GRANTED、SSH_KEY_NDS_HOST_ACCESS_REFRESHED、SSH_KEY_NDS_HOST_ACCESS_REQUESTED'枚举值
  • 在“/oneOf[subschema #14: NDS Audits]/eventTypeName”响应属性中添加了新的“SERVERLESS_UPGRADE_STARTED、SSL_CERTIFICATE_ISSUED”枚举值
  • 添加了可选属性“/oneOf[subschema #12: Host Events]/deskLocation、/oneOf[subschema #12: Host Events]/employeeIdentifier、/oneOf[subschema #13: Host Metric Events]/deskLocation ，/oneOf[subschema #13: Host Metric Events]/employeeIdentifier' 到响应
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 在响应中添加了可选属性“protectedHours, timeZoneId”
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 添加了新的可选请求属性“protectedHours”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“Https”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 从“results/items/connections/items/”响应属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 已从响应的 'results/items/connections/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/StreamsWebAPIConnection'
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“Https”鉴别器映射键添加到“connections/items/”请求属性
  • 从“connections/items/”请求属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“Https”鉴别器映射键添加到“connections/items/”响应属性
  • 从“connections/items/”响应属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已从响应的 'connections/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/StreamsWebAPIConnection'
  • 在请求属性“connections/items/type”中添加了新的“Https”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/accountDetails
Updated
  • 在响应中添加了可选属性“cidrBlock”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“Https”鉴别器映射键添加到“connections/items/”响应属性
  • 从“connections/items/”响应属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已从响应的 'connections/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/StreamsWebAPIConnection'
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“Https”鉴别器映射键添加到“connections/items/”响应属性
  • 从“connections/items/”响应属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已从响应的 'connections/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/StreamsWebAPIConnection'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“Https”鉴别器映射键添加到“results/items/”响应属性
  • 从“results/items/”响应属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 已从响应的 'results/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/StreamsWebAPIConnection'
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“Https”映射键添加到请求鉴别器
  • 从请求鉴别器中删除了“WebAPI”映射键
  • 将 '#/components/schemas/StreamsHttpsConnection' 添加到请求正文 'oneOf' 列表
  • 已将“Https”映射键添加到响应状态“200”的响应鉴别器
  • 已从响应状态“200”的响应鉴别器中删除“WebAPI”映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/StreamsWebAPIConnection”
  • 已将新的 'Https'枚举值添加到请求属性'/type'
  • 已将新的 'Https'枚举值添加到请求属性'type'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“Https”映射键添加到响应状态“200”的响应鉴别器
  • 已从响应状态“200”的响应鉴别器中删除“WebAPI”映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/StreamsWebAPIConnection”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“Https”映射键添加到请求鉴别器
  • 从请求鉴别器中删除了“WebAPI”映射键
  • 将 '#/components/schemas/StreamsHttpsConnection' 添加到请求正文 'oneOf' 列表
  • 已将“Https”映射键添加到响应状态“200”的响应鉴别器
  • 已从响应状态“200”的响应鉴别器中删除“WebAPI”映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的响应正文“oneOf”列表中
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/StreamsWebAPIConnection”
  • 已将新的 'Https'枚举值添加到请求属性'/type'
  • 已将新的 'Https'枚举值添加到请求属性'type'
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“Https”鉴别器映射键添加到“connections/items/”响应属性
  • 从“connections/items/”响应属性中删除了“WebAPI”鉴别器映射键
  • 将“#/components/schemas/StreamsHttpsConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已从响应的 'connections/items/' 响应属性'oneOf' 列表中删除 '#/components/schemas/StreamsWebAPIConnection'
GET /api/atlas/v2/orgs
Updated
  • 在响应中添加了可选属性“results/items/skipDefaultAlertsSettings”
POST /api/atlas/v2/orgs
Updated
  • 在响应中添加了可选属性“组织/skipDefaultAlertsSettings, skipDefaultAlertsSettings”
  • 添加了新的可选请求属性“skipDefaultAlertsSettings”
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 在响应中添加了可选属性“skipDefaultAlertsSettings”
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 在响应中添加了可选属性“skipDefaultAlertsSettings”
  • 添加了新的可选请求属性“skipDefaultAlertsSettings”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_BACKFILL_SUPPORT”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 已将新的“ATLAS_NDS_BACKFILL_SUPPORT”枚举值添加到“lineItems/items/sku”响应属性中
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 响应属性“usernames”变为必填项

2024 年 12 月 03 日发布

GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 将新的“BYPASS_DEFAULT_MAX_TIME_MS”枚举值添加到“/items/actions/items/ 动作”响应属性中
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 将新的“BYPASS_DEFAULT_MAX_TIME_MS”枚举值添加到“actions/items/ 动作”响应属性中
  • 在请求属性“actions/items/ 动作 ”中添加了新的“BYPASS_DEFAULT_MAX_TIME_MS”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 将新的“BYPASS_DEFAULT_MAX_TIME_MS”枚举值添加到“actions/items/ 动作”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 将新的“BYPASS_DEFAULT_MAX_TIME_MS”枚举值添加到“actions/items/ 动作”响应属性中
  • 在请求属性“actions/items/ 动作 ”中添加了新的“BYPASS_DEFAULT_MAX_TIME_MS”枚举值
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
Updated
  • 请求可选属性“clusterType”变为非只读属性
  • 请求可选属性“名称”变为非只读属性
  • 请求可选属性“versionReleaseSystem”变为非只读属性
  • 在请求属性“versionReleaseSystem”中添加了新的“CONTINUOUS”枚举值
  • 在请求属性“clusterType”中添加了新的“GEOSHARDED、SHARDED”枚举值
  • 添加了新的可选请求属性“acceptDataRisksAndForceReplicaSetReconfig、backupEnabled、biConnector、configServerManagementMode、diskWarmingMode、encryptionAtRestProvider、globalClusterSelfManagedSharding、labels、mongoDBEmployeeAccessGrant、mongoDBMajorVersion、paused、pitEnabled、redactClientLogData、replicaSetScalingStrategy、replicationSpecs、rootCertType”

2024 年 11 月 22 日发布

GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_MONGODB_VERSION_EOL_EXTENSION_ACCEPTED、ORG_MONGODB_VERSION_EOL_EXTENSION_CANCELLED、ORG_MONGODB_VERSION_EOL_EXTENSION_PENDING”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_MONGODB_VERSION_EOL_EXTENSION_ACCEPTED、ORG_MONGODB_VERSION_EOL_EXTENSION_CANCELLED、ORG_MONGODB_VERSION_EOL_EXTENSION_PENDING”枚举值

2024 年 11 月 13 日发布

GET /api/atlas/v2/groups
Updated
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”
POST /api/atlas/v2/groups
Updated
  • 已添加“withDefaultAlertsSettings”请求属性默认值“true”
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”
GET /api/atlas/v2/groups/{groupId}
Updated
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/ datadogRegion' 响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 已将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/ datadogRegion' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知]/ datadogRegion' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的 'US1_FED'枚举值添加到 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知] /datadogRegion' 响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知 /items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog通知]/datadogRegion'
  • 在请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 已将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion '
  • 在请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 已将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion '
  • 已将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion'
  • 在请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 已将新的“US1_FED”枚举值添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion '
  • 在请求属性'/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'US1_FED'枚举值添加到 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知] /datadogRegion' 响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知 /items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'US1_FED'枚举值添加到 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知] /datadogRegion' 响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知 /items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的 'US1_FED'枚举值添加到 '/oneOf[subschema #10: NDS X509 用户身份验证警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知] /datadogRegion' 响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #12: 副本集阈值警报配置]/ 通知 /items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #4: 账单阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 在“/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应中添加了新的“US1_FED”枚举值属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog通知]/datadogRegion'
  • 在请求属性'/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 已将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion '
  • 在请求属性'/oneOf[subschema #13: Serverless Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #1: Any other Alert Configurations]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #2: App Services Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 已将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion '
  • 已将新的 'US1_FED'枚举值添加到请求属性'/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion'
  • 在请求属性'/oneOf[subschema #5: Cluster Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 已将新的“US1_FED”枚举值添加到请求属性“/oneOf[subschema #6: Cps 备份阈值警报配置]/通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion '
  • 在请求属性'/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #8: Host Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
  • 在请求属性'/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知 /items/oneOf[subschema #1: Datadog notification]/datadogRegion' 中添加了新的 'US1_FED'枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog 通知]/datadogRegion' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #11: Replica Set Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #12: Replica Set Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/ datadogRegion' 响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #13: Serverless Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #14: Stream Processor Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #1: Any other Alert Configurations]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #2: App Services Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 已将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/ datadogRegion' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #5: Cluster Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #6: Cps 备份阈值警报配置]/ 通知/items/oneOf[subschema #1: Datadog 通知]/ datadogRegion' 响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
  • 将新的“US1_FED”枚举值添加到“results/items/oneOf[subschema #8: Host Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion”响应属性
  • 将新的 'US1_FED'枚举值添加到 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/ 通知/items/oneOf[subschema #1: Datadog notification]/datadogRegion ' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 将“FLEX”鉴别器映射键添加到“providerSettings”请求属性
  • 将“#/components/schemas/ClusterFlexProviderSettings”添加到“providerSettings”请求属性“oneOf”列表
  • 将“FLEX”鉴别器映射键添加到“providerSettings”响应属性
  • 将“#/components/schemas/ClusterFlexProviderSettings”添加到响应的“providerSettings”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 添加了可选属性 'results/items/clusterName、results/items/parts/items/completedTime、results/items/parts/items/fcv、results/items/parts/items/machineId、results/items/parts/items/replicaState ' 到响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 在响应中添加了可选属性“clusterName、parts/items/completedTime、parts/items/fcv、parts/items/machineId、parts/items/replicaState”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 在响应中添加了可选属性“clusterName、parts/items/completedTime、parts/items/fcv、parts/items/machineId、parts/items/replicaState”
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“/items/actions/items/ 动作”响应属性中添加了新的“CHECK_METADATA_CONSISTENCY、ENABLE_SHARDING”枚举值
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“CHECK_METADATA_CONSISTENCY、ENABLE_SHARDING”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“CHECK_METADATA_CONSISTENCY、ENABLE_SHARDING”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“CHECK_METADATA_CONSISTENCY、ENABLE_SHARDING”枚举值
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“CHECK_METADATA_CONSISTENCY、ENABLE_SHARDING”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“CHECK_METADATA_CONSISTENCY、ENABLE_SHARDING”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #33: Version Audit Types]/”响应属性中添加了新的“CLUSTER_OS_FIXED、CLUSTER_OS_UNFIXED”枚举值
  • 在“results/items/oneOf[subschema #14: NDS Audits]/eventTypeName”响应属性中添加了新的“FLEX_UPGRADE_STARTED、RELOAD_SSL_ON_PROCESSES_REQUESTED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #1: Any other Events]/eventTypeName/oneOf[subschema #33: Version Audit Types]/”响应属性中添加了新的“CLUSTER_OS_FIXED、CLUSTER_OS_UNFIXED”枚举值
  • 已将新的“FLEX_UPGRADE_STARTED、RELOAD_SSL_ON_PROCESSES_REQUESTED”枚举值添加到“/oneOf[subschema #14: NDS Audits]/eventTypeName”响应属性
GET /api/atlas/v2/groups/{groupId}/flexClusters
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/flexClusters
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/flexClusters/{name}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/flexClusters/{name}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/download
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/restoreJobs/{restoreJobId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/flexClusters/{name}/backup/snapshots/{snapshotId}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/flexClusters:tenantUpgrade
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“WebAPI”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
  • 将新的“WebAPI”枚举值添加到“results/items/connections/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“WebAPI”鉴别器映射键添加到“connections/items/”请求属性
  • 将 '#/components/schemas/StreamsWebAPIConnection' 添加到 'connections/items/'请求属性'oneOf' 列表
  • 将“WebAPI”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“connections/items/type”响应属性中
  • 在请求属性“connections/items/type”中添加了新的“WebAPI”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“WebAPI”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“connections/items/type”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“WebAPI”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“connections/items/type”响应属性中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“WebAPI”鉴别器映射键添加到“results/items/”响应属性
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在“results/items/type”响应属性中添加了新的“WebAPI”枚举值
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“WebAPI”映射键添加到请求鉴别器
  • 将 '#/components/schemas/StreamsWebAPIConnection' 添加到请求正文 'oneOf' 列表
  • 已将“WebAPI”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“WebAPI”枚举值
  • 已将新的“WebAPI”枚举值添加到请求属性“/type”
  • 在请求属性“type”中添加了新的“WebAPI”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“WebAPI”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“WebAPI”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“WebAPI”映射键添加到请求鉴别器
  • 将 '#/components/schemas/StreamsWebAPIConnection' 添加到请求正文 'oneOf' 列表
  • 已将“WebAPI”映射键添加到响应状态“200”的响应鉴别器
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的响应正文“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“/type”响应属性
  • 在“type”响应属性中添加了新的“WebAPI”枚举值
  • 已将新的“WebAPI”枚举值添加到请求属性“/type”
  • 在请求属性“type”中添加了新的“WebAPI”枚举值
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“WebAPI”鉴别器映射键添加到“connections/items/”响应属性
  • 将“#/components/schemas/StreamsWebAPIConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
  • 已将新的“WebAPI”枚举值添加到“connections/items/type”响应属性中
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_SERVICE_ACCOUNT_SECRETS_EXPIRED、ORG_SERVICE_ACCOUNT_SECRETS_EXPIRING、ORG_SERVICE_ACCOUNT_SECRETS_NO_LONGER_EXPIRED、ORG_SERVICE_ACCOUNT_SECRETS_NO_LONGER_EXPIRING”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema #8: Org Events]/eventTypeName”响应属性中添加了新的“ORG_SERVICE_ACCOUNT_SECRETS_EXPIRED、ORG_SERVICE_ACCOUNT_SECRETS_EXPIRING、ORG_SERVICE_ACCOUNT_SECRETS_NO_LONGER_EXPIRED、ORG_SERVICE_ACCOUNT_SECRETS_NO_LONGER_EXPIRING”枚举值
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 已添加“withDefaultAlertsSettings”响应的属性默认值“true”

2024 年 11 月 07 日发布

GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“genAIFeaturesEnabled”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“genAIFeaturesEnabled”
  • 添加了新的可选请求属性“genAIFeaturesEnabled”

2024 年 10 月29 日发布

GET /api/atlas/v2/groups/{groupId}/serviceAccounts
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/serviceAccounts
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/accessList/{ipAddress}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}/secrets/{secretId}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/serviceAccounts/{clientId}:invite
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts
已交
  • 已添加端点
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
已交
  • 已添加端点
PATCH /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList
已交
  • 已添加端点
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/accessList/{ipAddress}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/groups
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets
已交
  • 已添加端点
DELETE /api/atlas/v2/orgs/{orgId}/serviceAccounts/{clientId}/secrets/{secretId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“maxServiceAccountSecretValidityInHours”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“maxServiceAccountSecretValidityInHours”
  • 添加了新的可选请求属性“maxServiceAccountSecretValidityInHours”

2024 年 10 月25 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema # 14 : NDS Audits]/eventTypeName”响应属性中添加了新的“INDEPENDENT_SHARD_SCALING_CLUSTER_MIGRATED、INDEPENDENT_SHARD_SCALING_CLUSTER_ROLLED_BACK”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema # 14 : NDS Audits]/eventTypeName' 响应属性中添加了新的 'INDEPENDENT_SHARD_SCALING_CLUSTER_MIGRATED、INDEPENDENT_SHARD_SCALING_CLUSTER_ROLLED_BACK'枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在请求属性“dataProcessRegion/ 地区 /”中添加了新的“eastus、eastus 2、westurope、westus”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 向请求属性“地区 /”添加了新的“eastus、eastus 2、westurope、westus”枚举值

2024 年 10 月24 日发布

GET /api/atlas/v2
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/clusters
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/eventTypes
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}/status
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“results/items/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”响应属性中
  • 已将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到请求属性“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”响应属性中
  • 已将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到请求属性“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“results/items/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
  • 将新的 'FTS_INDEXES_SYNONYM_MAPPING_INVALID'枚举值添加到 'results/items/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 4 : FTS Index Audit Types]/' 响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“results/items/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
  • 将新的 'FTS_INDEXES_SYNONYM_MAPPING_INVALID'枚举值添加到 'results/items/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 4 : FTS Index Audit Types]/' 响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
  • 在“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 4 : FTS Index Audit Types]/”响应属性中添加了新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
  • 在“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 4 : FTS Index Audit Types]/”响应属性中添加了新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“results/items/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 3 : FTS Index Audit Types]/”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 针对“results/items/”响应属性，鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/DiskBackupSnapshotAWSExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse”Amazon Web Services
  • 针对“results/items/”响应属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/DiskBackupSnapshotAzureExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAzureExportBucketResponse”Azure
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse' 添加到响应的 'results/items/' 响应属性'oneOf' 列表
  • 已从响应的“results/items/”响应属性“oneOf”列表中删除“#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode, results/items/ _id' 变为必填项
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • Amazon Web Services请求鉴别器中键“ Amazon Web Services ”的映射值从“#/components/schemas/DiskBackupSnapshotAWSExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAWSExportBucketRequest”
  • 请求鉴别器中键“ Azure ”的映射值从Azure '#/components/schemas/DiskBackupSnapshotAzureExportBucket' 更改为 '#/components/schemas/DiskBackupSnapshotAzureExportBucketRequest'
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucketRequest, #/components/schemas/DiskBackupSnapshotAzureExportBucketRequest' 添加到请求正文 'oneOf' 列表
  • 已将键“ Amazon Web ServicesAmazon Web Services ”的映射值从响应状态“”的响应鉴别器的“#/components/schemas/DiskBackupSnapshotAWSExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse”200
  • 已将响应状态“”的响应鉴别器中键“Azure Azure ”的映射值从“#/components/schemas/DiskBackupSnapshotAzureExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAzureExportBucketResponse”200
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse' 添加到响应的响应正文 'oneOf' 列表
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket”
  • 响应属性“_id, BadRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode ” 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 已将键“ Amazon Web ServicesAmazon Web Services ”的映射值从响应状态“”的响应鉴别器的“#/components/schemas/DiskBackupSnapshotAWSExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse”200
  • 已将响应状态“”的响应鉴别器中键“Azure Azure ”的映射值从“#/components/schemas/DiskBackupSnapshotAzureExportBucket”更改为“#/components/schemas/DiskBackupSnapshotAzureExportBucketResponse”200
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse' 添加到响应的响应正文 'oneOf' 列表
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket”
  • 响应属性“_id, BadRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode ” 变为必填项
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将新的“GCP”枚举值添加到“awsIamRoles/items/providerName”响应属性中
  • 将新的“GCP”枚举值添加到“azureServicePrincipals/items/providerName”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“GCP”映射键添加到请求鉴别器
  • 将“#/components/schemas/CloudProviderAccessGCPServiceAccountRequest”添加到请求正文“oneOf”列表中
  • 已将“GCP”映射键添加到响应状态“200”的响应鉴别器
  • 已将新的“GCP”枚举值添加到“providerName”响应属性中
  • 将新的“GCP”枚举值添加到请求属性“/providerName”
  • 已将新的“GCP”枚举值添加到请求属性“providerName”中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{cloudProvider}/{roleId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将新的枚举值“Azure GCPAzure , GCP ”添加到“path”请求参数“cloudProvider”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 已将“GCP”映射键添加到响应状态“200”的响应鉴别器
  • 已将新的“GCP”枚举值添加到“providerName”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“GCP”映射键添加到请求鉴别器
  • 已将“GCP”映射键添加到响应状态“200”的响应鉴别器
  • 已将新的“GCP”枚举值添加到“providerName”响应属性中
  • 已将新的“GCP”枚举值添加到请求属性“providerName”中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 端点已弃用
  • 请求可选属性“mongoDBEmployeeAccessGrant”变为非只读属性
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 请求可选属性“mongoDBEmployeeAccessGrant”变为非只读属性
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 端点已弃用
  • 请求可选属性“mongoDBEmployeeAccessGrant”变为非只读属性
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 从响应中删除了可选属性“results/items/deliveryUrl”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 从响应中删除了可选属性“deliveryUrl”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 对于“path”请求参数“exportId”，maxLength 已设立为“24”
  • 将模式“^([af 0 - 9 ]{24})$”添加到“path”请求参数“exportId”
  • 端点方案安全性“DigestAuth”已从API中删除
  • 从响应中删除了可选属性“deliveryUrl”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{hostName}/logs/{logName}.gz
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“dls:gcp, gcs”鉴别器映射键添加到“/items/ 存储/stores/items/”响应属性
  • 将 '#/components/schemas/DataLakeDLSGCPStore, #/components/schemas/DataLakeGoogleCloudStorageStore' 添加到响应的 '/items/ 存储/stores/items/' 响应属性'oneOf' 列表
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“dls:gcp, gcs”鉴别器映射键添加到“存储/stores/items/”请求属性
  • 将“#/components/schemas/DataLakeDLSGCPStore, #/components/schemas/DataLakeGoogleCloudStorageStore”添加到“存储/stores/items/”请求属性“oneOf”列表
  • 将“dls:gcp, gcs”鉴别器映射键添加到“存储/stores/items/”响应属性
  • 将 '#/components/schemas/DataLakeDLSGCPStore, #/components/schemas/DataLakeGoogleCloudStorageStore' 添加到响应的 ' 存储/stores/items/' 响应属性'oneOf' 列表
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“dls:gcp, gcs”鉴别器映射键添加到“存储/stores/items/”响应属性
  • 将 '#/components/schemas/DataLakeDLSGCPStore, #/components/schemas/DataLakeGoogleCloudStorageStore' 添加到响应的 ' 存储/stores/items/' 响应属性'oneOf' 列表
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“dls:gcp, gcs”鉴别器映射键添加到“存储/stores/items/”请求属性
  • 将“#/components/schemas/DataLakeDLSGCPStore, #/components/schemas/DataLakeGoogleCloudStorageStore”添加到“存储/stores/items/”请求属性“oneOf”列表
  • 将“dls:gcp, gcs”鉴别器映射键添加到“存储/stores/items/”响应属性
  • 将 '#/components/schemas/DataLakeDLSGCPStore, #/components/schemas/DataLakeGoogleCloudStorageStore' 添加到响应的 ' 存储/stores/items/' 响应属性'oneOf' 列表
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/queryLogs.gz
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“results/items/oneOf[subschema # 13 : Host Metric Events]/”响应属性
  • 在“results/items/oneOf[subschema # 14 : NDS Audits]/eventTypeName”响应属性中添加了新的“FEATURE_FLAG_MAINTENANCE、INDEPENDENT_SHARD_AUTO_SCALING_AVAILABLE、KMIP_KEY_ROTATION_SCHEDULED”枚举值
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“results/items/oneOf[subschema # 11 : FTS Index Audits]/eventTypeName”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 将“OPCOUNTER_TTL_DELETED”鉴别器映射键添加到“/oneOf[subschema # 13 : Host Metric Events]/”响应属性
  • 在 '/oneOf[subschema # 14 : NDS Audits]/eventTypeName' 响应属性中添加了新的 'FEATURE_FLAG_MAINTENANCE、INDEPENDENT_SHARD_AUTO_SCALING_AVAILABLE、KMIP_KEY_ROTATION_SCHEDULED'枚举值
  • 将新的“FTS_INDEXES_SYNONYM_MAPPING_INVALID”枚举值添加到“/oneOf[subschema # 11 : FTS Index Audits]/eventTypeName”响应属性中
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/invites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/invites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/invites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/liveMigrations/validate/{validationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}/cutover
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/autoDefer
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/defer
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/managedSlowMs/disable
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/managedSlowMs/enable
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 在响应中添加了可选属性“results/items/azureConnectionName、results/items/azureLinkId、results/items/customerEndpointIPAddress、results/items/errorMessage、results/items/status”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 在响应中添加了可选属性“results/items/azureConnectionName、results/items/azureLinkId、results/items/customerEndpointIPAddress、results/items/errorMessage、results/items/status”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
  • 添加了新的可选请求属性“azureConnectionName、azureLinkId、customerEndpointIPAddress、errorMessage、status”
DELETE /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 在响应中添加了可选属性“azureConnectionName、azureLinkId、customerEndpointIPAddress、errorMessage、status”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/namespaces
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/suggestedIndexes
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams/privateLinkConnections/{connectionId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:accept
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:reject
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:start
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:stop
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/customerX509
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/ldap/userToDNMapping
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify/{requestId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage/{token}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • Added the new 'ATLAS_AWS_STREAM_PROCESSING_PRIVATELINK, ATLAS_AZURE_STREAM_PROCESSING_PRIVATELINK, ATLAS_FLEX_AWS_ 100 _USAGE_HOURS, ATLAS_FLEX_AWS_ 200 _USAGE_HOURS, ATLAS_FLEX_AWS_ 300 _USAGE_HOURS, ATLAS_FLEX_AWS_ 400 _USAGE_HOURS, ATLAS_FLEX_AWS_ 500 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 100 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 200 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 300 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 400 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 500 _USAGE_HOURS, ATLAS_FLEX_GCP_ 100 _USAGE_HOURS, ATLAS_FLEX_GCP_ 200 _USAGE_HOURS, ATLAS_FLEX_GCP_ 300 _USAGE_HOURS, ATLAS_FLEX_GCP_ 400 _USAGE_HOURS, ATLAS_FLEX_GCP_ 500 _USAGE_HOURS' 枚举 values到 'results/items/lineItems/items/sku' 响应属性
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • Added the new 'ATLAS_AWS_STREAM_PROCESSING_PRIVATELINK, ATLAS_AZURE_STREAM_PROCESSING_PRIVATELINK, ATLAS_FLEX_AWS_ 100 _USAGE_HOURS, ATLAS_FLEX_AWS_ 200 _USAGE_HOURS, ATLAS_FLEX_AWS_ 300 _USAGE_HOURS, ATLAS_FLEX_AWS_ 400 _USAGE_HOURS, ATLAS_FLEX_AWS_ 500 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 100 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 200 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 300 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 400 _USAGE_HOURS, ATLAS_FLEX_AZURE_ 500 _USAGE_HOURS, ATLAS_FLEX_GCP_ 100 _USAGE_HOURS, ATLAS_FLEX_GCP_ 200 _USAGE_HOURS, ATLAS_FLEX_GCP_ 300 _USAGE_HOURS, ATLAS_FLEX_GCP_ 400 _USAGE_HOURS, ATLAS_FLEX_GCP_ 500 _USAGE_HOURS' 枚举 values到“lineItems/items/sku”响应属性
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 在响应中添加了可选属性“/items/resourceName”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 在响应中添加了可选属性“securityContact”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 添加了状态为“400”的不成功响应
  • 在响应中添加了可选属性“securityContact”
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
  • 添加了新的可选请求属性“securityContact”
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/teams/byName/{teamName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/unauth/controlPlaneIPAddresses
Updated
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
POST /api/atlas/v2/users
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项
GET /api/atlas/v2/users/{userId}
Updated
  • 端点方案安全性“DigestAuth”已从API中删除
  • 响应属性 'badRequestDetail/fields/items/description, BadRequestDetail/fields/items/ 字段, error, errorCode' 变为必填项

2024 年 10 月15 日发布

POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 添加了可选属性“providerSettings/oneOf[subschema # 4：集群的 Cloud 服务提供商设置]/autoScaling/compute/maxInstanceSize、providerSettings/oneOf[subschema # 4：集群的 Cloud 服务提供商设置]/autoScaling /compute/minInstanceSize' 到响应
  • 添加了新的可选请求属性 'providerSettings/oneOf[subschema # 4：集群的 Cloud 服务提供商设置]/autoScaling/compute/maxInstanceSize、providerSettings/oneOf[subschema # 4：集群的 Cloud 服务提供商设置] /autoScaling/compute/minInstanceSize'

2024 年 10 月03 日发布

GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 已将“subschema # 6 ：日志摄取匹配器字段”添加到“/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 将新的 'HOST_MOGOT_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 响应属性中
  • 从“results/items/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中删除了“<, >”枚举值
  • 从“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/操作符”响应属性中删除了“<, >”枚举值
  • 从“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中删除了“<, >”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在 '/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符' 响应属性中添加了新的 'GREATER_THAN, LESS_THAN'枚举值
  • 在“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 将新的 'HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 响应属性中
  • 删除了“/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
  • 从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符”响应属性中删除了“<, >”枚举值
  • 删除了“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
  • 在请求属性'/ 枚举 [subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符'
  • 向请求属性“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符 ”添加了新的“GREATER_THAN、LESS_THAN”枚举值
  • 在请求属性'/ 枚举 [subschema # 9 : Host Metric Alert Configuration]/metricThreshold/ 操作符'
  • 在请求属性'/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 中添加了新的 'HOST_MONGOT_STOP_REPLICATION'枚举值
  • 删除了请求属性'/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符 ' 的枚举值 '<, >'
  • 删除了请求属性'/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符 ' 的枚举值 '<, >'
  • 删除了请求属性'/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/ 操作符 ' 的枚举值 '<, >'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符' 响应属性中添加了新的 'GREATER_THAN, LESS_THAN'枚举值
  • 在“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 将新的 'HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 响应属性中
  • 删除了“/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
  • 从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符”响应属性中删除了“<, >”枚举值
  • 删除了“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符' 响应属性中添加了新的 'GREATER_THAN, LESS_THAN'枚举值
  • 在“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 将新的 'HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 响应属性中
  • 删除了“/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
  • 从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符”响应属性中删除了“<, >”枚举值
  • 删除了“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符' 响应属性中添加了新的 'GREATER_THAN, LESS_THAN'枚举值
  • 在“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 将新的 'HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 响应属性中
  • 删除了“/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
  • 从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符”响应属性中删除了“<, >”枚举值
  • 删除了“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中的“<, >”枚举值
  • 在请求属性'/ 枚举 [subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符'
  • 向请求属性“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符 ”添加了新的“GREATER_THAN、LESS_THAN”枚举值
  • 在请求属性'/ 枚举 [subschema # 9 : Host Metric Alert Configuration]/metricThreshold/ 操作符'
  • 在请求属性'/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 中添加了新的 'HOST_MONGOT_STOP_REPLICATION'枚举值
  • 删除了请求属性'/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/ 操作符 ' 的枚举值 '<, >'
  • 删除了请求属性'/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符 ' 的枚举值 '<, >'
  • 删除了请求属性'/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/ 操作符 ' 的枚举值 '<, >'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的 'HOST_MOGOT_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema # 3 : Host Alerts]/eventTypeName' 响应属性中
  • 将新的 'HOST_MOGOT_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema # 6 : Stream Processor Alerts]/eventTypeName' 响应属性中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的 'HOST_MOGOT_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema # 3 : Host Alerts]/eventTypeName' 响应属性中
  • 将新的 'HOST_MOGOT_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema # 6 : Stream Processor Alerts]/eventTypeName' 响应属性中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 3 : Host Alerts]/eventTypeName' 响应属性中
  • 已将新的“HOST_MOGOT_STOP_REPLICATION”枚举值添加到“/oneOf[subschema # 6 : Stream Processor Alerts]/eventTypeName”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将新的 'HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 3 : Host Alerts]/eventTypeName' 响应属性中
  • 已将新的“HOST_MOGOT_STOP_REPLICATION”枚举值添加到“/oneOf[subschema # 6 : Stream Processor Alerts]/eventTypeName”响应属性中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在“results/items/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/ 操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 在“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中添加了新的“GREATER_THAN, LESS_THAN”枚举值
  • 将新的 'HOST_MOGOT_STOP_REPLICATION'枚举值添加到 'results/items/oneOf[subschema # 8 : Host Alert Configuration]/eventTypeName' 响应属性中
  • 从“results/items/oneOf[subschema # 13 : Serverless Alert Configuration]/metricThreshold/操作符”响应属性中删除了“<, >”枚举值
  • 从“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold/操作符”响应属性中删除了“<, >”枚举值
  • 从“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold/操作符”响应属性中删除了“<, >”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/redactClientLogData”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“redactClientLogData”
  • 添加了新的可选请求属性“redactClientLogData”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 已添加“diskGBEnabled”请求属性默认值“false”
  • 添加了“enabled”请求属性默认值“false”
  • 已添加“scaleDownEnabled”请求属性默认值“false”
  • 已添加“diskGBEnabled”响应的属性默认值“false”
  • 已添加“enabled”响应的属性默认值“false”
  • 已添加“scaleDownEnabled”响应的属性默认值“false”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“redactClientLogData”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“redactClientLogData”
  • 添加了新的可选请求属性“redactClientLogData”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • “changeStreamOptionsPreAndPostImagesExpireAfterSeconds”响应的属性默认值“- 1.00 ” 已添加
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • “changeStreamOptionsPreAndPostImagesExpireAfterSeconds”请求属性默认值“- 1.00 ” 已添加
  • “changeStreamOptionsPreAndPostImagesExpireAfterSeconds”响应的属性默认值“- 1.00 ” 已添加
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“/items/actions/items/ 动作”响应属性中添加了新的“OUT_TO_AZURE、OUT_TO_GCS”枚举值
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“OUT_TO_AZURE、OUT_TO_GCS”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“OUT_TO_AZURE、OUT_TO_GCS”枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“OUT_TO_AZURE、OUT_TO_GCS”枚举值
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在“actions/items/ 动作”响应属性中添加了新的“OUT_TO_AZURE、OUT_TO_GCS”枚举值
  • 在请求属性“actions/items/ 动作 ”中添加了新的“OUT_TO_AZURE、OUT_TO_GCS”枚举值
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将“#/components/schemas/AtlasDataFederationGCPRegion”添加到响应的“/items/dataProcessRegion/ 地区”响应属性“oneOf”列表
  • 已将新的“GCP”枚举值添加到“/items/dataProcessRegion/cloudProvider”响应属性中
  • 在响应中添加了可选属性“/items/cloudProviderConfig/ GCP ”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将“#/components/schemas/AtlasDataFederationGCPRegion”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/AtlasDataFederationGCPRegion”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将新的“GCP”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 已将新的“GCP”枚举值添加到请求属性“dataProcessRegion/cloudProvider”中
  • 在响应中添加了可选属性“cloudProviderConfig/ GCP ”
  • 添加了新的可选请求属性'cloudProviderConfig/ GCP '
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将“#/components/schemas/AtlasDataFederationGCPRegion”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将新的“GCP”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 在响应中添加了可选属性“cloudProviderConfig/ GCP ”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将“#/components/schemas/AtlasDataFederationGCPRegion”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/AtlasDataFederationGCPRegion”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已将新的“GCP”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 已将新的“GCP”枚举值添加到请求属性“dataProcessRegion/cloudProvider”中
  • 在响应中添加了可选属性“cloudProviderConfig/ GCP ”
  • 添加了新的可选请求属性'cloudProviderConfig/ GCP '
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 在响应中添加了可选属性“results/items/description”
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 在响应中添加了可选属性“description”
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 在响应中添加了可选属性“description”
  • 添加了新的可选请求属性“description”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的 'CLUSTER_FCV_EXPIRATION_DATE_UPDATED'枚举值添加到 'results/items/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 33 : Version Audit Types]/' 响应属性中
  • 在“results/items/oneOf[subschema # 14 : NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_DISABLED、CLUSTER_INSTANCE_ENABLED”枚举值
  • 在“results/items/oneOf[subschema # 12 : Host Events]/eventTypeName”响应属性中添加了新的“HOST_MOGOT_RESUME_REPLICATION”、“HOST_MONGOT_STOP_REPLICATION”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的 'CLUSTER_FCV_EXPIRATION_DATE_UPDATED'枚举值添加到 '/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 33 : Version Audit Types]/' 响应属性中
  • 在“/oneOf[subschema # 14 : NDS Audits]/eventTypeName”响应属性中添加了新的“CLUSTER_INSTANCE_DISABLED、CLUSTER_INSTANCE_ENABLED”枚举值
  • 已将新的 'HOST_MOGOT_RESUME_REPLICATION、HOST_MONGOT_STOP_REPLICATION'枚举值添加到 '/oneOf[subschema # 12 : Host Events]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 添加了 'atlas.项目。部署.salesSoldM 0 s' 鉴别器将键映射到 '/items/' 响应属性
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了新的枚举值“atlas”。项目。部署.salesSoldM 0 s' 到“path”请求参数“limitName”
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了 'atlas.项目。部署.salesSoldM 0 s' 将键映射到响应状态“ 200 ”的响应鉴别器
  • 添加了新的枚举值“atlas”。项目。部署.salesSoldM 0 s' 到“path”请求参数“limitName”
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 添加了 'atlas.项目。部署.salesSoldM 0 s' 将键映射到请求鉴别器
  • 添加了 'atlas.项目。部署.salesSoldM 0 s' 将键映射到响应状态“ 200 ”的响应鉴别器
  • 添加了新的枚举值“atlas”。项目。部署.salesSoldM 0 s' 到“path”请求参数“limitName”
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • “hostnameSchemaType”请求属性默认值“PUBLIC”已删除
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • “hostnameSchemaType”请求属性默认值“PUBLIC”已删除
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已删除状态为“ 204 ”的成功响应
  • 添加了状态为“ 202 ”的成功响应
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/networking/ 访问权限/connectionId”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/connectionId”
  • 添加了新的可选请求属性“connections/items/networking/ 访问权限/connectionId”
GET /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:accept
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/vpcPeeringConnections/{id}:reject
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/connectionId”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/connectionId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/networking/ 访问权限/connectionId”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/networking/ 访问权限/connectionId”
  • 添加了新的可选请求属性“/networking/ 访问权限/connectionId”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking/ 访问权限/connectionId”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking/ 访问权限/connectionId”
  • 添加了新的可选请求属性“/networking/ 访问权限/connectionId”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 在响应中添加了可选属性“connections/items/networking/ 访问权限/connectionId”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_USS_AWS_ 100 _USAGE_HOURS, ATLAS_USS_AWS_ 200 _USAGE_HOURS, ATLAS_USS_AWS_ 300 _USAGE_HOURS, ATLAS_USS_AWS_ 400 _USAGE_HOURS, ATLAS_USS_AWS_ 500 _USAGE_HOURS, ATLAS_USS_AZURE_ 100 _USAGE_HOURS, ATLAS_USS_AZURE_ 200 _USAGE_HOURS, ATLAS_USS_AZURE_ 300 _USAGE_HOURS, ATLAS_USS_AZURE_ 400 _USAGE_HOURS, ATLAS_USS_AZURE_ 500 _USAGE_HOURS, ATLAS_USS_GCP_ 100 _USAGE_HOURS, ATLAS_USS_GCP_ 200 _USAGE_HOURS, ATLAS_USS_GCP_ 300 _USAGE_HOURS, ATLAS_USS_GCP_ 400 _USAGE_HOURS, ATLAS_USS_GCP_ 500 _USAGE_HOURS' 枚举 values to the 'results /items/lineItems/items/sku' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_USS_AWS_ 100 _USAGE_HOURS, ATLAS_USS_AWS_ 200 _USAGE_HOURS, ATLAS_USS_AWS_ 300 _USAGE_HOURS, ATLAS_USS_AWS_ 400 _USAGE_HOURS, ATLAS_USS_AWS_ 500 _USAGE_HOURS, ATLAS_USS_AZURE_ 100 _USAGE_HOURS, ATLAS_USS_AZURE_ 200 _USAGE_HOURS, ATLAS_USS_AZURE_ 300 _USAGE_HOURS, ATLAS_USS_AZURE_ 400 _USAGE_HOURS, ATLAS_USS_AZURE_ 500 _USAGE_HOURS, ATLAS_USS_GCP_ 100 _USAGE_HOURS, ATLAS_USS_GCP_ 200 _USAGE_HOURS, ATLAS_USS_GCP_ 300 _USAGE_HOURS, ATLAS_USS_GCP_ 400 _USAGE_HOURS, ATLAS_USS_GCP_ 500 _USAGE_HOURS' 枚举 values to the 'lineItems /items/sku' 响应属性
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 添加了新的可选“查询”请求参数“pretty”

2024 年 10 月01 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“defaultMaxTimeMS”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“defaultMaxTimeMS”
  • 添加了新的可选请求属性“defaultMaxTimeMS”

2024 年 9 月 30 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/configServerManagementMode、results/items/configServerType”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“configServerManagementMode、configServerType”
  • 添加了新的可选请求属性“configServerManagementMode”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在响应中添加了可选属性“configServerManagementMode、configServerType”
  • 添加了新的可选请求属性“configServerManagementMode”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“configServerManagementMode、configServerType”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“configServerManagementMode、configServerType”
  • 添加了新的可选请求属性“configServerManagementMode”

2024 年 9 月 24 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到响应的“results/items/dataProcessRegion/ 地区”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到“地区”请求属性“oneOf”列表
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
Updated
  • 将“#/components/schemas/ApiStreamsAzureRegionView”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中

2024 年 9 月 23 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“QUEUED_ADMIN_ACTION_CANCELLED”枚举值添加到“results/items/oneOf[subschema # 14 : NDS Audits]/eventTypeName”响应属性中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将新的“QUEUED_ADMIN_ACTION_CANCELLED”枚举值添加到“/oneOf[subschema # 14 : NDS Audits]/eventTypeName”响应属性中

2024 年 9 月 20 日发布

GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
Updated
  • 添加了API标签“资源策略”
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 添加了API标签“资源策略”
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
Updated
  • 添加了API标签“资源策略”
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了API标签“资源策略”
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了API标签“资源策略”
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
Updated
  • 添加了API标签“资源策略”
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
Updated
  • 添加了API标签“资源策略”

2024 年 9 月 19 日发布

POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 请求可选属性“destinationOrgId”变为非只读属性
  • 请求可选属性“destinationOrgPrivateApiKey”变为非只读属性
  • 请求可选属性“destinationOrgPublicApiKey”变为非只读属性

2024 年 9 月 16 日发布

POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 已将新的“PRIVATE_LINK”枚举值添加到请求属性“connections/items/networking/ 访问权限/type”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 已将新的“PRIVATE_LINK”枚举值添加到请求属性“/networking/ 访问权限/type”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将新的“PRIVATE_LINK”枚举值添加到请求属性“/networking/ 访问权限/type”

2024 年 9 月 12 日发布

GET /api/atlas/v2
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/clusters
Updated
  • “results/items/clusters/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]* 更改为$' 为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/eventTypes
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/metadata.xml
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/accessList
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/accessList/{entryValue}/status
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • “results/items/oneOf[subschema # 2 : Cluster Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA -Z 0 - 9 ]+$'
  • “results/items/oneOf[subschema # 3 : Host Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA -Z 0 - 9 ]+$'
  • “results/items/oneOf[subschema # 4 : Host Metric Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a- zA-Z 0 - 9 ]+$'
  • “results/items/oneOf[subschema # 5 : ReplicaSet Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA -Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • “results/items/oneOf[subschema # 2 : Cluster Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA -Z 0 - 9 ]+$'
  • “results/items/oneOf[subschema # 3 : Host Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA -Z 0 - 9 ]+$'
  • “results/items/oneOf[subschema # 4 : Host Metric Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a- zA-Z 0 - 9 ]+$'
  • “results/items/oneOf[subschema # 5 : ReplicaSet Alerts]/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 转换为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA -Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • '/oneOf[subschema # 2 : Cluster Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • '/oneOf[subschema # 3 : Host Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • '/oneOf[subschema # 4 : Host Metric Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • '/oneOf[subschema # 5 : ReplicaSet Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • '/oneOf[subschema # 2 : Cluster Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • '/oneOf[subschema # 3 : Host Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • '/oneOf[subschema # 4 : Host Metric Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • '/oneOf[subschema # 5 : ReplicaSet Alerts]/clusterName' 响应的属性模式已从 '^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$' 改为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/auditLog
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/awsCustomDNS
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 请求鉴别器中键“ Amazon Web Services ”的映射值从“#/components/schemas/CloudProviderAccessAWSIAMRole”更改为“#/components/schemas/CloudProviderAccessAWSIAMRoleRequest”
  • 请求鉴别器中键“ Azure ”的映射值从 '#/components/schemas/CloudProviderAccessAzureServicePrincipal' 更改为 '#/components/schemas/CloudProviderAccessAzureServicePrincipalRequest'
  • 将 '#/components/schemas/CloudProviderAccessAWSIAMRoleRequest, #/components/schemas/CloudProviderAccessAzureServicePrincipalRequest' 添加到请求正文 'oneOf' 列表
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{cloudProvider}/{roleId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 请求鉴别器中键“ Amazon Web Services ”的映射值从“#/components/schemas/CloudProviderAccessAWSIAMRole”更改为“#/components/schemas/CloudProviderAccessAWSIAMRoleRequestUpdate”
  • 请求鉴别器中键“ Azure ”的映射值从“#/components/schemas/CloudProviderAccessAzureServicePrincipal”更改为“#/components/schemas/CloudProviderAccessAzureServicePrincipalRequestUpdate”
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • “results/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail、results/items/mongoDBEmployeeAccessGrant”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将请求属性“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail, mongoDBEmployeeAccessGrant”
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 将请求属性“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail, mongoDBEmployeeAccessGrant”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 将请求属性“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail, mongoDBEmployeeAccessGrant”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail, mongoDBEmployeeAccessGrant”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “results/items/targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性 'badRequestDetail,Results/items/components/items/privateDownloadDeliveryUrls,results/items/privateDownloadDeliveryUrls'
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“targetClusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail、components/items/privateDownloadDeliveryUrls、privateDownloadDeliveryUrls”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail、components/items/privateDownloadDeliveryUrls、privateDownloadDeliveryUrls”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/download
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restore
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “results/items/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/restores/{restoreId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/tenant/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backupCheckpoints/{checkpointId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “results/items/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/queryLogs.gz
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/outageSimulation
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “results/items/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • “results/items/delivery/targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为to '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ] +$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“clusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 将请求属性“delivery/targetClusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^” ([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “results/items/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • “results/items/delivery/targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为to '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ] +$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “delivery/targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^( [a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshotSchedule
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/status
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:grantMongoDBEmployeeAccess
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:pinFeatureCompatibilityVersion
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:revokeMongoDBEmployeeAccess
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}:unpinFeatureCompatibilityVersion
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{hostName}/logs/{logName}.gz
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/limits/{limitName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}/queryLogs.gz
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • “results/items/scopes/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]* 更改为$' 为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 已将请求属性“scopes/items/name”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为'^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+ $'
  • “scopes/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • “scopes/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 已将请求属性“scopes/items/name”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为'^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+ $'
  • “scopes/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/clusters/{clusterName}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/dbAccessHistory/processes/{hostname}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • Added the new 'CLOUD_PROVIDER_ACCESS_GCP_SERVICE_ACCOUNT_ADDED, CLOUD_PROVIDER_ACCESS_GCP_SERVICE_ACCOUNT_DELETED, CLOUD_PROVIDER_ACCESS_GCP_SERVICE_ACCOUNT_UPDATED, EMPLOYEE_ACCESS_GRANTED, EMPLOYEE_ACCESS_REVOKED, QUEUED_ADMIN_ACTION_COMPLETED' 枚举 values to the 'results/items/oneOf[subschema # 14 : NDS Audits]/eventTypeName' response 属性
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • Added the new 'CLOUD_PROVIDER_ACCESS_GCP_SERVICE_ACCOUNT_ADDED, CLOUD_PROVIDER_ACCESS_GCP_SERVICE_ACCOUNT_DELETED, CLOUD_PROVIDER_ACCESS_GCP_SERVICE_ACCOUNT_UPDATED, EMPLOYEE_ACCESS_GRANTED, EMPLOYEE_ACCESS_REVOKED, QUEUED_ADMIN_ACTION_COMPLETED' 枚举 values to the '/oneOf[subschema # 14 : NDS Audits]/eventTypeName' response 属性
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/invites
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/invites
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/invites
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/invites/{invitationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/limits
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/limits/{limitName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/liveMigrations/validate/{validationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/groups/{groupId}/liveMigrations/{liveMigrationId}/cutover
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/autoDefer
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/maintenanceWindow/defer
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/managedSlowMs/disable
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/managedSlowMs/enable
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/peers
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/peers
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/peers/{peerId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/pipelines
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/pause
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/resume
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/endpointService
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/regionalMode
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 已将“path”请求参数“instanceName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint
Updated
  • 已将“path”请求参数“instanceName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 已将“path”请求参数“instanceName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 已将“path”请求参数“instanceName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/privateEndpoint/serverless/instance/{instanceName}/endpoint/{endpointId}
Updated
  • 已将“path”请求参数“instanceName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateEndpoint/{cloudProvider}/endpointService/{endpointServiceId}/endpoint/{endpointId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/privateIpMode
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/privateNetworkSettings/endpointIds/{endpointId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/namespaces
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/slowQueryLogs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/performanceAdvisor/suggestedIndexes
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{name}
Updated
  • 已将“路径”请求参数“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/sampleDatasetLoad/{sampleDatasetId}
Updated
  • “clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • “results/items/name”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 将请求属性“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “results/items/targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 将请求属性“targetClusterName”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([ a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • “targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “targetClusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “results/items/serverlessInstanceName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • “serverlessInstanceName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
Updated
  • Changed the pattern of the 'path' request parameter 'clusterName' from '^[a-zA-Z0-9][a-zA-Z0-9-]*$' to '^([a-zA-Z0-9][a-zA-Z0-9-]*)?[a-zA-Z0-9]+$'
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已将“路径”请求参数“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已将“路径”请求参数“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 已将“路径”请求参数“名称”的模式从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • “名称”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“^([a -zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/settings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“badRequestDetail、results/items/sampleConnections”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 向响应添加了可选属性“badRequestDetail、sampleConnections”
  • 添加了新的可选请求属性“sampleConnections”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 向响应添加了可选属性“badRequestDetail、sampleConnections”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 向响应添加了可选属性“badRequestDetail、sampleConnections”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:start
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:stop
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/streams:withSampleConnections
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/teams
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/teams
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/teams/{teamId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/groups/{groupId}/userSecurity
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/customerX509
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/userSecurity/ldap/userToDNMapping
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/userSecurity/ldap/verify/{requestId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/groups/{groupId}/users/{userId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/groups/{groupId}:migrate
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/orgs/{orgId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList/{ipAddress}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage/{token}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将“#/components/schemas/AtlasResourcePolicyAuditForOrg”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将“#/components/schemas/AtlasResourcePolicyAuditForOrg”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/federationSettings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • “results/items/lineItems/items/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]* $' 为 '^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$'
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • “lineItems/items/clusterName”响应的属性模式已从“^[a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*$”更改为“ ^([a-zA-Z 0 - 9 ][a-zA-Z 0 - 9 -]*)?[a-zA-Z 0 - 9 ]+$ '
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/liveMigrations/availableProjects
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/liveMigrations/linkTokens
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/nonCompliantResources
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies
已交
  • 已添加端点
DELETE /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
已交
  • 已添加端点
PATCH /api/atlas/v2/orgs/{orgId}/resourcePolicies/{resourcePolicyId}
已交
  • 已添加端点
POST /api/atlas/v2/orgs/{orgId}/resourcePolicies:validate
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/orgs/{orgId}/settings
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/teams
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/teams/byName/{teamName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users/{userId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 在响应中添加了可选属性“badRequestDetail”
DELETE /api/atlas/v2/orgs/{orgId}/users/{userId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
PUT /api/atlas/v2/orgs/{orgId}/users/{userId}/roles
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/unauth/controlPlaneIPAddresses
Updated
  • 在响应中添加了可选属性“badRequestDetail”
POST /api/atlas/v2/users
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 在响应中添加了可选属性“badRequestDetail”
GET /api/atlas/v2/users/{userId}
Updated
  • 在响应中添加了可选属性“badRequestDetail”

2024 年 9 月 03 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“changeStreamOptionsPreAndPostImagesExpireAfterSeconds”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“changeStreamOptionsPreAndPostImagesExpireAfterSeconds”
  • 添加了新的可选请求属性“changeStreamOptionsPreAndPostImagesExpireAfterSeconds”

2024 年 8 月 30 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/featureCompatibilityVersion、results/items/featureCompatibilityVersionExpirationDate”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“featureCompatibilityVersion、featureCompatibilityVersionExpirationDate”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在响应中添加了可选属性“featureCompatibilityVersion、featureCompatibilityVersionExpirationDate”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“featureCompatibilityVersion、featureCompatibilityVersionExpirationDate”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“featureCompatibilityVersion、featureCompatibilityVersionExpirationDate”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 33 : Version Audit Types]/”响应属性中添加了新的“CLUSTER_BINARY_VERSION_UPGRADED”、“CLUSTER_BINARY_VERSION_UPGRADED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 33 : Version Audit Types]/”响应属性中添加了新的“CLUSTER_BINARY_VERSION_UPGRADED”、“CLUSTER_BINARY_VERSION_UPGRADED”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
Updated
  • 在响应中添加了可选属性“options”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
Updated
  • 在响应中添加了可选属性“results/items/options”

2024 年 8 月 29 日发布

GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest/{cloudProvider}/privateEndpoints/{endpointId}
已交
  • 已添加端点

2024 年 8 月 28 日发布

GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems:search
已交
  • 已添加端点

2024 年 8 月 26 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在 'results/items/dataProcessRegion/ 地区/' 响应属性中添加了新的 'DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN'枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
  • 在请求属性“dataProcessRegion/ 地区 /”中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
  • 已将新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值添加到请求属性“地区/”

2024 年 8 月 24 日发布

GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在 'results/items/dataProcessRegion/ 地区/' 响应属性中添加了新的 'DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN'枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
  • 在请求属性“dataProcessRegion/ 地区 /”中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在“dataProcessRegion/ 地区/”响应属性中添加了新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值
  • 已将新的“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MONTREAL_CAN、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS、TOKYO_JPN”枚举值添加到请求属性“地区/”

2024 年 8 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“OPERATION_THROTTLING_REJECTED_OPERATIONS, OPERATIONS_QUERIES_KILLED”鉴别器映射键添加到“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“OPERATION_THROTTLING_REJECTED_OPERATIONS, OPERATIONS_QUERIES_KILLED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“OPERATION_THROTTLING_REJECTED_OPERATIONS, OPERATIONS_QUERIES_KILLED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“OPERATION_THROTTLING_REJECTED_OPERATIONS, OPERATIONS_QUERIES_KILLED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”请求属性
  • 将“OPERATION_THROTTLING_REJECTED_OPERATIONS, OPERATIONS_QUERIES_KILLED”鉴别器映射键添加到“/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“results/items/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“results/items/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“/oneOf[subschema # 4 : Host Metric Alerts]/”响应属性
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“OPERATION_THROTTLING_REJECTED_OPERATIONS, OPERATIONS_QUERIES_KILLED”鉴别器映射键添加到“results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold”响应属性
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 在响应中添加了可选属性“azureServicePrincipals”
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 已从请求正文“oneOf”列表中删除“#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal”
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal”
GET /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal”
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 已从请求正文“oneOf”列表中删除“#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal”
  • 已从响应的响应正文“oneOf”列表中删除“#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal”
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了可选属性 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs /diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/readOnlySpecs/diskIOPS,Results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure ]/analyticsSpecs/diskIOPS,results/items /replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范fications]/readOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskIOPS, Results/items/replicationSpecs/items/regionConfigs/items/oneOf [subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/diskIOPS,Results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema#3: GCP Regional ReplicationSpecifications]/readOnlySpecs/diskIOPS,results/items /replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskIOPS' 到响应
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskIOPS 、 replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskIOPS、 replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs /diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 : GCP区域复制规范]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/readOnlySpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/diskIOPS' 到响应
  • 添加了新的可选请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS、replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskIOPS、replicationSpecs/items /regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs /diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范] /electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[su bschema #3： GCP区域复制规范]/analyticsSpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskIOPS'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskIOPS 、 replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskIOPS、 replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs /diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 : GCP区域复制规范]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/readOnlySpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/diskIOPS' 到响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskIOPS 、 replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskIOPS、 replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs /diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 : GCP区域复制规范]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/readOnlySpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/diskIOPS' 到响应
  • 添加了新的可选请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS、replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskIOPS、replicationSpecs/items /regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs /diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范] /electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[su bschema #3： GCP区域复制规范]/analyticsSpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/diskIOPS，replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskIOPS'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 将“GCP”鉴别器映射键添加到“results/items/dataProcessRegion”响应属性
  • 将新的“GCP”枚举值添加到“results/items/dataProcessRegion/cloudProvider”响应属性中
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 将“GCP”鉴别器映射键添加到“dataProcessRegion”请求属性
  • 将“GCP”鉴别器映射键添加到“dataProcessRegion”响应属性
  • 已将新的“GCP”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 将“GCP”鉴别器映射键添加到“dataProcessRegion”响应属性
  • 已将新的“GCP”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 将“GCP”鉴别器映射键添加到“dataProcessRegion”请求属性
  • 将“GCP”鉴别器映射键添加到“dataProcessRegion”响应属性
  • 已将新的“GCP”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 已将新的“GCP”枚举值添加到请求属性“dataProcessRegion/cloudProvider”中
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“results/items/oneOf[subschema # 13 : Host Metric Events]/”响应属性
  • 将“#/components/schemas/SearchDeploymentAuditView”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 将“subschema # 24 ：搜索部署审核类型”添加到“results/items/oneOf[subschema # 1 ：任何其他事件]/eventTypeName”响应属性“oneOf”列表中
  • 将新的 'CLUSTER_IMPORT_COMPLETED'枚举值添加到 'results/items/oneOf[subschema # 14 : NDS Audits]/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“#/components/schemas/SearchDeploymentAuditView”添加到响应的响应正文“oneOf”列表中
  • 将“OPERATIONS_QUERIES_KILLED、OPERATION_THROTTLING_REJECTED_OPERATIONS”鉴别器映射键添加到“/oneOf[subschema # 13 : Host Metric Events]/”响应属性
  • 将“subschema # 24 ：搜索部署审核类型”添加到“/oneOf[subschema # 1 ：任何其他事件]/eventTypeName”响应属性“oneOf”列表中
  • 将新的 'CLUSTER_IMPORT_COMPLETED'枚举值添加到 '/oneOf[subschema # 14 : NDS Audits]/eventTypeName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/lineItems/:search
已交
  • 已添加端点

2024 年 8 月 20 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/replicaSetScalingStrategy”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“replicaSetScalingStrategy”
  • 添加了新的可选请求属性“replicaSetScalingStrategy”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在响应中添加了可选属性“replicaSetScalingStrategy”
  • 添加了新的可选请求属性“replicaSetScalingStrategy”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“replicaSetScalingStrategy”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“replicaSetScalingStrategy”
  • 添加了新的可选请求属性“replicaSetScalingStrategy”

2024 年 8 月 08 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
已交
  • 针对“results/items/replicationSpecs/items/regionConfigs/items/”响应，鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/AWSRegionConfig”更改为“#/components/schemas/AWSRegionConfig20240805”属性
  • 针对“results/items/replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/AzureRegionConfig”更改为“#/components/schemas/AzureRegionConfig20240805”
  • 已将“results/items/replicationSpecs/items/regionConfigs/items/”响应属性的鉴别器键“ GCP ”的映射值从“#/components/schemas/GCPRegionConfig”更改为“#/components/schemas/GCPRegionConfig 20240805 ”
  • 针对“results/items/replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“TENANT”的映射值从“#/components/schemas/TenantRegionConfig”更改为“#/components/schemas/TenantRegionConfig 20240805 ”
  • 将“#/components/schemas/AWSHardwareSpec 20240805 、#/components/schemas/AzureHardwareSpec 20240805 、#/components/schemas/GCPHardwareSpec 20240805 、#/components/schemas/TenantHardwareSpec 20240805 ”添加到“结果” /items/replicationSpecs/items/regionConfigs/items/electableSpecs' 响应的响应属性'oneOf' 列表
  • 20240805 20240805 20240805 20240805 /items/replicationSpecs/items/regionConfigs/items/' 响应的响应属性'oneOf' 列表
  • 从“results/items/replicationSpecs/items/regionConfigs/items/electableSpecs”中删除了“#/components/schemas/AWSHardwareSpec、#/components/schemas/AzureHardwareSpec、#/components/schemas/GCPHardwareSpec、#/components/schemas/TenantHardwareSpec” ' 响应的响应属性'oneOf' 列表
  • 已从“results/items/replicationSpecs/items/regionConfigs/items/”中删除“#/components/schemas/AWSRegionConfig, #/components/schemas/AzureRegionConfig, #/components/schemas/GCPRegionConfig, #/components/schemas/TenantRegionConfig”响应的响应属性“oneOf”列表
  • 在响应中添加了可选属性 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, results/items/replicationSpecs/items/zoneId'
  • 从响应中删除了可选属性“results/items/diskSizeGB、results/items/replicationSpecs/items/numShards”
POST /api/atlas/v2/groups/{groupId}/clusters
已交
  • 从“replicationSpecs/items/regionConfigs/items/electableSpecs”请求属性中删除了“#/components/schemas/AWSHardwareSpec、#/components/schemas/AzureHardwareSpec、#/components/schemas/GCPHardwareSpec、#/components/schemas/TenantHardwareSpec” oneOf' 列表
  • 从“replicationSpecs/items/regionConfigs/items/”请求属性“oneOf”中删除了“#/components/schemas/AWSRegionConfig, #/components/schemas/AzureRegionConfig, #/components/schemas/GCPRegionConfig, #/components/schemas/TenantRegionConfig” ' list
  • 针对“replicationSpecs/items/regionConfigs/items/”，鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/ 属性 ”更改为“#/components/schemas/ 请求 20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”请求属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/AzureRegionConfig”更改为“#/components/schemas/AzureRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”请求属性，鉴别器键“ GCP ”的映射值从“#/components/schemas/GCPRegionConfig”更改为“#/components/schemas/GCPRegionConfig 20240805 ”
  • 针对“replicationSpecs/items/regionConfigs/items/”请求属性，鉴别器键“TENANT”的映射值从“#/components/schemas/TenantRegionConfig”更改为“#/components/schemas/TenantRegionConfig 20240805 ”
  • 将 '#/components/schemas/AWSHardwareSpec 20240805 、 #/components/schemas/AzureHardwareSpec 20240805 、 #/components/schemas/GCPHardwareSpec 20240805 、 #/components/schemas/TenantHardwareSpec 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/electableSpecs'请求属性'oneOf' 列表
  • 将 '#/components/schemas/AWSRegionConfig 20240805 、 #/components/schemas/AzureRegionConfig 20240805 、 #/components/schemas/GCPRegionConfig 20240805 、 #/components/schemas/TenantRegionConfig 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/'请求属性'oneOf' 列表
  • 已将“replicationSpecs/items/regionConfigs/items/”响应属性的鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/AWSRegionConfig”更改为“#/components/schemas/AWSRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/AzureRegionConfig”更改为“#/components/schemas/AzureRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ GCP ”的映射值从“#/components/schemas/GCPRegionConfig”更改为“#/components/schemas/GCPRegionConfig 20240805 ”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“TENANT”的映射值从“#/components/schemas/TenantRegionConfig”更改为“#/components/schemas/TenantRegionConfig 20240805 ”
  • 将 '#/components/schemas/AWSHardwareSpec 20240805 、 #/components/schemas/AzureHardwareSpec 20240805 、 #/components/schemas/GCPHardwareSpec 20240805 、 #/components/schemas/TenantHardwareSpec 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/electableSpecs' 响应的响应属性'oneOf' 列表
  • 将 '#/components/schemas/AWSRegionConfig 20240805 、 #/components/schemas/AzureRegionConfig 20240805 、 #/components/schemas/GCPRegionConfig 20240805 、 #/components/schemas/TenantRegionConfig 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/' 响应的响应属性'oneOf' 列表
  • 从“replicationSpecs/items/regionConfigs/items/electableSpecs”响应属性中删除了“#/components/schemas/AWSHardwareSpec、#/components/schemas/AzureHardwareSpec、#/components/schemas/GCPHardwareSpec、#/components/schemas/TenantHardwareSpec” oneOf' 响应列表
  • 从“replicationSpecs/items/regionConfigs/items/”响应属性“oneOf”中删除了“#/components/schemas/AWSRegionConfig, #/components/schemas/AzureRegionConfig, #/components/schemas/GCPRegionConfig, #/components/schemas/TenantRegionConfig” ' 响应列表
  • 在响应中添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, replicationSpecs/items/zoneId'
  • 从响应中删除了可选属性“diskSizeGB、replicationSpecs/items/numShards”
  • 删除了请求属性“diskSizeGB, replicationSpecs/items/numShards”
  • 添加了新的可选请求属性'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 已将“replicationSpecs/items/regionConfigs/items/”响应属性的鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/AWSRegionConfig”更改为“#/components/schemas/AWSRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/AzureRegionConfig”更改为“#/components/schemas/AzureRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ GCP ”的映射值从“#/components/schemas/GCPRegionConfig”更改为“#/components/schemas/GCPRegionConfig 20240805 ”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“TENANT”的映射值从“#/components/schemas/TenantRegionConfig”更改为“#/components/schemas/TenantRegionConfig 20240805 ”
  • 将 '#/components/schemas/AWSHardwareSpec 20240805 、 #/components/schemas/AzureHardwareSpec 20240805 、 #/components/schemas/GCPHardwareSpec 20240805 、 #/components/schemas/TenantHardwareSpec 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/electableSpecs' 响应的响应属性'oneOf' 列表
  • 将 '#/components/schemas/AWSRegionConfig 20240805 、 #/components/schemas/AzureRegionConfig 20240805 、 #/components/schemas/GCPRegionConfig 20240805 、 #/components/schemas/TenantRegionConfig 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/' 响应的响应属性'oneOf' 列表
  • 从“replicationSpecs/items/regionConfigs/items/electableSpecs”响应属性中删除了“#/components/schemas/AWSHardwareSpec、#/components/schemas/AzureHardwareSpec、#/components/schemas/GCPHardwareSpec、#/components/schemas/TenantHardwareSpec” oneOf' 响应列表
  • 从“replicationSpecs/items/regionConfigs/items/”响应属性“oneOf”中删除了“#/components/schemas/AWSRegionConfig, #/components/schemas/AzureRegionConfig, #/components/schemas/GCPRegionConfig, #/components/schemas/TenantRegionConfig” ' 响应列表
  • 在响应中添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, replicationSpecs/items/zoneId'
  • 从响应中删除了可选属性“diskSizeGB、replicationSpecs/items/numShards”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 从“replicationSpecs/items/regionConfigs/items/electableSpecs”请求属性中删除了“#/components/schemas/AWSHardwareSpec、#/components/schemas/AzureHardwareSpec、#/components/schemas/GCPHardwareSpec、#/components/schemas/TenantHardwareSpec” oneOf' 列表
  • 从“replicationSpecs/items/regionConfigs/items/”请求属性“oneOf”中删除了“#/components/schemas/AWSRegionConfig, #/components/schemas/AzureRegionConfig, #/components/schemas/GCPRegionConfig, #/components/schemas/TenantRegionConfig” ' list
  • 针对“replicationSpecs/items/regionConfigs/items/”，鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/ 属性 ”更改为“#/components/schemas/ 请求 20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”请求属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/AzureRegionConfig”更改为“#/components/schemas/AzureRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”请求属性，鉴别器键“ GCP ”的映射值从“#/components/schemas/GCPRegionConfig”更改为“#/components/schemas/GCPRegionConfig 20240805 ”
  • 针对“replicationSpecs/items/regionConfigs/items/”请求属性，鉴别器键“TENANT”的映射值从“#/components/schemas/TenantRegionConfig”更改为“#/components/schemas/TenantRegionConfig 20240805 ”
  • 将 '#/components/schemas/AWSHardwareSpec 20240805 、 #/components/schemas/AzureHardwareSpec 20240805 、 #/components/schemas/GCPHardwareSpec 20240805 、 #/components/schemas/TenantHardwareSpec 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/electableSpecs'请求属性'oneOf' 列表
  • 将 '#/components/schemas/AWSRegionConfig 20240805 、 #/components/schemas/AzureRegionConfig 20240805 、 #/components/schemas/GCPRegionConfig 20240805 、 #/components/schemas/TenantRegionConfig 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/'请求属性'oneOf' 列表
  • 已将“replicationSpecs/items/regionConfigs/items/”响应属性的鉴别器键“ Amazon Web Services ”的映射值从“#/components/schemas/AWSRegionConfig”更改为“#/components/schemas/AWSRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ Azure ”的映射值从“#/components/schemas/AzureRegionConfig”更改为“#/components/schemas/AzureRegionConfig20240805”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“ GCP ”的映射值从“#/components/schemas/GCPRegionConfig”更改为“#/components/schemas/GCPRegionConfig 20240805 ”
  • 针对“replicationSpecs/items/regionConfigs/items/”响应属性，鉴别器键“TENANT”的映射值从“#/components/schemas/TenantRegionConfig”更改为“#/components/schemas/TenantRegionConfig 20240805 ”
  • 将 '#/components/schemas/AWSHardwareSpec 20240805 、 #/components/schemas/AzureHardwareSpec 20240805 、 #/components/schemas/GCPHardwareSpec 20240805 、 #/components/schemas/TenantHardwareSpec 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/electableSpecs' 响应的响应属性'oneOf' 列表
  • 将 '#/components/schemas/AWSRegionConfig 20240805 、 #/components/schemas/AzureRegionConfig 20240805 、 #/components/schemas/GCPRegionConfig 20240805 、 #/components/schemas/TenantRegionConfig 20240805 ' 添加到 'replicationSpecs /items/regionConfigs/items/' 响应的响应属性'oneOf' 列表
  • 从“replicationSpecs/items/regionConfigs/items/electableSpecs”响应属性中删除了“#/components/schemas/AWSHardwareSpec、#/components/schemas/AzureHardwareSpec、#/components/schemas/GCPHardwareSpec、#/components/schemas/TenantHardwareSpec” oneOf' 响应列表
  • 从“replicationSpecs/items/regionConfigs/items/”响应属性“oneOf”中删除了“#/components/schemas/AWSRegionConfig, #/components/schemas/AzureRegionConfig, #/components/schemas/GCPRegionConfig, #/components/schemas/TenantRegionConfig” ' 响应列表
  • 在响应中添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, replicationSpecs/items/zoneId'
  • 从响应中删除了可选属性“diskSizeGB、replicationSpecs/items/numShards”
  • 删除了请求属性“diskSizeGB, replicationSpecs/items/numShards”
  • 添加了新的可选请求属性'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB'
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
已交
  • 从响应中删除了可选的只写属性“deleteCopiedBackups/items/replicationSpecId”
  • 在响应中添加了必需的属性“copySettings/items/zoneId”
  • 从响应中删除了可选属性“copySettings/items/replicationSpecId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
已交
  • 从响应中删除了可选的只写属性“deleteCopiedBackups/items/replicationSpecId”
  • 在响应中添加了必需的属性“copySettings/items/zoneId”
  • 从响应中删除了可选属性“copySettings/items/replicationSpecId”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
已交
  • 从响应中删除了可选的只写属性“deleteCopiedBackups/items/replicationSpecId”
  • 在响应中添加了必需的属性“copySettings/items/zoneId”
  • 从响应中删除了可选属性“copySettings/items/replicationSpecId”
  • 添加了新的必需请求属性“copySettings/items/zoneId”
  • 删除了请求属性“copySettings/items/replicationSpecId, deleteCopiedBackups/items/replicationSpecId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
已交
  • 从响应中删除了可选属性“defaultReadConcern、failIndexKeyTooLong”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
已交
  • 从响应中删除了可选属性“defaultReadConcern、failIndexKeyTooLong”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
已交
  • 在响应中添加了可选属性“options”
  • 添加了新的可选请求属性“options”

2024 年 8 月 07 日发布

POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 已将新的“OIDC, SAML”枚举值添加到请求属性“/oneOf[subschema # 1 : OIDC WORKFORCE]/ 协议”
  • 在请求属性'/oneOf[subschema # 2 : OIDC WORKLOAD]/ 协议 ' 中添加了新的 'OIDC, SAML'枚举值
  • 已将新的“OIDC、SAML”枚举值添加到请求属性“协议”中
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 在请求属性'/oneOf[subschema # 1 : SAML]/ 协议 ' 中添加了新的 'OIDC, SAML'枚举值
  • 已将新的“OIDC, SAML”枚举值添加到请求属性“/oneOf[subschema # 2 : OIDC WORKFORCE]/ 协议”
  • 在请求属性'/oneOf[subschema # 3 : OIDC WORKLOAD]/ 协议 ' 中添加了新的 'OIDC, SAML'枚举值
  • 已将新的“OIDC、SAML”枚举值添加到请求属性“协议”中
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 添加了状态为“204”的成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 请求可选属性“customShardKey”变为只读
  • 请求可选属性“isCustomShardKeyHashed”变为只写
  • 请求可选属性“isShardKeyUnique”变为只写
  • 请求可选属性“numInitialChunks”变为只写
  • 请求可选属性“presplitHashedZones”变为只写
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 在“results/items/delivery/statusName”响应属性中添加了新的“PENDING”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 在“results/items/delivery/statusName”响应属性中添加了新的“PENDING”枚举值
  • 已将新的“PENDING”枚举值添加到请求属性“delivery/statusName”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs/{jobId}
Updated
  • 已将新的“PENDING”枚举值添加到“delivery/statusName”响应属性中
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将“ Azure ”鉴别器映射键添加到“/items/ 存储/stores/items/”响应属性
  • 将“#/components/schemas/DataLakeAzureBlobStore”添加到响应的“/items/ 存储/stores/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将“ Azure ”鉴别器映射键添加到“存储/stores/items/”请求属性
  • 将“#/components/schemas/DataLakeAzureBlobStore”添加到“存储/stores/items/”请求属性“oneOf”列表
  • 将“ Azure ”鉴别器映射键添加到“存储/stores/items/”响应属性
  • 将“#/components/schemas/DataLakeAzureBlobStore”添加到响应的“存储/stores/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将“ Azure ”鉴别器映射键添加到“存储/stores/items/”响应属性
  • 将“#/components/schemas/DataLakeAzureBlobStore”添加到响应的“存储/stores/items/”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将“ Azure ”鉴别器映射键添加到“存储/stores/items/”请求属性
  • 将“#/components/schemas/DataLakeAzureBlobStore”添加到“存储/stores/items/”请求属性“oneOf”列表
  • 将“ Azure ”鉴别器映射键添加到“存储/stores/items/”响应属性
  • 将“#/components/schemas/DataLakeAzureBlobStore”添加到响应的“存储/stores/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“azureKeyVault/requirePrivateNetworking”
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在响应中添加了可选属性“azureKeyVault/requirePrivateNetworking”
  • 添加了新的可选请求属性“azureKeyVault/requirePrivateNetworking”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema # 14 /eventTypeName 响应属性]”中添加了新的“ATLAS_SQL_SCHEDULED_UPDATE_CREATED、ATLAS_SQL_SCHEDULED_UPDATE_MODIFIED、ATLAS_SQL_SCHEDULED_UPDATE_REMOVED、INDEPENDENT_SHARD_SCALING_AVAILABLE、QUEUED_ADMIN_ACTION_CREATED”枚举值：NDS Audits
  • 在“results/items/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 32 : Version Audit Types]/”响应属性中添加了新的“CLUSTER_FCV_DOWNGRADED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema # 14 : NDS Audits]/eventTypeName' 响应属性中添加了新的 'ATLAS_SQL_SCHEDULED_UPDATE_CREATED、ATLAS_SQL_SCHEDULED_UPDATE_MODIFIED、ATLAS_SQL_SCHEDULED_UPDATE_REMOVED、INDEPENDENT_SHARD_SCALING_AVAILABLE、QUEUED_ADMIN_ACTION_CREATED'枚举值
  • 在“/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 32 : Version Audit Types]/”响应属性中添加了新的“CLUSTER_FCV_DOWNGRADED”枚举值
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processors
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的“SECURITY_CONTACT_MODIFIED”枚举值添加到“results/items/oneOf[subschema # 8 : Org Events]/eventTypeName”响应属性中
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的“SECURITY_CONTACT_MODIFIED”枚举值添加到“/oneOf[subschema # 8 : Org Events]/eventTypeName”响应属性中
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 添加了新的可选“查询”请求参数“fromDate”
  • 添加了新的可选“查询”请求参数“orderBy”
  • 添加了新的可选“查询”请求参数“sortBy”
  • 添加了新的可选“查询”请求参数“statusNames”
  • 添加了新的可选“查询”请求参数“toDate”

2024 年 7 月 24 日发布

GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • 响应属性 'results/items/bucketName、results/items/cloudProvider、results/items/iamRoleId、results/items/roleId、results/items/serviceUrl、results/items/tenantId' 变为必填项
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
Updated
  • “/bucketName”请求属性的 maxLength 已设立为“ 63 ”
  • “/bucketName”请求属性的 maxLength 已设立为“ 63 ”
  • “/serviceUrl”请求属性的 maxLength 已设立为“ 55 ”
  • “bucketName”请求属性的 maxLength 已设立为“ 63 ”
  • 响应属性 '/bucketName, /cloudProvider, /iamRoleId, /roleId, /serviceUrl, /tenantId, bucketName, cloudProvider' 变为必填项
DELETE /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 已将“path”请求参数“exportBucketId”的模式从“^((?!xn--)(?!.*-s 3 alias)[az 0 - 9 ][az 0 - 9 -]{1 , 61}[az 0 - 9 ])$' 为 '^([af 0 - 9 ]{24})$'
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
Updated
  • 已将“path”请求参数“exportBucketId”的模式从“^((?!xn--)(?!.*-s 3 alias)[az 0 - 9 ][az 0 - 9 -]{1 , 61}[az 0 - 9 ])$' 为 '^([af 0 - 9 ]{24})$'
  • 响应属性 '/bucketName, /cloudProvider, /iamRoleId, /roleId, /serviceUrl, /tenantId, bucketName, cloudProvider' 变为必填项

2024 年 7 月 18 日发布

GET /api/atlas/v2/eventTypes
Updated
  • 向响应添加了可选属性“links、results、totalCount”

2024 年 7 月 13 日发布

DELETE /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:start
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor/{processorName}:stop
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema # 8 : Org Events]/eventTypeName”响应属性中添加了新的“ORG_NO_FINANCIAL_PROTECTION”、“ORG_UNDER_FINANCIAL_PROTECTION”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema # 8 : Org Events]/eventTypeName”响应属性中添加了新的“ORG_NO_FINANCIAL_PROTECTION”、“ORG_UNDER_FINANCIAL_PROTECTION”枚举值

2024 年 7 月 11 日发布

GET /api/atlas/v2/eventTypes
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 'results/items/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“results/items/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 请求 属性 '/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 ：NDS Auto Scaling 审核类型]/'
  • 删除了请求属性'/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/' 的枚举值 'MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 请求 属性 '/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 ：NDS Auto Scaling 审核类型]/'
  • 删除了请求属性'/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/' 的枚举值 'MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 'results/items/oneOf[subschema # 7 : Any Other Alerts]/eventTypeName/oneOf[subschema # 14 ：NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“results/items/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 5 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 'results/items/oneOf[subschema # 7 : Any Other Alerts]/eventTypeName/oneOf[subschema # 14 ：NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“results/items/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 5 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 7 : Any Other Alerts]/eventTypeName/oneOf[subschema # 14 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 5 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 7 : Any Other Alerts]/eventTypeName/oneOf[subschema # 14 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 5 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_INITIATED, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 'results/items/oneOf[subschema # 1 : Any Other Alert Configurations]/eventTypeName/oneOf[subschema # 11 : NDS Auto Scaling 审核类型]/' 响应属性
  • 删除了“results/items/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 4 : Group Event Types]/”响应属性中的“MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 已删除“mongoDBMajorVersion”响应的属性默认值“ 7.0 ”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • “mongoDBMajorVersion”请求属性默认值“ 7.0 ”已删除
  • 已删除“mongoDBMajorVersion”响应的属性默认值“ 7.0 ”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • “mongoDBMajorVersion”请求属性默认值“ 7.0 ”已删除
  • 已删除“mongoDBMajorVersion”响应的属性默认值“ 7.0 ”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 已删除“mongoDBMajorVersion”响应的属性默认值“ 7.0 ”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • “mongoDBMajorVersion”请求属性默认值“ 7.0 ”已删除
  • 已删除“mongoDBMajorVersion”响应的属性默认值“ 7.0 ”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写属性“deleteCopiedBackups/items/zoneId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写属性“deleteCopiedBackups/items/zoneId”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 在响应中添加了可选的只写属性“deleteCopiedBackups/items/zoneId”
  • 添加了新的可选请求属性“deleteCopiedBackups/items/zoneId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots
Updated
  • 将新的 'CONFIG_SHARD_REPLICA_SET'枚举值添加到 'results/items/parts/items/typeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 将新的“CONFIG_SHARD_REPLICA_SET”枚举值添加到“parts/items/typeName”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/snapshots/{snapshotId}
Updated
  • 将新的“CONFIG_SHARD_REPLICA_SET”枚举值添加到“parts/items/typeName”响应属性中
  • 已将新的“CONFIG_SHARD_REPLICA_SET”枚举值添加到请求属性“parts/items/typeName”
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • “/items/inheritedRoles/items/ 角色”响应的属性模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\ atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
  • “/items/roleName”响应的属性模式“^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|” readWrite|dbAdmin|dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 删除了模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin |clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' from the 请求 属性 'inheritedRoles/items/ 角色'
  • 删除了模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin请求属性“roleName”中的“|clusterAdmin|clusterManager|clusterMonitor|hostManager|备份|恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$”
  • “inheritedRoles/items/ 角色”响应的属性模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read |readWrite|dbAdmin|dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
  • “roleName”响应的属性模式“^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin” |dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
DELETE /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 删除了模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin “|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$”（来自“path”请求参数“roleName”）
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 删除了模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin “|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$”（来自“path”请求参数“roleName”）
  • “inheritedRoles/items/ 角色”响应的属性模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read |readWrite|dbAdmin|dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
  • “roleName”响应的属性模式“^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin” |dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 删除了模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin “|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$”（来自“path”请求参数“roleName”）
  • 删除了模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin|dbOwner|userAdmin |clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' from the 请求 属性 'inheritedRoles/items/ 角色'
  • “inheritedRoles/items/ 角色”响应的属性模式'^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read |readWrite|dbAdmin|dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
  • “roleName”响应的属性模式“^\b(?!xgen-)([ 0 - 9 A-Za-z_\-]+)\b(?<!\atlasAdmin|read|readWrite|dbAdmin” |dbOwner|userAdmin|clusterAdmin|clusterManager|clusterMonitor|hostManager| 备份| 恢复|readAnyDatabase|readWriteAnyDatabase|userAdminAnyDatabase|dbAdminAnyDatabase|root|__system)$' 已删除
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将“#/components/schemas/AtlasDataFederationAzureRegion”添加到响应的“/items/dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 从响应的“/items/dataProcessRegion/ 地区”响应属性“oneOf”列表中删除了“#/components/schemas/ApiAtlasDataLakeAzureRegionView”
  • 在响应中添加了可选属性“/items/cloudProviderConfig/ Azure ”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 请求属性“cloudProviderConfig/ Amazon Web Services ”变为可选
  • 将“#/components/schemas/AtlasDataFederationAzureRegion”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/AtlasDataFederationAzureRegion”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已从响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“#/components/schemas/ApiAtlasDataLakeAzureRegionView”
  • 已将新的“MONTREAL_CAN, TOKYO_JPN”枚举值添加到请求属性“dataProcessRegion/ 地区/”
  • 在响应中添加了可选属性“cloudProviderConfig/ Azure ”
  • 添加了新的可选请求属性“cloudProviderConfig/ Azure ”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 将“#/components/schemas/AtlasDataFederationAzureRegion”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已从响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“#/components/schemas/ApiAtlasDataLakeAzureRegionView”
  • 在响应中添加了可选属性“cloudProviderConfig/ Azure ”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 请求属性“cloudProviderConfig/ Amazon Web Services ”变为可选
  • 将“#/components/schemas/AtlasDataFederationAzureRegion”添加到“dataProcessRegion/ 地区”请求属性“oneOf”列表
  • 将“#/components/schemas/AtlasDataFederationAzureRegion”添加到响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中
  • 已从响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“#/components/schemas/ApiAtlasDataLakeAzureRegionView”
  • 已将新的“MONTREAL_CAN, TOKYO_JPN”枚举值添加到请求属性“dataProcessRegion/ 地区/”
  • 在响应中添加了可选属性“cloudProviderConfig/ Azure ”
  • 添加了新的可选请求属性“cloudProviderConfig/ Azure ”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the 'results/items/oneOf[subschema # 15 : NDS Auto Scaling Audits]/eventTypeName' response 属性
  • 已从“results/items/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 12 : Group Event Types”中删除了“M 0 _CLUSTERS_PER_GROUP_WITHIN_LIMIT、MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值]/' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • Added the new 'COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, COMPUTE_AUTO_SCALE_OPLOG_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_OPLOG_FAIL_BASE, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_SCALE_DOWN_FAIL_BASE, DISK_AUTO_SCALE_MAX_DISK_SIZE_FAIL, DISK_AUTO_SCALE_OPLOG_FAIL' 枚举 values to the '/oneOf[subschema # 15 : NDS Auto Scaling Audits]/eventTypeName' response 属性
  • 已从“/oneOf[subschema # 1 ：任何其他事件]/eventTypeName/oneOf[subschema # 12 ：群组事件类型]/”中删除“M 0 _CLUSTERS_PER_GROUP_WITHIN_LIMIT、MAX_M 0 _CLUSTERS_PER_GROUP_EXCEEDED”枚举值响应属性
GET /api/atlas/v2/groups/{groupId}/mongoDBVersions
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/processor
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 添加了新的可选“查询”请求参数“viewLinkedInvoices”
  • 从响应中删除了可选属性“results/items/groupId”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AZURE_SNAPSHOT_EXPORT_UPLOAD”枚举值
  • 从响应中删除了可选属性“results/items/groupId”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 已将新的“ATLAS_NDS_AZURE_SNAPSHOT_EXPORT_UPLOAD”枚举值添加到“lineItems/items/sku”响应属性中
  • 从响应中删除了可选属性“groupId”

2024 年 7 月 06 日发布

GET /api/atlas/v2/unauth/controlPlaneIPAddresses
Updated
  • 端点方案安全“未验证”已从API中删除

2024 年 7 月 02 日发布

GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AWS_COMPRESSED_OBJECT_STORAGE”、“ATLAS_NDS_AZURE_COMPRESSED_OBJECT_STORAGE”、“ATLAS_NDS_GCP_COMPRESSED_OBJECT_STORAGE”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 在“lineItems/items/sku”响应属性中添加了新的“ATLAS_NDS_AWS_COMPRESSED_OBJECT_STORAGE”、“ATLAS_NDS_AZURE_COMPRESSED_OBJECT_STORAGE”、“ATLAS_NDS_GCP_COMPRESSED_OBJECT_STORAGE”枚举值

2024 年 6 月 29 日发布

GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在 'results/items/lineItems/items/sku' 响应属性中添加了新的 'ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP 10 、 ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP 50 '枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 已将新的 'ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP 10 、 ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP 50 '枚举值添加到 'lineItems/items/sku' 响应属性

2024 年 6 月 28 日发布

GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 从响应中删除了可选属性“results/items/lineItems、results/items/endings、results/items/refunds”

2024 年 6 月 27 日发布

POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 添加了新的可选请求属性“dropDestinationData”
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 添加了新的可选请求属性“dropDestinationData”

2024 年 6 月 26 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已重新激活
  • 删除了可选属性 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置] /diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/analyticsSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/electableSpecs/diskSizeGB，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, results/items/replicationSpecs/items/ regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskSizeGB、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[ subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/diskSizeGB, Results/items/ replicationSp ecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, Results/items/replicationSpecs/items/ regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/diskSizeGB，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/ oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB, results/ items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, Results/items/replicationSpecs/ items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1 ： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs /items/oneOf[subschema #3： GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf [subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群 HA响应中的 rdware Settings]/diskSizeGB'
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已重新激活
  • 删除了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/r egionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件re Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsSpecs/diskSizeGB， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/ , replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/响应中的“diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB”
  • 删除了请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/re gionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件eSettings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsSpecs/diskSizeGB， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB , replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已重新激活
  • 删除了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/r egionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件re Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsSpecs/diskSizeGB， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/ , replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/响应中的“diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已重新激活
  • 删除了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/r egionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件re Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsSpecs/diskSizeGB， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/ , replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4：租户区域复制规范]/electableSpecs/响应中的“diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB”
  • 删除了请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/re gionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件eSettings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/analyticsSpecs/diskSizeGB， replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB , replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已重新激活
  • 在响应中添加了可选属性“defaultReadConcern、failIndexKeyTooLong”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已重新激活
  • 在响应中添加了可选属性“defaultReadConcern、failIndexKeyTooLong”
  • 添加了新的可选请求属性“defaultReadConcern, failIndexKeyTooLong”

2024 年 6 月 25 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到“results/items/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到“/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”请求属性“oneOf”列表
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到了“/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到了“/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到了“/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到“/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”请求属性“oneOf”列表
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到了“/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 已将“subschema # 14 ：NDS Auto Scaling 审核类型”添加到“results/items/oneOf[subschema # 7 ：任何其他警报]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 已将“subschema # 14 ：NDS Auto Scaling 审核类型”添加到“results/items/oneOf[subschema # 7 ：任何其他警报]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema # 14 : NDS Auto Scaling Audit Types”（子模式 # ：NDS Auto Scaling 审核类型）添加到了响应的“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“subschema # 14 : NDS Auto Scaling Audit Types”（子模式 # ：NDS Auto Scaling 审核类型）添加到了响应的“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“subschema # 11 ：NDS Auto Scaling 审核类型”添加到“results/items/oneOf[subschema # 1 ：任何其他警报配置]/eventTypeName”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
Updated
  • 添加了请求鉴别器
  • 将 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal' 添加到请求正文 'oneOf' 列表
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
Updated
  • 添加了请求鉴别器
  • 将 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal' 添加到请求正文 'oneOf' 列表
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已弃用
  • 添加了可选属性 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings] /diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/analyticsSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/electableSpecs/diskSizeGB，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1： Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services [subschema #1: Amazon Web Services Amazon Web Services复制规范]/readOnlySpecs/diskSizeGB, results/items/replicationSpecs/items/ regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/oneOf[subschema #1: 集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/diskSizeGB、results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[ subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/electableSpecs/diskSizeGB, Results/items/ replicationSpec s/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/ regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/diskSizeGB，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/readOnlySpecs/ oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB, results/ items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, Results/items/replicationSpecs/ items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/diskSizeGB，results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3： GCP区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items /oneOf[subschema #3： GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1 ： Amazon Web Services集群硬ware Settings]/diskSizeGB' 到响应
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已弃用
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/reg ionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs /items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf [subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB' 到响应
  • 添加了新的可选请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items /regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs /oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items /regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpe cs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/ items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群[硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB , replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items /oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1 ： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 : GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs /diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已弃用
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/reg ionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs /items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf [subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB' 到响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已弃用
  • 添加了可选属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/oneOf [subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs /items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/reg ionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/ oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs /items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf [subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional ReplicationSpecifications]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/diskSizeGB 、replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB' 到响应
  • 添加了新的可选请求属性 'replicationSpecs/items/regionConfigs/items/electableSpecs/diskSizeGB、replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB、replicationSpecs/items /regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/analyticsSpecs /oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items /regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpe cs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services区域复制规范]/readOnlySpecs/oneOf[subschema #1： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/analyticsSpecs/diskSizeGB, replicationSpecs/ items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2： Azure区域复制规范]/electableSpecs/diskSizeGB，replicationSpecs/items/regionConfigs/items/oneOf[subschema #2： Azure区域复制规范]/electableSpecs/oneOf[subschema #1： Amazon Web Services集群[硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/diskSizeGB , replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services Cluster Hardware Settings]/diskSizeGB, replicationSpecs/items/regionConfigs/items /oneOf[subschema #3: GCP区域复制规范]/electableSpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/electableSpecs/oneOf[subschema #1 ： Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP区域复制规范]/readOnlySpecs/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3 : GCP区域复制规范]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs /diskSizeGB, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 租户区域复制规范]/electableSpecs/oneOf[subschema #1: Amazon Web Services集群硬件设置]/diskSizeGB'
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 在响应中添加了可选属性“results/items/components/items/exportId”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports
Updated
  • 在响应中添加了可选属性“components/items/exportId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/exports/{exportId}
Updated
  • 在响应中添加了可选属性“components/items/exportId”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 在响应中添加了可选属性“results/items/components/items/downloadUrl”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs
Updated
  • 在响应中添加了可选属性“components/items/downloadUrl”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/restoreJobs/{restoreJobId}
Updated
  • 在响应中添加了可选属性“components/items/downloadUrl”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 添加了状态为“ 409 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了状态为“ 409 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已弃用
  • 从响应中删除了可选属性“defaultReadConcern、failIndexKeyTooLong”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已弃用
  • 从响应中删除了可选属性“defaultReadConcern、failIndexKeyTooLong”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 添加了状态为“ 409 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • “分析器”请求属性默认值“lucene.standard”已删除
  • 添加了状态为“ 409 ”的非成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • “分析器”请求属性默认值“lucene.standard”已删除
  • 添加了状态为“ 409 ”的非成功响应
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[subschema # 5 : ServiceAccount Events]/eventTypeName”响应属性中添加了新的“SERVICE_ACCOUNT_UI_IP_ACCESS_LIST_INHERITANCE_ENABLED”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[subschema # 5 : ServiceAccount Events]/eventTypeName' 响应属性中添加了新的 'SERVICE_ACCOUNT_UI_IP_ACCESS_LIST_INHERITANCE_ENABLED'枚举值
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/networking”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/networking”
  • 添加了新的可选请求属性“connections/items/networking”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/networking”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/networking”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“/networking”
  • 添加了新的可选请求属性“/networking”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性“/networking”
  • 添加了新的可选请求属性“/networking”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的“ORG_SERVICE_ACCOUNT_MAX_SECRET_VALIDITY_EDITED”枚举值添加到“results/items/oneOf[subschema # 8 : Org Events]/eventTypeName”响应属性中
  • 在“results/items/oneOf[subschema # 5 : ServiceAccount Events]/eventTypeName”响应属性中添加了新的“SERVICE_ACCOUNT_UI_IP_ACCESS_LIST_INHERITANCE_ENABLED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将新的“ORG_SERVICE_ACCOUNT_MAX_SECRET_VALIDITY_EDITED”枚举值添加到“/oneOf[subschema # 8 : Org Events]/eventTypeName”响应属性中
  • 在 '/oneOf[subschema # 5 : ServiceAccount Events]/eventTypeName' 响应属性中添加了新的 'SERVICE_ACCOUNT_UI_IP_ACCESS_LIST_INHERITANCE_ENABLED'枚举值

2024 年 6 月 22 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已重新激活
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已重新激活

2024 年 6 月 13 日发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”请求属性
  • 已从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”请求属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
  • 将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”请求属性
  • 已从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”请求属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
  • 将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“[REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键添加到“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“results/items/oneOf[subschema # 3 : App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键

2024 年 6 月 12 日发布

GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[subschema # 6 : Billing Events]/eventTypeName”响应属性中添加了新的“EVERGREEN_PRIORITY_MODIFIED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在“/oneOf[subschema # 6 : Billing Events]/eventTypeName”响应属性中添加了新的“EVERGREEN_PRIORITY_MODIFIED”枚举值

2024 年 6 月 04 日发布

PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
Updated
  • 将“#/components/schemas/TextSearchIndexDefinition, #/components/schemas/VectorSearchIndexDefinition”添加到“definition”请求属性“oneOf”列表
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
Updated
  • 将“#/components/schemas/TextSearchIndexDefinition, #/components/schemas/VectorSearchIndexDefinition”添加到“definition”请求属性“oneOf”列表

31 5 月2024发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 将“[REALM_SYNC_CLIENT_WRITES_FAILED REALM_SYNC_CLIENT_READS_FAILED]”鉴别器映射键添加到“results/items/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“results/items/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_UPLOADS_FAILED REALM_SYNC_CLIENT_UPLOADS_INVALID]”鉴别器映射键
POST /api/atlas/v2/groups/{groupId}/alertConfigs
已交
  • 添加了“[REALM_SYNC_CLIENT_WRITES_FAILED REALM_SYNC_CLIENT_READS_FAILED]”鉴别器映射键到“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”请求属性
  • 已从“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”请求属性中删除“[REALM_SYNC_CLIENT_UPLOADS_FAILED REALM_SYNC_CLIENT_UPLOADS_INVALID]”鉴别器映射键
  • 将“[REALM_SYNC_CLIENT_READS_FAILED REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键添加到“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_UPLOADS_FAILED REALM_SYNC_CLIENT_UPLOADS_INVALID]”鉴别器映射键
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“[REALM_SYNC_CLIENT_WRITES_FAILED REALM_SYNC_CLIENT_READS_FAILED]”鉴别器映射键添加到“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_UPLOADS_INVALID REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 将“[REALM_SYNC_CLIENT_WRITES_FAILED REALM_SYNC_CLIENT_READS_FAILED]”鉴别器映射键添加到“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_UPLOADS_FAILED REALM_SYNC_CLIENT_UPLOADS_INVALID]”鉴别器映射键
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
已交
  • 添加了“[REALM_SYNC_CLIENT_WRITES_FAILED REALM_SYNC_CLIENT_READS_FAILED]”鉴别器映射键到“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”请求属性
  • 已从“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”请求属性中删除“[REALM_SYNC_CLIENT_UPLOADS_FAILED REALM_SYNC_CLIENT_UPLOADS_INVALID]”鉴别器映射键
  • 将“[REALM_SYNC_CLIENT_READS_FAILED REALM_SYNC_CLIENT_WRITES_FAILED]”鉴别器映射键添加到“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_UPLOADS_FAILED REALM_SYNC_CLIENT_UPLOADS_INVALID]”鉴别器映射键
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
已交
  • 添加了新的可选请求属性“acknowledgedUntil、acknowledgementComment、unacknowledgeAlert”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
已交
  • 将“[REALM_SYNC_CLIENT_WRITES_FAILED REALM_SYNC_CLIENT_READS_FAILED]”鉴别器映射键添加到“results/items/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性
  • 已从“results/items/oneOf[subschema #3: Atlas App Services Metric Alert Configuration]/metricThreshold”响应属性中删除“[REALM_SYNC_CLIENT_UPLOADS_INVALID REALM_SYNC_CLIENT_UPLOADS_FAILED]”鉴别器映射键
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets
已交
  • 已将鉴别器添加到 'results/items/' 响应属性
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket' 添加到响应的 'results/items/' 响应属性 'oneOf' 列表
  • 从响应中删除了可选属性“results/items/iamRoleId”
POST /api/atlas/v2/groups/{groupId}/backup/exportBuckets
已交
  • 添加了请求鉴别器
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket' 添加到请求正文 'oneOf' 列表
  • 为响应状态“200”添加了响应鉴别器
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket' 添加到响应的响应正文 'oneOf' 列表
  • 从响应中删除了可选属性“iamRoleId”
  • 删除了请求属性“iamRoleId”
GET /api/atlas/v2/groups/{groupId}/backup/exportBuckets/{exportBucketId}
已交
  • 为响应状态“200”添加了响应鉴别器
  • 将 '#/components/schemas/DiskBackupSnapshotAWSExportBucket, #/components/schemas/DiskBackupSnapshotAzureExportBucket' 添加到响应的响应正文 'oneOf' 列表
  • 从响应中删除了可选属性“iamRoleId”
POST /api/atlas/v2/groups/{groupId}/cloudProviderAccess
已交
  • 删除了请求鉴别器
PATCH /api/atlas/v2/groups/{groupId}/cloudProviderAccess/{roleId}
已交
  • 删除了请求鉴别器
  • 添加了新的可选请求属性“iamAssumedRoleArn”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
已交
  • API操作ID “createAtlasSearchIndex”已删除并替换为“createAtlasSearchIndexDeprecated”
  • 端点已弃用
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
已交
  • API操作ID “listAtlasSearchIndexes”已删除并替换为“listAtlasSearchIndexesDeprecated”
  • 端点已弃用
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
已交
  • API操作ID “deleteAtlasSearchIndex”已删除并替换为“deleteAtlasSearchIndexDeprecated”
  • 端点已弃用
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
已交
  • API操作ID “getAtlasSearchIndex”已删除并替换为“getAtlasSearchIndexDeprecated”
  • 端点已弃用
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
已交
  • API操作ID “updateAtlasSearchIndex”已删除并替换为“updateAtlasSearchIndexDeprecated”
  • 端点已弃用
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 已删除状态为“ 200 ”的成功响应
  • 添加了状态为“204”的成功响应
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 添加了状态为“ 409 ”的非成功响应
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 已删除状态为“ 200 ”的成功响应
  • 添加了状态为“ 409 ”的非成功响应
  • 添加了状态为“201”的成功响应
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{databaseName}/{collectionName}/{indexName}
已交
  • 已添加端点
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/indexes/{indexId}
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/managedSlowMs
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams
已交
  • 在响应中添加了可选属性“results/items/connections/items/proxyInfo”
POST /api/atlas/v2/groups/{groupId}/streams
已交
  • 在响应中添加了可选属性“connections/items/proxyInfo”
  • 添加了新的可选请求属性“connections/items/proxyInfo”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 在响应中添加了可选属性“connections/items/proxyInfo”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
已交
  • 在响应中添加了可选属性“connections/items/proxyInfo”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 在响应中添加了可选属性“results/items/proxyInfo”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
已交
  • 在响应中添加了可选属性“/proxyInfo”
  • 添加了新的可选请求属性“/proxyInfo”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 在响应中添加了可选属性“/proxyInfo”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
已交
  • 在响应中添加了可选属性“/proxyInfo”
  • 添加了新的可选请求属性“/proxyInfo”
POST /api/atlas/v2/groups/{groupId}:migrate
已交
  • 已添加端点

22 5 月2024发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 添加了必需属性 'results/items/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/ 操作符, results/items/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, results/items/oneOf[subschema # 13 ：无服务器警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 13 ：无服务器警报配置]/matchers/items/ 操作符, results/items/oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, results/items/oneOf[subschema # 1 : Any other Alert Configurations]/matchers/items/fieldName, results/items/oneOf[subschema # 1 : Any other Alerts Configurations]/matchers/items/ 操作符, Results/items/oneOf[subschema # 1 : Any other Alert Configurations]/matchers/items/value, results/items/oneOf[subschema # 4 : Billing Threshol d 警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 4 : 账单阈值警报配置 ]/matchers/items/ 操作符, results/items/oneOf[subschema # 4 : 账单阈值警报Configuration]/matchers/items/value, results/items/oneOf[subschema # 6 : Cps 备份阈值警报 Configuration]/matchers/items/fieldName, results/items/oneOf[subschema # 6 : Cps 备份阈值警报Configuration]/matchers/items/ 操作符, results/items/oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/value, results/items/oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/ 操作符, results/items/oneOf[subschema # 7 : 加密密钥警报配置]/ matchers/items/value' 到响应
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 请求可选属性'/oneOf[subschema # 10 : NDS X 509 User Authentication Alert Configuration]/matchers' 变为非只读属性
  • 请求可选属性“/oneOf[subschema # 13 : Serverless Alert Configuration]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 1 : Any other Alert Configurations]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 4 : Billing Threshold Alert Configuration]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 7 : Encryption Key Alert Configuration]/matchers”变为非只读属性
  • 添加了必需属性 '/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置] /matchers/items/operator, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items /fieldName, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/operator, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, /oneOf[subschema # 1 : 任何其他警报配置]/matchers/items/fieldName, /oneOf[subschema # 1 任何其他警报配置]/matchers/items/operator, /oneOf[subschema # 1 : 任何其他警报配置]/ matchers/items/value, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/operato r, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/value, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/operator，/oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/value，/oneOf[subschema # 7 ：加密密钥警报配置]/matchers/items/fieldName, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/operator, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/ value' 到响应
  • 添加了新的必需请求属性 '/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, /oneOf[subschema # 10 : NDS X 509用户身份验证警报Configuration]/matchers/items/operator, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers /items/fieldName, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/operator, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, /oneOf[subschema # 1 ：任何其他警报配置]/matchers/items/fieldName、/oneOf[subschema # 1 ：任何其他警报配置]/matchers/items/operator、/oneOf[subschema # 1 ：任何其他警报配置]/matchers/items/value, /oneOf[subschema # 4 : 账单阈值警报配置 ]/matchers/items/fieldName, /oneOf[subschema # 4 : 账单阈值警报配置 ]/matchers/i tems/operator, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/value, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/fieldName, /oneOf[ subschema # 6 : Cps 备份阈值警报配置]/matchers/items/operator, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/value, /oneOf[subschema # 7 :加密密钥警报配置]/matchers/items/fieldName, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/operator, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/ items/value'
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了必需属性 '/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置] /matchers/items/operator, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items /fieldName, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/operator, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, /oneOf[subschema # 1 : 任何其他警报配置]/matchers/items/fieldName, /oneOf[subschema # 1 任何其他警报配置]/matchers/items/operator, /oneOf[subschema # 1 : 任何其他警报配置]/ matchers/items/value, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/operato r, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/value, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/operator，/oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/value，/oneOf[subschema # 7 ：加密密钥警报配置]/matchers/items/fieldName, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/operator, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/ value' 到响应
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 添加了必需属性 '/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置] /matchers/items/operator, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items /fieldName, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/operator, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, /oneOf[subschema # 1 : 任何其他警报配置]/matchers/items/fieldName, /oneOf[subschema # 1 任何其他警报配置]/matchers/items/operator, /oneOf[subschema # 1 : 任何其他警报配置]/ matchers/items/value, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/operato r, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/value, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/operator，/oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/value，/oneOf[subschema # 7 ：加密密钥警报配置]/matchers/items/fieldName, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/operator, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/ value' 到响应
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 请求可选属性'/oneOf[subschema # 10 : NDS X 509 User Authentication Alert Configuration]/matchers' 变为非只读属性
  • 请求可选属性“/oneOf[subschema # 13 : Serverless Alert Configuration]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 1 : Any other Alert Configurations]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 4 : Billing Threshold Alert Configuration]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers”变为非只读属性
  • 请求可选属性“/oneOf[subschema # 7 : Encryption Key Alert Configuration]/matchers”变为非只读属性
  • 添加了必需属性 '/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置] /matchers/items/operator, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items /fieldName, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/operator, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, /oneOf[subschema # 1 : 任何其他警报配置]/matchers/items/fieldName, /oneOf[subschema # 1 任何其他警报配置]/matchers/items/operator, /oneOf[subschema # 1 : 任何其他警报配置]/ matchers/items/value, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/operato r, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/value, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/fieldName, /oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/operator，/oneOf[subschema # 6 ：Cps 备份阈值警报配置]/matchers/items/value，/oneOf[subschema # 7 ：加密密钥警报配置]/matchers/items/fieldName, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/operator, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/ value' 到响应
  • 添加了新的必需请求属性 '/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, /oneOf[subschema # 10 : NDS X 509用户身份验证警报Configuration]/matchers/items/operator, /oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers /items/fieldName, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/operator, /oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, /oneOf[subschema # 1 ：任何其他警报配置]/matchers/items/fieldName、/oneOf[subschema # 1 ：任何其他警报配置]/matchers/items/operator、/oneOf[subschema # 1 ：任何其他警报配置]/matchers/items/value, /oneOf[subschema # 4 : 账单阈值警报配置 ]/matchers/items/fieldName, /oneOf[subschema # 4 : 账单阈值警报配置 ]/matchers/i tems/operator, /oneOf[subschema # 4 : 账单阈值警报配置]/matchers/items/value, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/fieldName, /oneOf[ subschema # 6 : Cps 备份阈值警报配置]/matchers/items/operator, /oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/value, /oneOf[subschema # 7 :加密密钥警报配置]/matchers/items/fieldName, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/operator, /oneOf[subschema # 7 : 加密密钥警报配置]/matchers/ items/value'
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 添加了必需属性 'results/items/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/ 操作符, results/items/oneOf[subschema # 10 : NDS X 509用户身份验证警报配置]/matchers/items/value, results/items/oneOf[subschema # 13 ：无服务器警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 13 ：无服务器警报配置]/matchers/items/ 操作符, results/items/oneOf[subschema # 13 : Serverless Alert Configuration]/matchers/items/value, results/items/oneOf[subschema # 1 : Any other Alert Configurations]/matchers/items/fieldName, results/items/oneOf[subschema # 1 : Any other Alerts Configurations]/matchers/items/ 操作符, Results/items/oneOf[subschema # 1 : Any other Alert Configurations]/matchers/items/value, results/items/oneOf[subschema # 4 : Billing Threshol d 警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 4 : 账单阈值警报配置 ]/matchers/items/ 操作符, results/items/oneOf[subschema # 4 : 账单阈值警报Configuration]/matchers/items/value, results/items/oneOf[subschema # 6 : Cps 备份阈值警报 Configuration]/matchers/items/fieldName, results/items/oneOf[subschema # 6 : Cps 备份阈值警报Configuration]/matchers/items/ 操作符, results/items/oneOf[subschema # 6 : Cps 备份阈值警报配置]/matchers/items/value, results/items/oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/fieldName, results/items/oneOf[subschema # 7 : 加密密钥警报配置]/matchers/items/ 操作符, results/items/oneOf[subschema # 7 : 加密密钥警报配置]/ matchers/items/value' 到响应

16 5 月2024发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已重新激活
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已重新激活
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已重新激活
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已重新激活

09 5 月2024发布

GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • Removed '[MAX_DISK_PARTITION_UTILIZATION_DATA DISK_PARTITION_UTILIZATION_INDEX MAX_DISK_PARTITION_UTILIZATION_INDEX MAX_DISK_PARTITION_UTILIZATION_JOURNAL DISK_PARTITION_UTILIZATION_DATA DISK_PARTITION_UTILIZATION_JOURNAL]' discriminator mapping keys from the 'results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold' response property
  • 在“results/items/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 已从 '/oneOf[subschema] Host 属性 : Configuration 请求 9
  • 已从 '/oneOf[subschema] Configuration Host Metrics 响应中删除了 '[DISK_PARTITION_UTILIZATION_JOURNAL DISK_PARTITION_UTILIZATION_DATA 9 MAX_DISK_PARTITION_UTILIZATION_INDEX MAX_DISK_PARTITION_UTILIZATION_JOURNAL 属性 ]' 鉴别器映射键：
  • 在“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在请求属性 '/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/' 中添加了新的 'CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY' 枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 从 '/oneOf[subschema 9 Configuration Host MetricAlertMetric 响应中删除了 '[MAX_DISK_PARTITION_UTILIZATION_DATA DISK_PARTITION_UTILIZATION_JOURNAL]' 鉴别器映射键
  • 在“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 从 '/oneOf[subschema 9 Configuration Host MetricAlertMetric 响应中删除了 '[MAX_DISK_PARTITION_UTILIZATION_INDEX 属性 ]' 鉴别器映射键
  • 在“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 已从“/oneOf[subschema”HostMetric] 配置请求属性9中删除了 鉴别器映射键
  • 从 '/oneOf[subschema 9 Configuration Host MetricAlertMetric 响应中删除了 '[MAX_DISK_PARTITION_UTILIZATION_INDEX 属性 ]' 鉴别器映射键
  • 在“/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在请求属性 '/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/' 中添加了新的 'CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY' 枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将新的 'CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY' 枚举值添加到 'results/items/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/' 响应属性中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将新的 'CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY' 枚举值添加到 'results/items/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/' 响应属性中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
  • 在请求属性 '/oneOf[subschema # 7 : Any other Alerts]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/' 中添加了新的 'CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY' 枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • Removed '[MAX_DISK_PARTITION_UTILIZATION_INDEX MAX_DISK_PARTITION_UTILIZATION_JOURNAL DISK_PARTITION_UTILIZATION_DATA DISK_PARTITION_UTILIZATION_JOURNAL MAX_DISK_PARTITION_UTILIZATION_DATA DISK_PARTITION_UTILIZATION_INDEX]' discriminator mapping keys from the 'results/items/oneOf[subschema # 9 : Host Metric Alert Configuration]/metricThreshold' response 属性
  • 在“results/items/oneOf[subschema # 1 : Any other Alert Configurations]/eventTypeName/oneOf[subschema # 2 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已弃用
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 端点已弃用
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 请求可选属性“名称”变为非只读属性
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已弃用
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 端点已弃用
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已弃用
  • “chunkMigrationConcurrency”响应的属性默认值“ 1.00 ”已删除
  • “defaultWriteConcern”响应的属性默认值“ 1 ”已删除
  • “javascriptEnabled”响应的属性默认值“true”已删除
  • “noTableScan”响应的属性默认值“false”已删除
  • “queryStatsLogVerbosity”响应的属性默认值“ 1.00 ”已删除
  • “sampleSizeBIConnector”响应的属性默认值“ 1000.00 ”已删除
  • “transactionLifetimeLimitSeconds”响应的属性默认值“ 60.00 ”已删除
  • 删除了“defaultReadConcern”响应属性中的“linearizable、majority、snapshot”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 端点已弃用
  • “chunkMigrationConcurrency”请求属性默认值“ 1.00 ”已删除
  • “defaultWriteConcern”请求属性默认值“ 1 ”已删除
  • “javascriptEnabled”请求属性默认值“true”已删除
  • “noTableScan”请求属性默认值“false”已删除
  • “queryStatsLogVerbosity”请求属性默认值“ 1.00 ”已删除
  • “sampleSizeBIConnector”请求属性默认值“ 1000.00 ”已删除
  • “transactionLifetimeLimitSeconds”请求属性默认值“ 60.00 ”已删除
  • “chunkMigrationConcurrency”响应的属性默认值“ 1.00 ”已删除
  • “defaultWriteConcern”响应的属性默认值“ 1 ”已删除
  • “javascriptEnabled”响应的属性默认值“true”已删除
  • “noTableScan”响应的属性默认值“false”已删除
  • “queryStatsLogVerbosity”响应的属性默认值“ 1.00 ”已删除
  • “sampleSizeBIConnector”响应的属性默认值“ 1000.00 ”已删除
  • “transactionLifetimeLimitSeconds”响应的属性默认值“ 60.00 ”已删除
  • 删除了“defaultReadConcern”响应属性中的“linearizable、majority、snapshot”枚举值
  • 删除了请求属性“defaultReadConcern”的枚举值“linearizable、majority、snapshot”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的 'CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY'枚举值添加到 'results/items/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 5 : Cps Backup Event Types]/' 响应属性中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在“/oneOf[subschema # 1 : Any other Events]/eventTypeName/oneOf[subschema # 5 : Cps Backup Event Types]/”响应属性中添加了新的“CPS_CONCURRENT_SNAPSHOT_FAILED_WILL_RETRY”枚举值

04 5 月2024发布

GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 在响应中添加了可选属性“results/items/Payments/items/currency, Results/items/Payments/items/unitPrice”
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在响应中添加了可选属性“results/items/Payments/items/currency, Results/items/Payments/items/unitPrice”
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 在响应中添加了可选属性“付款/项目/货币，付款/项目/单位价格”

01 5 月2024发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 添加了新的可选“查询”请求参数“itemsPerPage”
  • 添加了新的可选“查询”请求参数“pageNum”
  • 向响应添加了可选属性“links、results、totalCount”

2024 年 4 月 30 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/globalClusterSelfManagedSharding”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“globalClusterSelfManagedSharding”
  • 添加了新的可选请求属性“globalClusterSelfManagedSharding”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在响应中添加了可选属性“globalClusterSelfManagedSharding”
  • 添加了新的可选请求属性“globalClusterSelfManagedSharding”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“globalClusterSelfManagedSharding”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“globalClusterSelfManagedSharding”
  • 添加了新的可选请求属性“globalClusterSelfManagedSharding”

2024 年 4 月 25 日发布

PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 请求属性“identityProviderId”变为可选
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在响应中添加了可选属性“results/items/ 通知/items/integrationId”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在响应中添加了可选属性“/ 通知/items/integrationId”
  • 添加了新的可选请求属性“/ 通知/items/integrationId”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“/ 通知/items/integrationId”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“/ 通知/items/integrationId”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应中添加了可选属性“/ 通知/items/integrationId”
  • 添加了新的可选请求属性“/ 通知/items/integrationId”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 在响应中添加了可选属性“results/items/ 通知/items/integrationId”
GET /api/atlas/v2/groups/{groupId}/integrations
Updated
  • 在响应中添加了可选属性“results/items/ ID ”
GET /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 已将可选属性“ ID ”添加到响应
POST /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 在响应中添加了可选属性“results/items/ ID ”
  • 添加了新的可选请求属性“ ID ”
PUT /api/atlas/v2/groups/{groupId}/integrations/{integrationType}
Updated
  • 在响应中添加了可选属性“results/items/ ID ”
  • 添加了新的可选请求属性“ ID ”

2024 年 4 月 23 日发布

GET /api/atlas/v2/alertConfigs/matchers/fieldNames
Updated
  • 将“Streams Matcher Fields”添加到响应的“/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“流处理器事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表中
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“流处理器事件类型”添加到“/eventTypeName”请求属性“oneOf”列表
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“流处理器事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“流处理器事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“流处理器事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“流处理器事件类型”添加到“/eventTypeName”请求属性“oneOf”列表
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“流处理器事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“流处理器事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表中
  • 将“StreamProcessorAlertViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“流处理器事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表中
  • 将“StreamProcessorAlertViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“StreamProcessorAlertViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“流处理器事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“StreamProcessorAlertViewForNdsGroup”添加到请求正文“oneOf”列表
  • 将“流处理器事件类型”添加到“/eventTypeName”请求属性“oneOf”列表
  • 将“StreamProcessorAlertViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“流处理器事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“流处理器事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表中
  • 将“StreamProcessorAlertConfigViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“Streams Event Types”、“Stream Processor Event Types”添加到“results/items/eventTypeName”响应属性“oneOf”列表中
  • 将“StreamsEventViewForNdsGroup, StreamProcessorEventViewForNdsGroup”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“StreamsEventViewForNdsGroup, StreamProcessorEventViewForNdsGroup”添加到响应的响应正文“oneOf”列表中
  • 将“Streams Event Types”、“Stream Processor Event Types”添加到“/eventTypeName”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 已从响应的“results/items/dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“ApiStreamsAzureRegionView”
  • 从“results/items/dataProcessRegion/region/”响应属性中删除了“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS”枚举值
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 已从“dataProcessRegion/region”请求属性“oneOf”列表中删除“ApiStreamsAzureRegionView”
  • 已从响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“ApiStreamsAzureRegionView”
  • 从“dataProcessRegion/ 地区/”响应属性中删除了“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS”枚举值
  • 删除了请求属性“dataProcessRegion/region/”的枚举值“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 已从响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“ApiStreamsAzureRegionView”
  • 从“dataProcessRegion/ 地区/”响应属性中删除了“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS”枚举值
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 已从“region”请求属性“oneOf”列表中删除“ApiStreamsAzureRegionView”
  • 已从响应的“dataProcessRegion/ 地区”响应属性“oneOf”列表中删除“ApiStreamsAzureRegionView”
  • 从“dataProcessRegion/ 地区/”响应属性中删除了“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS”枚举值
  • 删除了请求属性“地区 /”的枚举值“DUBLIN_IRL、FRANKFURT_DEU、LONDON_GBR、MUMBAI_IND、OREGON_USA、SAOPAULO_BRA、SINGAPORE_SGP、SYDNEY_AUS”

2024 年 4 月 20 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 添加了新的可选“查询”请求参数“itemsPerPage”
  • 添加了新的可选“查询”请求参数“pageNum”

2024 年 4 月 19 日发布

POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 请求属性“bucketName、iamRoleId、prefixPath”变为必填项

2024 年 4 月 18 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 将“FederationOidcWorkloadIdentityProvider”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“results/items/authorizationType、results/items/idpType”
  • 从响应中删除了可选属性“results/items/audienceClaim”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 将“FederationOidcWorkloadIdentityProviderUpdate”添加到请求正文“oneOf”列表中
  • 将“FederationOidcWorkloadIdentityProvider”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/authorizationType、/idpType、authorizationType、idpType”
  • 从响应中删除了可选属性“/audienceClaim,audienceClaim”
  • 删除了请求属性“/audienceClaim,audienceClaim”
  • 添加了新的可选请求属性“/authorizationType、/idpType、authorizationType、idpType”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 将“FederationOidcWorkloadIdentityProvider”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/authorizationType, /idpType, idpType”
  • 从响应中删除了可选属性“/audienceClaim”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 将“FederationOidcWorkloadIdentityProviderUpdate”添加到请求正文“oneOf”列表中
  • 将“FederationOidcWorkloadIdentityProvider”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“/authorizationType, /idpType, idpType”
  • 从响应中删除了可选属性“/audienceClaim”
  • 删除了请求属性“/audienceClaim”
  • 添加了新的可选请求属性“/authorizationType, /idpType, idpType”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“results/items/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到“/eventTypeName”请求属性“oneOf”列表
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到“/eventTypeName”请求属性“oneOf”列表
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“results/items/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“results/items/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到“/eventTypeName”请求属性“oneOf”列表
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“Cps 备份事件类型、资源事件类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表
  • 已从响应的“results/items/eventTypeName”响应属性“oneOf”列表中删除“Cps 备份事件类型”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
Updated
  • 在响应中添加了可选属性“selfManagedSharding”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 在响应中添加了可选属性“selfManagedSharding”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
Updated
  • 在响应中添加了可选属性“selfManagedSharding”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 在响应中添加了可选属性“selfManagedSharding”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
Updated
  • 在响应中添加了可选属性“selfManagedSharding”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 已将鉴别器添加到“results/items/dataProcessRegion”响应属性
  • 将新的“ Azure ”枚举值添加到“results/items/dataProcessRegion/cloudProvider”响应属性中
  • 从响应中删除了可选属性“results/items/dataProcessRegion/region”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 已将鉴别器添加到“dataProcessRegion”请求属性
  • 已将鉴别器添加到“dataProcessRegion”响应属性
  • 已将新的“ Azure ”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 已将新的“ Azure ”枚举值添加到请求属性“dataProcessRegion/cloudProvider”
  • 从响应中删除了可选属性“dataProcessRegion/ 地区”
  • 删除了请求属性“dataProcessRegion/region”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 已将鉴别器添加到“dataProcessRegion”响应属性
  • 已将新的“ Azure ”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 从响应中删除了可选属性“dataProcessRegion/ 地区”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 已将鉴别器添加到“dataProcessRegion”请求属性
  • 已将鉴别器添加到“dataProcessRegion”响应属性
  • 已将新的“ Azure ”枚举值添加到“dataProcessRegion/cloudProvider”响应属性中
  • 已将新的“ Azure ”枚举值添加到请求属性“dataProcessRegion/cloudProvider”
  • 从响应中删除了可选属性“dataProcessRegion/ 地区”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restoreJobs
Updated
  • 添加了API标签“Legacy Backup”（传统备份）
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 已将新的 'CREATE_STREAM_PROCESSOR、DROP_STREAM_PROCESSOR、GET_STREAM_PROCESSOR、LIST_CONNECTIONS、LIST_STREAM_PROCESSORS、PROCESS_STREAM_PROCESSOR、SAMPLE_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STREAM_PROCESSORS' 的新值添加到 theaction/site/stats'um response/site 中
POST /api/atlas/v2/groups/{groupId}/customDBRoles/roles
Updated
  • 已将新的 'CREATE_STREAM_PROCESSOR、DROP_STREAM_PROCESSOR、GET_STREAM_PROCESSOR、LIST_CONNECTIONS、LIST_STREAM_PROCESSORS、PROCESS_STREAM_PROCESSOR、SAMPLE_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STREAM_PROCESSOR_S' 值添加到属性的actions/ms 枚举中
  • 已将新的 'CREATE_STREAM_PROCESSOR、DROP_STREAM_PROCESSOR、GET_STREAM_PROCESSOR、LIST_CONNECTIONS、LIST_STREAM_PROCESSORS、PROCESS_STREAM_PROCESSOR、SAMPLE_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STREAM_PROCESSORS' 添加到请求 'action' 操作的 STAT/Site 属性枚举值
GET /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 已将新的 'CREATE_STREAM_PROCESSOR、DROP_STREAM_PROCESSOR、GET_STREAM_PROCESSOR、LIST_CONNECTIONS、LIST_STREAM_PROCESSORS、PROCESS_STREAM_PROCESSOR、SAMPLE_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STREAM_PROCESSOR_S' 值添加到属性的actions/ms 枚举中
PATCH /api/atlas/v2/groups/{groupId}/customDBRoles/roles/{roleName}
Updated
  • 已将新的 'CREATE_STREAM_PROCESSOR、DROP_STREAM_PROCESSOR、GET_STREAM_PROCESSOR、LIST_CONNECTIONS、LIST_STREAM_PROCESSORS、PROCESS_STREAM_PROCESSOR、SAMPLE_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STREAM_PROCESSOR_S' 值添加到属性的actions/ms 枚举中
  • 已将新的 'CREATE_STREAM_PROCESSOR、DROP_STREAM_PROCESSOR、GET_STREAM_PROCESSOR、LIST_CONNECTIONS、LIST_STREAM_PROCESSORS、PROCESS_STREAM_PROCESSOR、SAMPLE_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、START_STREAM_PROCESSOR、STOP_STREAM_PROCESSOR、STREAM_PROCESSORS' 添加到请求 'action' 操作的 STAT/Site 属性枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 已将新的 'CPS_COPY_SNAPSHOT_FAILED、CPS_COPY_SNAPSHOT_STARTED、CPS_COPY_SNAPSHOT_SUCCESSFUL'枚举值添加到 'results/items/eventTypeName/oneOf[# 5 ]/' 响应属性
  • 将新的 'UPDATE_BUMPER_FILES'枚举值添加到 'results/items/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已将新的 'CPS_COPY_SNAPSHOT_FAILED、CPS_COPY_SNAPSHOT_STARTED、CPS_COPY_SNAPSHOT_SUCCESSFUL' 枚举值添加到 '/eventTypeName/oneOf[# 5 ]/' 响应属性
  • 已将新的 'UPDATE_BUMPER_FILES' 枚举值添加到 '/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将新的“SP 10 ”枚举值添加到“results/items/streamConfig/ 层级”响应属性中
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 已将新的“SP 10 ”枚举值添加到“streamConfig/ 层级”响应属性中
  • 已将新的“SP 10 ”枚举值添加到请求属性“streamConfig/tier”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 已将新的“SP 10 ”枚举值添加到“streamConfig/ 层级”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 已将新的“SP 10 ”枚举值添加到“streamConfig/ 层级”响应属性中
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将新的 'INVITED_TO_TEAM' 枚举值添加到 'results/items/eventTypeName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 已将新的 'INVITED_TO_TEAM'枚举值添加到 '/eventTypeName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP 10 ”、“ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP 50 ”、“ATLAS_AWS_STREAM_PROCESSING_VPC_PEERING”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • 在“results/items/lineItems/items/sku”响应属性中添加了新的“ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP 10 ”、“ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP 50 ”、“ATLAS_AWS_STREAM_PROCESSING_VPC_PEERING”枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • 在 'lineItems/items/sku' 响应属性中添加了新的 'ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP 10 、 ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP 50 、 ATLAS_AWS_STREAM_PROCESSING_VPC_PEERING'枚举值

2024 年 4 月 12 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
已交
  • 已添加端点
PUT /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/pinned
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/collStats/unpin
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/collStats/namespaces
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/{clusterView}/{databaseName}/{collectionName}/collStats/measurements
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/collStats/metrics
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/collStats/namespaces
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/{databaseName}/{collectionName}/collStats/measurements
已交
  • 已添加端点

2024 年 4 月 05 日发布

GET /api/atlas/v2/groups
Updated
  • “regionUsageRestrictions”响应的属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • 删除了“results/items/regionUsageRestrictions”响应属性中的“NONE”枚举值
POST /api/atlas/v2/groups
Updated
  • “regionUsageRestrictions”请求属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • “regionUsageRestrictions”响应的属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • 删除了“regionUsageRestrictions”响应属性中的“NONE”枚举值
  • 删除了请求属性“regionUsageRestrictions”的枚举值“NONE”
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • “regionUsageRestrictions”响应的属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • 删除了“regionUsageRestrictions”响应属性中的“NONE”枚举值
GET /api/atlas/v2/groups/{groupId}
Updated
  • “regionUsageRestrictions”响应的属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • 删除了“regionUsageRestrictions”响应属性中的“NONE”枚举值
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • “regionUsageRestrictions”响应的属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • 删除了“regionUsageRestrictions”响应属性中的“NONE”枚举值
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • “regionUsageRestrictions”响应的属性默认值从“NONE”更改为“COMMERCIAL_FEDRAMP_REGIONS_ONLY”
  • 删除了“results/items/regionUsageRestrictions”响应属性中的“NONE”枚举值

2024 年 3 月 29 日发布

GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S 70 _LOWCPU_NVME”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S 70 _LOWCPU_NVME”枚举值
  • 已将新的“S 70 _LOWCPU_NVME”枚举值添加到请求属性“specs/items/instanceSize”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S 70 _LOWCPU_NVME”枚举值
  • 已将新的“S 70 _LOWCPU_NVME”枚举值添加到请求属性“specs/items/instanceSize”

2024 年 3 月 28 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 在响应中添加了可选属性“results/items/audience”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 在响应中添加了可选属性“/audience,audience”
  • 添加了新的可选请求属性“/audience,audience”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 在响应中添加了可选属性“/audience”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 在响应中添加了可选属性“/audience”
  • 添加了新的可选请求属性“/audience”
GET /api/atlas/v2/groups/{groupId}/clusters/provider/regions
Updated
  • 将新的“GCP”枚举值添加到“results/items/ 提供商”响应属性中
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S 135 _LOWCPU_NVME”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S 135 _LOWCPU_NVME”枚举值
  • 已将新的“S 135 _LOWCPU_NVME”枚举值添加到请求属性“specs/items/instanceSize”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S 135 _LOWCPU_NVME”枚举值
  • 已将新的“S 135 _LOWCPU_NVME”枚举值添加到请求属性“specs/items/instanceSize”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到 'results/items/region' 响应属性
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到 '/region' 响应属性
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到请求属性 '/region'
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到 'results/items/region' 响应属性
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到 '/region' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到 '/region' 响应属性
  • 已将新的 'US_EAST_ 2 _EUAP' 枚举值添加到请求属性 '/region'
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 已将新的 'CLUSTER_INSTANCE_FAMILY_UPDATED' 枚举值添加到 'results/items/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 已将新的 'CLUSTER_INSTANCE_FAMILY_UPDATED' 枚举值添加到 '/eventTypeName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • Added the new 'ATLAS_AZURE_SEARCH_INSTANCE_S 100 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 110 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 130 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 135 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 20 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 30 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 40 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 40 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 50 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 50 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 60 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 60 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 70 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 80 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 80 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 90 _MEMORY_LOCALSSD' 'results/items/lineItems/items/sku' 响应属性的枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_AZURE_SEARCH_INSTANCE_S 100 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 110 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 130 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 135 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 20 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 30 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 40 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 40 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 50 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 50 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 60 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 60 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 70 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 80 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 80 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 90 _MEMORY_LOCALSSD' 'results/items/lineItems/items/sku' 响应属性的枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_AZURE_SEARCH_INSTANCE_S 100 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 110 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 130 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 135 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 20 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 30 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 40 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 40 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 50 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 50 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 60 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 60 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 70 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 80 _COMPUTE_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 80 _MEMORY_LOCALSSD, ATLAS_AZURE_SEARCH_INSTANCE_S 90 _MEMORY_LOCALSSD' “lineItems/items/sku”响应属性的枚举值

2024 年 3 月 7 日发布

GET /api/atlas/v2/groups
Updated
  • 响应属性 'results/items/tags/items/key, results/items/tags/items/value' 变为必填项
POST /api/atlas/v2/groups
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
GET /api/atlas/v2/groups/{groupId}
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 添加了新的可选请求属性“tags”
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 添加了状态为“204”的成功响应
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“AP1”枚举值添加到“results/items/notifications/items/datadogRegion”响应属性中
  • 在“results/items/eventTypeName”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“AP1”枚举值添加到“/notifications/items/datadogRegion”响应属性中
  • 在“/eventTypeName”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
  • 将新的“AP1”枚举值添加到请求属性“/notifications/items/datadogRegion”
  • 在请求属性“/eventTypeName”中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“AP1”枚举值添加到“/notifications/items/datadogRegion”响应属性中
  • 在“/eventTypeName”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“AP1”枚举值添加到“/notifications/items/datadogRegion”响应属性中
  • 在“/eventTypeName”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 将新的“AP1”枚举值添加到“/notifications/items/datadogRegion”响应属性中
  • 在“/eventTypeName”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
  • 将新的“AP1”枚举值添加到请求属性“/notifications/items/datadogRegion”
  • 在请求属性“/eventTypeName”中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在 'results/items/eventTypeName/oneOf[#3]/' 响应属性中添加了新的 'AWS_ENCRYPTION_KEY_INVALID、AZURE_ENCRYPTION_KEY_INVALID、GCP_ENCRYPTION_KEY_INVALID' 枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在 'results/items/eventTypeName/oneOf[#3]/' 响应属性中添加了新的 'AWS_ENCRYPTION_KEY_INVALID、AZURE_ENCRYPTION_KEY_INVALID、GCP_ENCRYPTION_KEY_INVALID' 枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/eventTypeName/oneOf[#3]/”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在“/eventTypeName/oneOf[#3]/”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
  • 在请求属性 '/eventTypeName/oneOf[#3]/' 中添加了新的 'AWS_ENCRYPTION_KEY_INVALID、AZURE_ENCRYPTION_KEY_INVALID、GCP_ENCRYPTION_KEY_INVALID' 枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的“AP1”枚举值添加到“results/items/notifications/items/datadogRegion”响应属性中
  • 在“results/items/eventTypeName”响应属性中添加了新的“AWS_ENCRYPTION_KEY_INVALID”、“AZURE_ENCRYPTION_KEY_INVALID”和“GCP_ENCRYPTION_KEY_INVALID”枚举值
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 添加了新的可选“查询”请求参数“overwriteBackupPolicies”
  • 添加了状态为“400”的不成功响应
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US' 枚举值
  • 响应属性 'results/items/tags/items/key, results/items/tags/items/value' 变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US' 枚举值
  • 已将新的枚举值“GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US”添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/”
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/regionName”响应属性中添加了新的“GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US”枚举值
  • 在请求属性“providerSettings/regionName”中添加了新的“GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US”枚举值
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgradeToServerless
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US' 枚举值
  • 响应属性“tags/items/key,tags/items/value”变为必填项
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US' 枚举值
  • 已将新的枚举值“GOV_CENTRAL_US、GOV_US_EAST_4、GOV_US_EAST_5、GOV_US_SOUTH_1、GOV_US_WEST_2、GOV_US_WEST_3、GOV_US_WEST_4、GOV_WESTERN_US”添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/”
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S120_LOWCPU_NVME、S130_LOWCPU_NVME、S140_LOWCPU_NVME”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S120_LOWCPU_NVME、S130_LOWCPU_NVME、S140_LOWCPU_NVME”枚举值
  • 在请求属性“specs/items/instanceSize”中添加了新的“S120_LOWCPU_NVME、S130_LOWCPU_NVME、S140_LOWCPU_NVME”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
Updated
  • 在“specs/items/instanceSize”响应属性中添加了新的“S120_LOWCPU_NVME、S130_LOWCPU_NVME、S140_LOWCPU_NVME”枚举值
  • 在请求属性“specs/items/instanceSize”中添加了新的“S120_LOWCPU_NVME、S130_LOWCPU_NVME、S140_LOWCPU_NVME”枚举值
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“加密事件类型、版本审核类型”添加到响应的“results/items/eventTypeName”响应属性“oneOf”列表中
  • 将“ServiceAccountGroupEvents”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 从响应的“results/items/eventTypeName”响应属性“oneOf”列表中删除了“加密事件类型、版本审核类型”
  • 已将新的 'STREAM_TENANT_AUDIT_LOGS_DELETED' 枚举值添加到 'results/items/eventTypeName' 响应属性
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 将“ServiceAccountGroupEvents”添加到响应的响应正文“oneOf”列表中
  • 将“加密事件类型、版本审核类型”添加到响应的“/eventTypeName”响应属性“oneOf”列表中
  • 已从响应的“/eventTypeName”响应属性“oneOf”列表中删除“加密事件类型、版本审核类型”
  • 已将新的“STREAM_TENANT_AUDIT_LOGS_DELETED”枚举值添加到“/eventTypeName”响应属性
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 请求可选属性“state”变为只读
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
Updated
  • 请求可选属性“state”变为只读
GET /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 响应属性 'results/items/tags/items/key, results/items/tags/items/value' 变为必填项
POST /api/atlas/v2/groups/{groupId}/serverless
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
GET /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
PATCH /api/atlas/v2/groups/{groupId}/serverless/{name}
Updated
  • 响应属性“tags/items/key,tags/items/value”变为必填项
  • 请求属性“tags/items/key,tags/items/value”变为必填项
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“[Sample]”鉴别器映射键添加到“results/items/connections/items/”响应属性
  • 将“StreamsSampleConnection”添加到响应的“results/items/connections/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 将“[Sample]”鉴别器映射键添加到“connections/items/”请求属性
  • 将“StreamsSampleConnection”添加到“connections/items/”请求属性“oneOf”列表
  • 将“[Sample]”鉴别器映射键添加到“connections/items/”响应属性
  • 将“StreamsSampleConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“[Sample]”鉴别器映射键添加到“connections/items/”响应属性
  • 将“StreamsSampleConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 将“[Sample]”鉴别器映射键添加到“connections/items/”响应属性
  • 将“StreamsSampleConnection”添加到响应的“connections/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/auditLogs
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“[Sample]”鉴别器映射键添加到“results/items/”响应属性
  • 将“StreamsSampleConnection”添加到响应的“results/items/”响应属性“oneOf”列表中
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 将“[Sample]”映射键添加到请求鉴别器
  • 将“StreamsSampleConnection”添加到请求正文“oneOf”列表
  • 已将“[Sample]”映射键添加到响应状态“200”的响应鉴别器
  • 将“StreamsSampleConnection”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 已将“[Sample]”映射键添加到响应状态“200”的响应鉴别器
  • 将“StreamsSampleConnection”添加到响应的响应正文“oneOf”列表中
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 将“[Sample]”映射键添加到请求鉴别器
  • 将“StreamsSampleConnection”添加到请求正文“oneOf”列表
  • 已将“[Sample]”映射键添加到响应状态“200”的响应鉴别器
  • 将“StreamsSampleConnection”添加到响应的响应正文“oneOf”列表中
POST /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}/accessList
Updated
  • 已将请求属性“/items/cidrBlock”的模式从“^((([0-9]{1,3}\.){3}[0-9]{1,3} })|([\:]{0,2}([0-9a-f]{1,4}\:){0,7}[0-9a-f]{1 ,4}[\:]{0,2}))((%2[fF]|\/)[0-9]{1,3})+$' to '^((( [0-9]{1,3}\.){3}[0-9]{1,3})|(:{0,2}([0-9a-f ]{1,4}:){0,7}[0-9a-f]{1,4}[:]{0,2}))((%2[fF] |/)[0-9]{1,3})+$'
  • 已将请求属性“/items/ipAddress”的模式从“^((([0-9]{1,3}\.){3}[0-9]{1,3} })|([\:]{0,2}([0-9a-f]{1,4}\:){0,7}[0-9a-f]{1 ,4}[\:]{0,2}))$' 改为 '^((25[0-5]|(2[0-4]|1\d|[1-9]|) \d)(\.(?!$)|$)){4}|([0-9a-f]{1,4}:){7}[0-9a-f] {1,4}$'
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 将“ServiceAccountOrgEvents”添加到响应的“results/items/”响应属性“oneOf”列表中
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 将“ServiceAccountOrgEvents”添加到响应的响应正文“oneOf”列表中
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 响应属性 'results/items/tags/items/key, results/items/tags/items/value' 变为必填项
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • Added the new 'ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_DIFFERENT_REGION, ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_INTERNET, ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_SAME_REGION, ATLAS_DATA_FEDERATION_GCP_DATA_SCANNED, ATLAS_NDS_GCP_DATA_LAKE_STORAGE, ATLAS_NDS_GCP_DATA_LAKE_STORAGE_ACCESS, ATLAS_NDS_GCP_OBJECT_STORAGE, ATLAS_NDS_GCP_OBJECT_STORAGE_ACCESS' 枚举 values to the 'results/items/lineItems/items/sku' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_DIFFERENT_REGION, ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_INTERNET, ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_SAME_REGION, ATLAS_DATA_FEDERATION_GCP_DATA_SCANNED, ATLAS_NDS_GCP_DATA_LAKE_STORAGE, ATLAS_NDS_GCP_DATA_LAKE_STORAGE_ACCESS, ATLAS_NDS_GCP_OBJECT_STORAGE, ATLAS_NDS_GCP_OBJECT_STORAGE_ACCESS' 枚举 values to the 'results/items/lineItems/items/sku' 响应属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_DIFFERENT_REGION, ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_INTERNET, ATLAS_DATA_FEDERATION_GCP_DATA_RETURNED_SAME_REGION, ATLAS_DATA_FEDERATION_GCP_DATA_SCANNED, ATLAS_NDS_GCP_DATA_LAKE_STORAGE, ATLAS_NDS_GCP_DATA_LAKE_STORAGE_ACCESS, ATLAS_NDS_GCP_OBJECT_STORAGE, ATLAS_NDS_GCP_OBJECT_STORAGE_ACCESS' 枚举 values to the 'lineItems/items/sku' 响应属性

2024 年 2 月 29 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • “mongoDBMajorVersion”响应的属性默认值从“6.0”更改为“7.0”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • “mongoDBMajorVersion”请求属性默认值从“6.0”更改为“7.0”
  • “mongoDBMajorVersion”响应的属性默认值从“6.0”更改为“7.0”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • “mongoDBMajorVersion”请求属性默认值从“6.0”更改为“7.0”
  • “mongoDBMajorVersion”响应的属性默认值从“6.0”更改为“7.0”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • “mongoDBMajorVersion”响应的属性默认值从“6.0”更改为“7.0”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • “mongoDBMajorVersion”请求属性默认值从“6.0”更改为“7.0”
  • “mongoDBMajorVersion”响应的属性默认值从“6.0”更改为“7.0”

2024 年 2 月 21 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在“results/items/oneOf[#/components/schemas/NDSAuditViewForNdsGroup]/eventTypeName”属性中添加了新的“集群、MATERIAL_CLUSTER_UPDATE_COMPLETED_INTERNAL”枚举值
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[#/components/schemas/NDSAuditViewForNdsGroup]/eventTypeName' 响应属性中添加了新的 'CLUSTER_UPDATE_STARTED_INTERNAL、MATERIAL_CLUSTER_UPDATE_COMPLETED_INTERNAL' 枚举值

2024 年 2 月 17 日发布

GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“STREAM_TENANT_AUDIT_LOGS”枚举值添加到“results/items/oneOf[#/components/schemas/NDSAuditViewForNdsGroup]/eventTypeName”响应属性中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[#/components/schemas/NDSAuditViewForNdsGroup]/eventTypeName' 响应属性中添加了新的 'STREAM_TENANT_AUDIT_LOGS' 枚举值

2024 年 2 月 15 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 添加了新的可选“查询”请求参数“idpType”
POST /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
已交
  • 已添加端点
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
已交
  • 已添加端点
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“identityProviderId”，minLength 从“20”减少到“0”
  • 已从“path”请求参数“identityProviderId”中删除模式“^([a-f0-9]{20})$”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 对于“path”请求参数“identityProviderId”，minLength 从“20”减少到“0”
  • 已从“path”请求参数“identityProviderId”中删除模式“^([a-f0-9]{20})$”
DELETE /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}/jwks
已交
  • 已添加端点
GET /api/atlas/v2/groups
Updated
  • 在响应中添加了可选属性“results/items/tags”
POST /api/atlas/v2/groups
Updated
  • 在响应中添加了可选属性“tags”
  • 添加了新的可选请求属性“tags”
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 在响应中添加了可选属性“tags”
GET /api/atlas/v2/groups/{groupId}
Updated
  • 在响应中添加了可选属性“tags”
PATCH /api/atlas/v2/groups/{groupId}
Updated
  • 在响应中添加了可选属性“tags”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 响应属性 'results/items/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications,Results/items/oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/ BillingThresholdAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas /DefaultAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/ schemas/HostMetricAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications,results/i tems/oneOf[#/components/schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, results/items/oneOf[#/components/schemas/ReplicaSetThresholdConfigViewForNdsGroup]/notifications, results/items/oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 成为必需
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 响应属性 '/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/BillingThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[# /components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/ notifications, /oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/HostMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components /schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ReplicaSetThresholdAlertConfig ViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 响应属性 '/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/BillingThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[# /components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/ notifications, /oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/HostMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components /schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ReplicaSetThresholdAlertConfig ViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 变为必填项
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 响应属性 '/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/BillingThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[# /components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/ notifications, /oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/HostMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components /schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ReplicaSetThresholdAlertConfig ViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 变为必填项
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 响应属性 '/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/BillingThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[# /components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/ notifications, /oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/HostMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components /schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ReplicaSetThresholdAlertConfig ViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 变为必填项
  • 请求属性 '/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/BillingThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[# /components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/ notifications, /oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/HostMetricAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components /schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, /oneOf[#/components/schemas/ReplicaSetThresholdAlertConfigV iewForNdsGroup]/notifications, /oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 变为必填项
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 响应属性 'results/items/oneOf[#/components/schemas/AppServiceAlertConfigViewForNdsGroup]/notifications,Results/items/oneOf[#/components/schemas/AppServiceMetricAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/ BillingThresholdAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/ClusterAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas /DefaultAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/EncryptionKeyAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/HostAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/ schemas/HostMetricAlertConfigViewForNdsGroup]/notifications,results/items/oneOf[#/components/schemas/NDSX509UserAuthenticationAlertConfigViewForNdsGroup]/notifications,results/i tems/oneOf[#/components/schemas/ReplicaSetAlertConfigViewForNdsGroup]/notifications, results/items/oneOf[#/components/schemas/ReplicaSetThresholdConfigViewForNdsGroup]/notifications, results/items/oneOf[#/components/schemas/ServerlessMetricAlertConfigViewForNdsGroup]/notifications' 成为必需
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在“scheduledPolicyItems/items/FrequencyType”响应属性中添加了新的“yearly”枚举值
  • 在“onDemandPolicyItem/retentionUnit”响应属性中添加了新的“years”枚举值
  • 在“scheduledPolicyItems/items/retentionUnit”响应属性中添加了新的“years”枚举值
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
Updated
  • 在“scheduledPolicyItems/items/FrequencyType”响应属性中添加了新的“yearly”枚举值
  • 在“onDemandPolicyItem/retentionUnit”响应属性中添加了新的“years”枚举值
  • 在“scheduledPolicyItems/items/retentionUnit”响应属性中添加了新的“years”枚举值
  • 在请求属性“scheduledPolicyItems/items/FrequencyType”中添加了新的“yearly”枚举值
  • 在请求属性“onDemandPolicyItem/retentionUnit”中添加了新的“years”枚举值
  • 已将新的 'years' 枚举值添加到请求属性 'scheduledPolicyItems/items/retentionUnit'
GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的“GOV_EASTERN_US”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_EASTERN_US' 枚举值
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/”响应属性中
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 将新的“GOV_EASTERN_US”枚举值添加到“providerSettings/oneOf[#/components/schemas/CloudGCPProviderSettings]/regionName”响应属性中
  • 在请求属性“providerSettings/oneOf[#/components/schemas/CloudGCPProviderSettings]/regionName”中添加了新的“GOV_EASTERN_US”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_EASTERN_US' 枚举值
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'GOV_EASTERN_US' 枚举值
  • 将新的 'GOV_EASTERN_US' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中
  • 将新的“GOV_EASTERN_US”枚举值添加到“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/”响应属性中
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 中添加了新的 'GOV_EASTERN_US' 枚举值
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 将新的“YEARLY”枚举值添加到“copySettings/items/frequencies/items/”响应属性中
  • 在“extraRetentionSettings/items/FrequencyType”响应属性中添加了新的“YEARLY”枚举值
  • 已将新的 'yearly' 枚举值添加到 'export/FrequencyType' 响应属性中
  • 将新的 'yearly' 枚举值添加到 'policies/items/policyItems/items/FrequencyType' 响应属性中
  • 在“policies/items/policyItems/items/retentionUnit”响应属性中添加了新的“years”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 将新的“YEARLY”枚举值添加到“copySettings/items/frequencies/items/”响应属性中
  • 在“extraRetentionSettings/items/FrequencyType”响应属性中添加了新的“YEARLY”枚举值
  • 已将新的 'yearly' 枚举值添加到 'export/FrequencyType' 响应属性中
  • 将新的 'yearly' 枚举值添加到 'policies/items/policyItems/items/FrequencyType' 响应属性中
  • 在“policies/items/policyItems/items/retentionUnit”响应属性中添加了新的“years”枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/schedule
Updated
  • 将新的“YEARLY”枚举值添加到“copySettings/items/frequencies/items/”响应属性中
  • 在“extraRetentionSettings/items/FrequencyType”响应属性中添加了新的“YEARLY”枚举值
  • 已将新的 'yearly' 枚举值添加到 'export/FrequencyType' 响应属性中
  • 将新的 'yearly' 枚举值添加到 'policies/items/policyItems/items/FrequencyType' 响应属性中
  • 在“policies/items/policyItems/items/retentionUnit”响应属性中添加了新的“years”枚举值
  • 已将新的“YEARLY”枚举值添加到请求属性“copySettings/items/frequencies/items/”
  • 在请求属性“extraRetentionSettings/items/FrequencyType”中添加了新的“YEARLY”枚举值
  • 已将新的“yearly”枚举值添加到请求属性“export/FrequencyType”
  • 已将新的 'yearly' 枚举值添加到请求属性 'policies/items/policyItems/items/FrequencyType'
  • 在请求属性“policies/items/policyItems/items/retentionUnit”中添加了新的“years”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 在“results/items/frequentType”响应属性中添加了新的“yearly”枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots
Updated
  • 已将新的 'yearly'（每年）枚举值添加到 'FrequencyType'（频率类型）响应属性中
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedCluster/{snapshotId}
Updated
  • 已将新的 'yearly'（每年）枚举值添加到 'FrequencyType'（频率类型）响应属性中
  • 在响应中添加了可选属性“configServerType”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/shardedClusters
Updated
  • 在“results/items/frequentType”响应属性中添加了新的“yearly”枚举值
  • 在响应中添加了可选属性“results/items/configServerType”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 已将新的 'yearly'（每年）枚举值添加到 'FrequencyType'（频率类型）响应属性中
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/backup/snapshots/{snapshotId}
Updated
  • 已将新的 'yearly'（每年）枚举值添加到 'FrequencyType'（频率类型）响应属性中
  • 已将新的“YEARS”枚举值添加到请求属性“retentionUnit”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在“results/items/oneOf[#/components/schemas/AzureCloudProviderContainer]/地区”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL”枚举值
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在 '/oneOf[#/components/schemas/AzureCloudProviderContainer]/地区' 响应属性中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/AzureCloudProviderContainer]/region' 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL' 枚举值
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 在“results/items/oneOf[#/components/schemas/AzureCloudProviderContainer]/地区”响应属性中添加了新的“ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL”枚举值
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[#/components/schemas/AzureCloudProviderContainer]/地区' 响应属性中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL' 枚举值
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[#/components/schemas/AzureCloudProviderContainer]/地区' 响应属性中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/AzureCloudProviderContainer]/region' 中添加了新的 'ISRAEL_CENTRAL、ITALY_NORTH、POLAND_CENTRAL' 枚举值
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSchedules
Updated
  • 将新的 'yearly' 枚举值添加到 '/items/FrequencyType' 响应属性
  • 已将新的 'years' 枚举值添加到 '/items/retentionUnit' 响应属性
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/availableSnapshots
Updated
  • 在“results/items/frequentType”响应属性中添加了新的“yearly”枚举值
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs
Updated
  • 将新的“YEARLY”枚举值添加到“results/items/backupFrequencyType”响应属性中
GET /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/runs/{pipelineRunId}
Updated
  • 已将新的“YEARLY”枚举值添加到“backupFrequencyType”响应属性中
POST /api/atlas/v2/groups/{groupId}/pipelines/{pipelineName}/trigger
Updated
  • 已将新的“YEARLY”枚举值添加到“backupFrequencyType”响应属性中
GET /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/serverless/{clusterName}/performanceAdvisor/autoIndexing
已交
  • 已添加端点
GET /api/atlas/v2/orgs/{orgId}/groups
Updated
  • 在响应中添加了可选属性“results/items/tags”
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • Added the new 'ATLAS_GCP_SEARCH_INSTANCE_S100_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S110_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S120_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S130_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S140_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S20_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S30_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S30_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S40_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S40_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S50_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S50_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S60_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S60_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S70_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S70_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S80_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S80_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S90_MEMORY_LOCALSSD' 枚举 values to the 'results/items /lineItems/items/sku' 属性
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_GCP_SEARCH_INSTANCE_S100_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S110_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S120_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S130_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S140_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S20_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S30_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S30_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S40_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S40_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S50_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S50_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S60_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S60_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S70_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S70_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S80_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S80_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S90_MEMORY_LOCALSSD' 枚举 values to the 'results/items /lineItems/items/sku' 属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_GCP_SEARCH_INSTANCE_S100_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S110_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S120_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S130_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S140_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S20_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S30_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S30_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S40_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S40_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S50_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S50_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S60_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S60_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S70_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S70_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S80_COMPUTE_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S80_MEMORY_LOCALSSD, ATLAS_GCP_SEARCH_INSTANCE_S90_MEMORY_LOCALSSD' enum values to the 'lineItems/items /sku' 响应属性
PATCH /api/atlas/v2/orgs/{orgId}/teams/{teamId}
Updated
  • 请求所需属性“名称”变为只写
GET /api/atlas/v2/unauth/controlPlaneIPAddresses
Updated
  • 添加了 Api 标签“Root”

2024 年 2 月 7 日发布

GET /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 在响应中添加了可选属性“numberOfDeferrals”
PATCH /api/atlas/v2/groups/{groupId}/maintenanceWindow
Updated
  • 请求属性“hourOfDay”变为可选

2024 年 2 月 6 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#1]/”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[#1]/”响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1, IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#1]/”
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#1]/”
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#1]/' 中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#1]/”
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#1]/”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/oneOf[#/components/schemas/AWSCloudProviderSettings]/regionName”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 在请求属性“providerSettings/oneOf[#/components/schemas/AWSCloudProviderSettings]/regionName”中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1, IL_CENTRAL_1' 枚举值
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#1]/”响应属性中
  • 在 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#1]/' 响应属性中添加了新的 'CA_WEST_1, IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#1]/”
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#1]/”
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#1]/' 中添加了新的 'CA_WEST_1、IL_CENTRAL_1' 枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#1]/”
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“replicationSpecs/items/regionConfigs/items/regionName/oneOf[#1]/”
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“results/items/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”响应属性中
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在“/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“results/items/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”响应属性中
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在“/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在“/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“/oneOf[#/components/schemas/AWSCloudProviderContainer]/regionName”
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“/items/storage/stores/items/oneOf[#/components/schemas/DataLakeDLSAWSStore]/地区”响应属性
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到“/items/storage/stores/items/oneOf[#/components/schemas/DataLakeS3StoreSettings]/地区”响应属性
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 在“storage/stores/items/oneOf[#/components/schemas/DataLakeDLSAWSStore]/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 在“storage/stores/items/oneOf[#/components/schemas/DataLakeS3StoreSettings]/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“storage/stores/items/oneOf[#/components/schemas/DataLakeDLSAWSStore]/地区”
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“storage/stores/items/oneOf[#/components/schemas/DataLakeS3StoreSettings]/地区
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在“storage/stores/items/oneOf[#/components/schemas/DataLakeDLSAWSStore]/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 在“storage/stores/items/oneOf[#/components/schemas/DataLakeS3StoreSettings]/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在“storage/stores/items/oneOf[#/components/schemas/DataLakeDLSAWSStore]/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 在“storage/stores/items/oneOf[#/components/schemas/DataLakeS3StoreSettings]/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“storage/stores/items/oneOf[#/components/schemas/DataLakeDLSAWSStore]/地区”
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“storage/stores/items/oneOf[#/components/schemas/DataLakeS3StoreSettings]/地区
GET /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“awsKms/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
PATCH /api/atlas/v2/groups/{groupId}/encryptionAtRest
Updated
  • 在“awsKms/地区”响应属性中添加了新的“CA_WEST_1、IL_CENTRAL_1”枚举值
  • 已将新的“CA_WEST_1、IL_CENTRAL_1”枚举值添加到请求属性“awsKms/地区”

2024 年 1 月 26 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性
  • 将新的“EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 将新的“EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2”枚举值添加到“results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/”响应属性中
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/'
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在“providerSettings/oneOf[#/components/schemas/CloudGCPProviderSettings]/regionName”响应属性中添加了新的“EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2”枚举值
  • 在请求属性“providerSettings/oneOf[#/components/schemas/CloudGCPProviderSettings]/regionName”中添加了新的“EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2”枚举值
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/' 响应属性
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 响应属性
  • 将新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值添加到请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AWSRegionConfig]/regionName/oneOf[#3]/'
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/AzureRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/GCPRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/oneOf[#/components/schemas/TenantRegionConfig]/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[#3]/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
GET /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在 'results/items/oneOf[#/components/schemas/GCPCloudProviderContainer]/地区/items/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
POST /api/atlas/v2/groups/{groupId}/containers
Updated
  • 在 '/oneOf[#/components/schemas/GCPCloudProviderContainer]/regions/items/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/GCPCloudProviderContainer]/regions/items/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
GET /api/atlas/v2/groups/{groupId}/containers/all
Updated
  • 在 'results/items/oneOf[#/components/schemas/GCPCloudProviderContainer]/地区/items/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
GET /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[#/components/schemas/GCPCloudProviderContainer]/regions/items/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
PATCH /api/atlas/v2/groups/{groupId}/containers/{containerId}
Updated
  • 在 '/oneOf[#/components/schemas/GCPCloudProviderContainer]/regions/items/' 响应属性中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/GCPCloudProviderContainer]/regions/items/' 中添加了新的 'EUROPE_WEST_10, MIDDLE_EAST_CENTRAL_2' 枚举值

2024 年 1 月 25 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 从“results/items/”响应属性中删除了鉴别器
  • 将“FederationSamlIdentityProvider, FederationOidcWorkforceIdentityProvider”添加到响应的“results/items/”响应属性“oneOf”列表中
  • 在响应中添加了可选属性“results/items/createdAt、results/items/updatedAt”
  • 从响应中删除了可选属性“results/items/associedDomains”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 删除了响应状态“200”的响应鉴别器
  • 将“FederationSamlIdentityProvider, FederationOidcWorkforceIdentityProvider”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“createdAt、updatedAt”
  • 从响应中删除了可选属性“关联域”
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
Updated
  • 删除了请求鉴别器
  • 将“FederationSamlIdentityProviderUpdate, FederationOidcWorkforceIdentityProviderUpdate”添加到请求正文“oneOf”列表
  • 删除了响应状态“200”的响应鉴别器
  • 将“FederationSamlIdentityProvider, FederationOidcWorkforceIdentityProvider”添加到响应的响应正文“oneOf”列表中
  • 在响应中添加了可选属性“createdAt、updatedAt”
  • 从响应中删除了可选属性“关联域”
  • 删除了请求属性“关联域”
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将新的“CPS_AUTO_EXPORT_FAILED”枚举值添加到“results/items/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/”响应属性中
  • 将新的“CPS_PREV_SNAPSHOT_OLD”枚举值添加到“results/items/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName”响应属性中
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 在 '/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/' 响应属性中添加了新的 'CPS_AUTO_EXPORT_FAILED' 枚举值
  • 将新的“CPS_PREV_SNAPSHOT_OLD”枚举值添加到“/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName”响应属性中
  • 在请求属性 '/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/' 中添加了新的 'CPS_AUTO_EXPORT_FAILED' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName' 中添加了新的 'CPS_PREV_SNAPSHOT_OLD' 枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/' 响应属性中添加了新的 'CPS_AUTO_EXPORT_FAILED' 枚举值
  • 将新的“CPS_PREV_SNAPSHOT_OLD”枚举值添加到“/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName”响应属性中
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/' 响应属性中添加了新的 'CPS_AUTO_EXPORT_FAILED' 枚举值
  • 将新的“CPS_PREV_SNAPSHOT_OLD”枚举值添加到“/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName”响应属性中
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在 '/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/' 响应属性中添加了新的 'CPS_AUTO_EXPORT_FAILED' 枚举值
  • 将新的“CPS_PREV_SNAPSHOT_OLD”枚举值添加到“/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName”响应属性中
  • 在请求属性 '/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/' 中添加了新的 'CPS_AUTO_EXPORT_FAILED' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName' 中添加了新的 'CPS_PREV_SNAPSHOT_OLD' 枚举值
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 在“results/items/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName/oneOf[#2]/”响应属性中添加了新的“CPS_AUTO_EXPORT_FAILED、CPS_PREV_SNAPSHOT_OLD”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 在“results/items/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName/oneOf[#2]/”响应属性中添加了新的“CPS_AUTO_EXPORT_FAILED、CPS_PREV_SNAPSHOT_OLD”枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在 '/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName/oneOf[#2]/' 响应属性中添加了新的 'CPS_AUTO_EXPORT_FAILED、CPS_PREV_SNAPSHOT_OLD' 枚举值
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在 '/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName/oneOf[#2]/' 响应属性中添加了新的 'CPS_AUTO_EXPORT_FAILED、CPS_PREV_SNAPSHOT_OLD' 枚举值
  • 在请求属性 '/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName/oneOf[#2]/' 中添加了新的 'CPS_AUTO_EXPORT_FAILED、CPS_PREV_SNAPSHOT_OLD' 枚举值
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将新的“CPS_AUTO_EXPORT_FAILED”枚举值添加到“results/items/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName/oneOf[#2]/”响应属性中
  • 将新的“CPS_PREV_SNAPSHOT_OLD”枚举值添加到“results/items/oneOf[#/components/schemas/CpsBackupThresholdAlertConfigViewForNdsGroup]/eventTypeName”响应属性中
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 在响应中添加了可选属性“results/items/dataProcessRegion”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 请求可选属性“collectionType”变为只写
  • 请求可选属性“dataProcessRegion”变为只写
  • 请求可选属性“partitionFields”变为只写
  • 请求必需属性“collName”变为只写
  • 请求必需属性“dbName”变为只写
  • 在响应中添加了可选属性“dataProcessRegion”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 在响应中添加了可选属性“dataProcessRegion”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 在响应中添加了可选属性“dataProcessRegion”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 在响应的“results/items/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“Cps 备份事件类型”、“磁盘备份事件类型”
  • 从响应的“results/items/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“Cps 备份事件类型”、“磁盘备份事件类型”
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在响应的“/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“Cps 备份事件类型”、“磁盘备份事件类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“Cps 备份事件类型”、“磁盘备份事件类型”
POST /api/atlas/v2/groups/{groupId}/liveMigrations
Updated
  • 添加了新的可选请求属性“sharding”
POST /api/atlas/v2/groups/{groupId}/liveMigrations/validate
Updated
  • 添加了新的可选请求属性“sharding”
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/streamConfig”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“streamConfig”
  • 添加了新的可选请求属性“streamConfig”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“streamConfig”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“streamConfig”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[#/components/schemas/BillingEventViewForOrg]/eventTypeName”响应属性中添加了新的“信用、PENDING_DEAL_ACTIVATION_ADDED、PENDING_DEAL_ACTIVATION_CANCELED、PENDING_DEAL_ACTIVATION_FAILED、PENDING_DEAL_APPLIED”枚举值
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在 '/oneOf[#/components/schemas/BillingEventViewForOrg]/eventTypeName' 响应属性中添加了新的 '信用、PENDING_DEAL_ACTIVATION_ADDED、PENDING_DEAL_ACTIVATION_CANCELED、PENDING_DEAL_ACTIVATION_FAILED、PENDING_DEAL_APPLIED' 枚举值
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}/csv
Updated
  • 添加了状态为“404”的不成功响应

2024 年 1 月 19 日发布

POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/index
Updated
  • 在请求属性“collation/locale”中添加了新的“simple”枚举值

2024 年 1 月 18 日发布

GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 向响应添加了可选属性“links、results、totalCount”
GET /api/atlas/v2/groups/{groupId}/ipAddresses
Updated
  • 在响应中添加了可选属性“groupId, services”

2024 年 1 月 17 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“results/items/diskWarmingMode”
POST /api/atlas/v2/groups/{groupId}/clusters
Updated
  • 在响应中添加了可选属性“diskWarmingMode”
  • 添加了新的可选请求属性“diskWarmingMode”
POST /api/atlas/v2/groups/{groupId}/clusters/tenantUpgrade
Updated
  • 在响应中添加了可选属性“diskWarmingMode”
  • 添加了新的可选请求属性“diskWarmingMode”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“diskWarmingMode”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
Updated
  • 在响应中添加了可选属性“diskWarmingMode”
  • 添加了新的可选请求属性“diskWarmingMode”
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将新的“SERVERLESS_MTM_DRAIN_STOPPED”枚举值添加到“results/items/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName/oneOf[#18]/”响应属性中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在 '/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName/oneOf[#18]/' 响应属性中添加了新的 'SERVERLESS_MTM_DRAIN_STOPPED' 枚举值

2024 年 1 月 10 日发布

GET /api/atlas/v2
Updated
  • 端点方案安全“DigestAuth”已添加到 API
  • 已将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'apiKey/角色/items/roleName' 响应属性
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs
Updated
  • 端点方案安全“DigestAuth”已添加到 API
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '/items/roleMappings/items/roleAssignments/items/role' 响应属性
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'roleMappings/items/roleAssignments/items/role' 响应属性
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'roleMappings/items/roleAssignments/items/role' 响应属性
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roleMappings/items/roleAssignments/items/role”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/roleAssignments/items/role' 响应属性
POST /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“roleAssignments/items/角色”响应属性中
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roleAssignments/items/role”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“roleAssignments/items/角色”响应属性中
PUT /api/atlas/v2/federationSettings/{federationSettingsId}/connectedOrgConfigs/{orgId}/roleMappings/{id}
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“roleAssignments/items/角色”响应属性中
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roleAssignments/items/role”
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders
Updated
  • 已从响应的“/items/”响应属性“oneOf”列表中删除“FederationSamlIdentityProvider, FederationOidcIdentityProvider”
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '/items/关联Orgs/items/roleMappings/items/roleAssignments/items/角色' 响应属性
GET /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
已交
  • 为响应状态“200”添加了响应鉴别器
  • 从响应中删除了可选属性“acsUrl、audienceUri、pemFileInfo、requestBinding、responseSignatureAlgorithm、ssoDebugEnabled、ssoUrl、status”
  • 添加了状态为“403”的不成功响应
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“关联Orgs/items/roleMappings/items/roleAssignments/items/role”响应属性中
  • 从响应中删除了可选属性“pemFileInfo/certificates/items/content”
  • 2023 年 11 月 15 日添加了新资源。 资源版本 2023-02-01 已弃用，并标记为删除日期：2025 年 1 月 1 日
PATCH /api/atlas/v2/federationSettings/{federationSettingsId}/identityProviders/{identityProviderId}
已交
  • 添加了请求鉴别器
  • 为响应状态“200”添加了响应鉴别器
  • 从响应中删除了可选属性“acsUrl、audienceUri、pemFileInfo、requestBinding、responseSignatureAlgorithm、ssoDebugEnabled、ssoUrl、status”
  • 删除了请求属性“slug”
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“关联Orgs/items/roleMappings/items/roleAssignments/items/role”响应属性中
  • 从响应中删除了可选属性“pemFileInfo/certificates/items/content”
  • 2023 年 11 月 15 日添加了新资源。 资源版本 2023-02-01 已弃用，并标记为删除日期：2025 年 1 月 1 日
GET /api/atlas/v2/groups
Updated
  • 端点方案安全“DigestAuth”已添加到 API
GET /api/atlas/v2/groups/byName/{groupName}
Updated
  • 端点方案安全“DigestAuth”已添加到 API
POST /api/atlas/v2/groups/{groupId}/access
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“groupRoleAssignments/items/groupRole”响应属性中
GET /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 将“群组事件类型、NDS 审核类型”添加到响应的“results/items/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的“results/items/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
POST /api/atlas/v2/groups/{groupId}/alertConfigs
Updated
  • 从“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”请求属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
  • 将“群组事件类型、NDS 审核类型”添加到“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”请求属性“oneOf”列表
  • 在响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、NDS 审核类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、NDS 审核类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
PATCH /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 在响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、NDS 审核类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
PUT /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}
Updated
  • 从“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”请求属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
  • 将“群组事件类型、NDS 审核类型”添加到“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”请求属性“oneOf”列表
  • 在响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、NDS 审核类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
GET /api/atlas/v2/groups/{groupId}/alertConfigs/{alertConfigId}/alerts
Updated
  • 将“群组事件类型、NDS 审核类型”添加到响应的“results/items/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的“results/items/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
GET /api/atlas/v2/groups/{groupId}/alerts
Updated
  • 将“群组事件类型、NDS 审核类型”添加到响应的“results/items/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的“results/items/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 在响应的“/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、NDS 审核类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
PATCH /api/atlas/v2/groups/{groupId}/alerts/{alertId}
Updated
  • 从“/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”请求属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
  • 将“群组事件类型、NDS 审核类型”添加到“/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”请求属性“oneOf”列表
  • 在响应的“/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、NDS 审核类型”
  • 从响应的“/oneOf[#/components/schemas/DefaultAlertViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
GET /api/atlas/v2/groups/{groupId}/alerts/{alertId}/alertConfigs
Updated
  • 将“群组事件类型、NDS 审核类型”添加到响应的“results/items/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的“results/items/oneOf[#/components/schemas/DefaultAlertConfigViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型、NDS 审核类型”
GET /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/角色/items/roleName' 响应属性
POST /api/atlas/v2/groups/{groupId}/apiKeys
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
PATCH /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“roles/items/”
POST /api/atlas/v2/groups/{groupId}/apiKeys/{apiUserId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
  • 已将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到请求属性 '/items/roles/items/'
GET /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
已交
  • 响应属性“authorizedUserFirstName、authorizedUserLastName”变为必填项
  • 添加了新的“0.00” “onDemandPolicyItem/FrequencyInterval”响应属性的枚举值
  • 2023 年 11 月 15 日添加了新资源。 资源版本 2023-02-01 已弃用，并标记为删除日期：2024 年 10 月 1 日
PUT /api/atlas/v2/groups/{groupId}/backupCompliancePolicy
已交
  • 响应属性“authorizedUserFirstName、authorizedUserLastName”变为必填项
  • 请求属性“authorizedUserFirstName、authorizedUserLastName”变为必填项
  • 添加了新的“0.00” “onDemandPolicyItem/FrequencyInterval”响应属性的枚举值
  • 添加了新的“0.00” 请求属性“onDemandPolicyItem/FrequencyInterval”的枚举值
  • 2023 年 11 月 15 日添加了新资源。 资源版本 2023-02-01 已弃用，并标记为删除日期：2024 年 10 月 1 日
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes
Updated
  • 添加了请求鉴别器
  • 为响应状态“200”添加了响应鉴别器
  • 在响应中添加了可选属性“类型”
  • 从响应中删除了可选属性“分析器、分析器、mappings、searchAnalyzer、synonyms”
  • 删除了请求属性“analyzer、analyzers、mappings、searchAnalyzer、synonyms”
  • 添加了新的可选请求属性“type”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{databaseName}/{collectionName}
Updated
  • 已将鉴别器添加到 '/items/' 响应属性
  • 在响应中添加了可选属性“/items/type”
  • 从响应中删除了可选属性“/items/分析器、/items/分析器、/items/mappings、/items/searchAnalyzer、/items/synonyms”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 为响应状态“200”添加了响应鉴别器
  • 在响应中添加了可选属性“类型”
  • 从响应中删除了可选属性“分析器、分析器、mappings、searchAnalyzer、synonyms”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/fts/indexes/{indexId}
Updated
  • 添加了请求鉴别器
  • 为响应状态“200”添加了响应鉴别器
  • 在响应中添加了可选属性“类型”
  • 从响应中删除了可选属性“分析器、分析器、mappings、searchAnalyzer、synonyms”
  • 删除了请求属性“analyzer、analyzers、mappings、searchAnalyzer、synonyms”
  • 添加了新的可选请求属性“type”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 从响应中删除了可选属性“results/items/dataProcessRegion”
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives
Updated
  • 从响应中删除了可选属性“dataProcessRegion”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 从响应中删除了可选属性“dataProcessRegion”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/onlineArchives/{archiveId}
Updated
  • 请求可选属性“collName”变为只读
  • 请求可选属性“collectionType”变为只读
  • 请求可选属性“dbName”变为只读
  • 请求可选属性“partitionFields”变为只读
  • 从响应中删除了可选属性“dataProcessRegion”
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“queryStatsLogVerbosity”
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/processArgs
Updated
  • 在响应中添加了可选属性“queryStatsLogVerbosity”
  • 添加了新的可选请求属性“queryStatsLogVerbosity”
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/search/deployment
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 在响应中添加了可选属性“/items/privateEndpointHostnames”
POST /api/atlas/v2/groups/{groupId}/dataFederation
Updated
  • 在响应中添加了可选属性“privateEndpointHostnames”
GET /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在响应中添加了可选属性“privateEndpointHostnames”
PATCH /api/atlas/v2/groups/{groupId}/dataFederation/{tenantName}
Updated
  • 在响应中添加了可选属性“privateEndpointHostnames”
GET /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 将新的“STREAM”枚举值添加到“results/items/scopes/items/type”响应属性中
  • 将新的“USER”枚举值添加到“results/items/oidcAuthType”响应属性中
POST /api/atlas/v2/groups/{groupId}/databaseUsers
Updated
  • 添加了状态为“201”的成功响应
  • 将新的“STREAM”枚举值添加到请求属性“scopes/items/type”
  • 已将新的“USER”枚举值添加到请求属性“oidcAuthType”中
GET /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 在“scopes/items/type”响应属性中添加了新的“STREAM”枚举值
  • 在“oidcAuthType”响应属性中添加了新的“USER”枚举值
PATCH /api/atlas/v2/groups/{groupId}/databaseUsers/{databaseName}/{username}
Updated
  • 在“scopes/items/type”响应属性中添加了新的“STREAM”枚举值
  • 在“oidcAuthType”响应属性中添加了新的“USER”枚举值
  • 将新的“STREAM”枚举值添加到请求属性“scopes/items/type”
  • 已将新的“USER”枚举值添加到请求属性“oidcAuthType”中
POST /api/atlas/v2/groups/{groupId}/databaseUsers/{username}/certs
Updated
  • 添加了状态为“201”的成功响应
GET /api/atlas/v2/groups/{groupId}/events
Updated
  • 将“群组事件类型、主动操作事件类型”添加到响应的“results/items/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中
  • 从响应的“results/items/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中删除了“群组事件类型”
  • Added the new '集群, REGIONALIZED_PRIVATE_ENDPOINT_MODE_DISABLED, REGIONALIZED_PRIVATE_ENDPOINT_MODE_ENABLED, STREAMS_AUDIT_LOG_CONFIGURATION_UPDATED, STREAM_TENANT_CONNECTIONS_LISTED, STREAM_TENANT_CONNECTION_CREATED, STREAM_TENANT_CONNECTION_DELETED, STREAM_TENANT_CONNECTION_UPDATED, STREAM_TENANT_CONNECTION_VIEWED, STREAM_TENANT_CREATED, STREAM_TENANT_DELETED, STREAM_TENANT_UPDATED' 枚举 values to the 'results/items/oneOf[#/components/schemas/NDSAuditViewForNdsGroup]/eventTypeName'响应属性
  • 将新的“FTS_INDEX_CLEANED_UP”枚举值添加到“results/items/oneOf[#/components/schemas/FTSIndexAuditView]/eventTypeName”响应属性中
GET /api/atlas/v2/groups/{groupId}/events/{eventId}
Updated
  • 在响应的“/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName”响应属性“oneOf”列表中添加了“群组事件类型、主动操作事件类型”
  • 已从响应的 '/oneOf[#/components/schemas/DefaultEventViewForNdsGroup]/eventTypeName' 属性 'oneOf' 列表中删除 'Group Event Types'
  • Added the new '集群, REGIONALIZED_PRIVATE_ENDPOINT_MODE_DISABLED, REGIONALIZED_PRIVATE_ENDPOINT_MODE_ENABLED, STREAMS_AUDIT_LOG_CONFIGURATION_UPDATED, STREAM_TENANT_CONNECTIONS_LISTED, STREAM_TENANT_CONNECTION_CREATED, STREAM_TENANT_CONNECTION_DELETED, STREAM_TENANT_CONNECTION_UPDATED, STREAM_TENANT_CONNECTION_VIEWED, STREAM_TENANT_CREATED, STREAM_TENANT_DELETED, STREAM_TENANT_UPDATED' 枚举 values to the '/oneOf[#/components/schemas/NDSAuditViewForNdsGroup]/eventTypeName' 属性 response
  • 在 '/oneOf[#/components/schemas/FTSIndexAuditView]/eventTypeName' 响应属性中添加了新的 'FTS_INDEX_CLEANED_UP' 枚举值
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics
Updated
  • 在“hardwareMetrics/items/metricName”响应属性中添加了新的“PAGE_FAULTS”枚举值
  • 在“indexMetrics/items/metricName”响应属性中添加了新的“PAGE_FAULTS”枚举值
  • 在“statusMetrics/items/metricName”响应属性中添加了新的“PAGE_FAULTS”枚举值
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/measurements
Updated
  • 在“indexStatsMeasurements/items/units”响应属性中添加了新的“MICROSECONDS”枚举值
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/indexes/{databaseName}/{collectionName}/{indexName}/measurements
Updated
  • 在“indexStatsMeasurements/items/units”响应属性中添加了新的“MICROSECONDS”枚举值
GET /api/atlas/v2/groups/{groupId}/hosts/{processId}/fts/metrics/measurements
Updated
  • 在“hardwareMeasurements/items/units”响应属性中添加了新的“MICROSECONDS”枚举值
  • 将新的“MICROSECONDS”枚举值添加到“statusMeasurements/items/units”响应属性中
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/databases/{databaseName}/measurements
Updated
  • 端点方案安全“DigestAuth”已添加到 API
  • 在“measurements/items/units”响应属性中添加了新的“MICROSECONDS”枚举值
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/disks/{partitionName}/measurements
Updated
  • 在“measurements/items/units”响应属性中添加了新的“MICROSECONDS”枚举值
GET /api/atlas/v2/groups/{groupId}/processes/{processId}/measurements
Updated
  • 在“measurements/items/units”响应属性中添加了新的“MICROSECONDS”枚举值
DELETE /api/atlas/v2/groups/{groupId}/pushBasedLogExport
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/pushBasedLogExport
已交
  • 已添加端点
PATCH /api/atlas/v2/groups/{groupId}/pushBasedLogExport
已交
  • 已添加端点
POST /api/atlas/v2/groups/{groupId}/pushBasedLogExport
已交
  • 已添加端点
GET /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“results/items/connections/items/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute”
POST /api/atlas/v2/groups/{groupId}/streams
Updated
  • 在响应中添加了可选属性“connections/items/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute”
  • 添加了新的可选请求属性 'connections/items/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute”
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}
Updated
  • 在响应中添加了可选属性“connections/items/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute”
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性“results/items/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute”
POST /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections
Updated
  • 在响应中添加了可选属性 '/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute'
  • 添加了新的可选请求属性 '/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute'
GET /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性 '/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute'
PATCH /api/atlas/v2/groups/{groupId}/streams/{tenantName}/connections/{connectionName}
Updated
  • 在响应中添加了可选属性 '/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute'
  • 添加了新的可选请求属性 '/oneOf[#/components/schemas/StreamsClusterConnection]/dbRoleToExecute'
GET /api/atlas/v2/groups/{groupId}/users
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/角色/items/roleName' 响应属性
PUT /api/atlas/v2/groups/{groupId}/users/{userId}/roles
Updated
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“groupRoles/items/”响应属性中
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“groupRoles/items/”
POST /api/atlas/v2/orgs
Updated
  • 已将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'apiKey/角色/items/roleName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/角色/items/roleName' 响应属性
POST /api/atlas/v2/orgs/{orgId}/apiKeys
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
PATCH /api/atlas/v2/orgs/{orgId}/apiKeys/{apiUserId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
POST /api/atlas/v2/orgs/{orgId}/billing/costExplorer/usage
Updated
  • 将新的“Atlas Stream Processing”枚举值添加到请求属性“services/items/”
GET /api/atlas/v2/orgs/{orgId}/events
Updated
  • 在“results/items/oneOf[#/components/schemas/BillingEventViewForOrg]/eventTypeName”响应属性中添加了新的“GRACE_PERIOD_ACTIVATED”、“GRACE_PERIOD_NO_LONGER_IN_EFFECT”、“ORG_UNLINK_CANCELLED”、“ORG_UNLINK_REQUESTED”枚举值
  • 将新的“ORG_SUSPENSION_DATE_CHANGED”枚举值添加到“results/items/oneOf[#/components/schemas/OrgEventViewForOrg]/eventTypeName”响应属性中
GET /api/atlas/v2/orgs/{orgId}/events/{eventId}
Updated
  • 在 '/oneOf[#/components/schemas/BillingEventViewForOrg]/eventTypeName' 响应属性中添加了新的 'GRACE_PERIOD_ACTIVATED、GRACE_PERIOD_NO_LONGER_IN_EFFECT、ORG_UNLINK_CANCELLED、ORG_UNLINK_REQUESTED' 枚举值
  • 将新的“ORG_SUSPENSION_DATE_CHANGED”枚举值添加到“/oneOf[#/components/schemas/OrgEventViewForOrg]/eventTypeName”响应属性中
GET /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '/items/groupRoleAssignments/items/groupRole' 响应属性
PATCH /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“groupRoleAssignments/items/groupRole”响应属性中
POST /api/atlas/v2/orgs/{orgId}/invites
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“groupRoleAssignments/items/groupRole”响应属性中
GET /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“groupRoleAssignments/items/groupRole”响应属性中
PATCH /api/atlas/v2/orgs/{orgId}/invites/{invitationId}
Updated
  • 将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到“groupRoleAssignments/items/groupRole”响应属性中
GET /api/atlas/v2/orgs/{orgId}/invoices
Updated
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S100_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S110_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S30_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S40_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_MEMORY_NVME, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP30, ATLAS_AZURE_BACKUP_DOWNLOAD_VM_STORAGE, ATLAS_AZURE_BACKUP_DOWNLOAD_VM_STORAGE_EXTENDED_IOPS, ATLAS_AZURE_EXTENDED_STANDARD_IOPS, ATLAS_AZURE_SNAPSHOT_EXPORT_VM_STORAGE, ATLAS_AZURE_SNAPSHOT_EXPORT_VM_STORAGE_EXTENDED_IOPS, ATLAS_AZURE_STANDARD_STORAGE, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP30' 枚举 values to the 'results/items/lineItems /items/sku' 属性
GET /api/atlas/v2/orgs/{orgId}/invoices/pending
Updated
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S100_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S110_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S30_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S40_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_MEMORY_NVME, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP30, ATLAS_AZURE_BACKUP_DOWNLOAD_VM_STORAGE, ATLAS_AZURE_BACKUP_DOWNLOAD_VM_STORAGE_EXTENDED_IOPS, ATLAS_AZURE_EXTENDED_STANDARD_IOPS, ATLAS_AZURE_SNAPSHOT_EXPORT_VM_STORAGE, ATLAS_AZURE_SNAPSHOT_EXPORT_VM_STORAGE_EXTENDED_IOPS, ATLAS_AZURE_STANDARD_STORAGE, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP30' 枚举 values to the 'results/items/lineItems /items/sku' 属性
GET /api/atlas/v2/orgs/{orgId}/invoices/{invoiceId}
Updated
  • Added the new 'ATLAS_AWS_SEARCH_INSTANCE_S100_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S110_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S30_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S40_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S50_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S60_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S80_MEMORY_NVME, ATLAS_AWS_SEARCH_INSTANCE_S90_MEMORY_NVME, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP30, ATLAS_AZURE_BACKUP_DOWNLOAD_VM_STORAGE, ATLAS_AZURE_BACKUP_DOWNLOAD_VM_STORAGE_EXTENDED_IOPS, ATLAS_AZURE_EXTENDED_STANDARD_IOPS, ATLAS_AZURE_SNAPSHOT_EXPORT_VM_STORAGE, ATLAS_AZURE_SNAPSHOT_EXPORT_VM_STORAGE_EXTENDED_IOPS, ATLAS_AZURE_STANDARD_STORAGE, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP30' 枚举 values to the 'lineItems/items/sku ' 属性
GET /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/角色/items/roleName' 响应属性
POST /api/atlas/v2/orgs/{orgId}/teams/{teamId}/users
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/角色/items/roleName' 响应属性
GET /api/atlas/v2/orgs/{orgId}/users
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 'results/items/角色/items/roleName' 响应属性
GET /api/atlas/v2/unauth/controlPlaneIPAddresses
已交
  • 已添加端点
POST /api/atlas/v2/users
Updated
  • 请求所需属性“emailAddress”变为只读
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
  • 已将新的“GROUP_STREAM_PROCESSING_OWNER”枚举值添加到请求属性“角色/items/roleName”
GET /api/atlas/v2/users/byName/{userName}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性
GET /api/atlas/v2/users/{userId}
Updated
  • 将新的 'GROUP_STREAM_PROCESSING_OWNER' 枚举值添加到 '角色/items/roleName' 响应属性

2023 年 2 月 1 日发布

GET /api/atlas/v2/groups/{groupId}/clusters
已交
  • 从响应中删除了可选属性：'results.items.mongoURIWithOptions', 'results.items.providerBackupEnabled', 'results.items.mongoURIUpdated', 'results.items.srvAddress', 'results.items.replicationSpec', 'results.items.mongoURI', 'results.items.numShards', 'results.items.autoScaling', 'results.items.providerSettings', 'results.items.replicationFactor', 'results.items.replicationSpecs.regionsConfig'
  • 添加了响应属性“results.items.replicationSpecs.regionConfigs”
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
POST /api/atlas/v2/groups/{groupId}/clusters
已交
  • 删除了请求属性：“mongoURIWithOptions”、“providerBackupEnabled”、“mongoURIUpdated”、“srvAddress”、“replicationSpec”、“mongoURI”、“numShards”、“autoScaling”、“providerSettings”、“replicationFactor”、“replicationSpecs.regionsConfig”
  • 添加了“replicationSpecs.regionConfigs” 请求属性
  • 从响应中删除了可选属性：“mongoURIWithOptions”、“providerBackupEnabled”、“mongoURIUpdated”、“srvAddress”、“replicationSpec”、“mongoURI”、“numShards”、“autoScaling”、“providerSettings”、“replicationFactor”、“replicationSpecs” .regionsConfig'
  • 添加了响应属性“replicationSpecs.regionConfigs”
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已弃用
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 从响应中删除了可选属性：“mongoURIWithOptions”、“providerBackupEnabled”、“mongoURIUpdated”、“srvAddress”、“replicationSpec”、“mongoURI”、“numShards”、“autoScaling”、“providerSettings”、“replicationFactor”、“replicationSpecs” .regionsConfig'
  • 添加了响应属性“replicationSpecs.regionConfigs”
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
PATCH /api/atlas/v2/groups/{groupId}/clusters/{clusterName}
已交
  • 删除了请求属性：“mongoURIWithOptions”、“providerBackupEnabled”、“mongoURIUpdated”、“srvAddress”、“replicationSpec”、“mongoURI”、“numShards”、“autoScaling”、“providerSettings”、“replicationFactor”、“replicationSpecs.regionsConfig”
  • 添加了“replicationSpecs.regionConfigs” 请求属性
  • 从响应中删除了可选属性：“mongoURIWithOptions”、“providerBackupEnabled”、“mongoURIUpdated”、“srvAddress”、“replicationSpec”、“mongoURI”、“numShards”、“autoScaling”、“providerSettings”、“replicationFactor”、“replicationSpecs” .regionsConfig'
  • 添加了响应属性“replicationSpecs.regionConfigs”
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
GET /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites
已弃用
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
已弃用
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/customZoneMapping
已交
  • 删除了请求属性“customZoneMappings”
  • 添加了请求属性“customZoneMapping”
  • 添加了请求属性“managedNamespaces”
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
DELETE /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
已弃用
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/globalWrites/managedNamespaces
已交
  • 请求属性“db”变为可选
  • 请求属性 'collection' 变为可选
  • 请求属性“customShardKey”变为可选
  • “numInitialChunks”请求属性的最大值已删除（来自 8192）
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
POST /api/atlas/v2/groups/{groupId}/clusters/{clusterName}/restartPrimaries
已弃用
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日
GET /api/atlas/v2/groups/{groupId}/clusters/{hostName}/logs/{logName}.gz
已弃用
  • 2023 年 2 月 1 日添加了新资源。 资源版本 2023-01-01 已弃用，并标记为删除日期：2025 年 6 月 1 日