AI 에이전트의 경우: 문서 인덱스는 https://www.mongodb.com/ko-kr/docs/llms.txt에서 사용할 수 있으며, 모든 페이지의 마크다운 버전은 어떤 URL 경로에 .md를 추가하여 사용할 수 있습니다.
Docs Menu

API 변경 로그

(2.0~df88910a7b3)

2026년 9월 09일 출시

  • Added the enum value `CAPACITY_RETRY_OVERRIDE_REMOVED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CAPACITY_RETRY_OVERRIDE_SET` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_FORCE_PAUSE_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_ENDED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_END_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_FAILED_TO_START` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_STARTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `eventType`
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the request property 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the request property 'oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the request property 'oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the request property 'oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #16: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #16: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #16: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #16: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #1: Datadog Notification]/datadogRegion' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Removed the 'ENHANCED_FULLY_WARMED' enum value from the 'results/items/diskWarmingMode' response property for the response status '200'
  • Added the optional properties 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput' to the response with the '200' status
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '201'
  • Removed the 'ENHANCED_FULLY_WARMED' enum value from the 'diskWarmingMode' response property for the response status '201'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • Removed the enum value 'ENHANCED_FULLY_WARMED' of the request property 'diskWarmingMode'
  • Added the optional properties 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput' to the response with the '201' status
  • Added the new optional request properties 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS'
  • Added the new 'M300_GEN_2' enum value to the 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/instanceSizeName' response property for the response status '200'
  • Removed the 'ENHANCED_FULLY_WARMED' enum value from the 'diskWarmingMode' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the request property 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/instanceSizeName'
  • Removed the enum value 'ENHANCED_FULLY_WARMED' of the request property 'diskWarmingMode'
  • Added the new 'M300_GEN_2' enum value to the 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the request property 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Removed the 'ENHANCED_FULLY_WARMED' enum value from the 'diskWarmingMode' response property for the response status '200'
  • Added the optional properties 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput' to the response with the '200' status
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' response property for the response status '200'
  • Removed the 'ENHANCED_FULLY_WARMED' enum value from the 'diskWarmingMode' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • Removed the enum value 'ENHANCED_FULLY_WARMED' of the request property 'diskWarmingMode'
  • Added the optional properties 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskThroughput' to the response with the '200' status
  • Added the new optional request properties 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS'
  • For the `query` request parameter `commands`, the maxItems was increased from `3` to `7`
  • For the `query` request parameter `series`, the maxItems was increased from `15` to `22`
  • Added the enum value `DOCS_DELETED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `DOCS_INSERTED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `DOCS_MATCHED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `DOCS_MODIFIED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `DOCS_UPSERTED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `KEYS_DELETED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `KEYS_INSERTED` to the property `items/` of the `query` request parameter `series`
  • Added the enum value `count` to the property `items/` of the `query` request parameter `commands`
  • Added the enum value `delete` to the property `items/` of the `query` request parameter `commands`
  • Added the enum value `insert` to the property `items/` of the `query` request parameter `commands`
  • Added the enum value `update` to the property `items/` of the `query` request parameter `commands`
  • Added the new 'count, delete, insert, update' enum values to the 'summaries/items/command' response property for the response status '200'
  • Added the optional properties 'queryStatsCollection, summaries/items/keysDeleted, summaries/items/keysInserted, summaries/items/nDeleted, summaries/items/nInserted, summaries/items/nMatched, summaries/items/nModified, summaries/items/nUpserted' to the response with the '200' status
  • Added the new 'count, delete, insert, update' enum values to the 'queryStats/command' response property for the response status '200'
  • Added the optional properties 'queryStats/keysDeleted, queryStats/keysInserted, queryStats/nDeleted, queryStats/nInserted, queryStats/nMatched, queryStats/nModified, queryStats/nUpserted, queryStatsCollection' to the response with the '200' status
  • Added the new 'COUNT, DELETE, INSERT, UPDATE' enum values to the 'results/items/command' response property for the response status '200'
  • Added the new 'COUNT, DELETE, INSERT, UPDATE' enum values to the 'command' response property for the response status '200'
  • Added the new 'COUNT, DELETE, INSERT, UPDATE' enum values to the 'command' response property for the response status '200'
  • Added the enum value `CAPACITY_RETRY_OVERRIDE_REMOVED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CAPACITY_RETRY_OVERRIDE_REMOVED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CAPACITY_RETRY_OVERRIDE_SET` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CAPACITY_RETRY_OVERRIDE_SET` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CLUSTER_FORCE_PAUSE_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_FORCE_PAUSE_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_ENDED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_ENDED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_END_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_END_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_FAILED_TO_START` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_FAILED_TO_START` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_REQUESTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_STARTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `CLUSTER_OVERLOAD_PROTECTION_SIMULATION_STARTED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE` to the property `items/oneOf[subschema #32: Auto Scaling Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the new 'CAPACITY_RETRY_OVERRIDE_REMOVED, CAPACITY_RETRY_OVERRIDE_SET, CLUSTER_FORCE_PAUSE_REQUESTED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_ENDED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_END_REQUESTED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_FAILED_TO_START, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_REQUESTED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_STARTED' enum values to the 'results/items/oneOf[subschema #15: Atlas Project Audits]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'results/items/oneOf[subschema #16: Auto Scaling Audits]/eventTypeName' response property for the response status '200'
  • Added the new 'CAPACITY_RETRY_OVERRIDE_REMOVED, CAPACITY_RETRY_OVERRIDE_SET, CLUSTER_FORCE_PAUSE_REQUESTED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_ENDED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_END_REQUESTED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_FAILED_TO_START, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_REQUESTED, CLUSTER_OVERLOAD_PROTECTION_SIMULATION_STARTED' enum values to the 'oneOf[subschema #15: Atlas Project Audits]/eventTypeName' response property for the response status '200'
  • Added the new 'COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_ANALYTICS, COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE, PREDICTIVE_COMPUTE_AUTO_SCALE_CAPACITY_CONSTRAINT_FAIL_BASE' enum values to the 'oneOf[subschema #16: Auto Scaling Audits]/eventTypeName' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'
  • Added the new 'M300_GEN_2' enum value to the request property 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'
  • Removed the enum value 'ENHANCED_FULLY_WARMED' of the request property 'diskWarmingMode'
  • Added the new optional request properties 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/diskIOPS, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/diskIOPS'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #3: DATADOG]/region' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'oneOf[subschema #3: DATADOG]/region' response property for the response status '200'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #3: DATADOG]/region' response property for the response status '200'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #3: DATADOG]/region'
  • Added the new 'AP2' enum value to the 'results/items/oneOf[subschema #3: DATADOG]/region' response property for the response status '200'
  • Added the new 'AP2' enum value to the request property 'oneOf[subschema #3: DATADOG]/region'
  • The response property `dayOfWeek` became optional for the status `200`
  • Added the optional properties 'effectiveWaveAssignment, waveAssignment' to the response with the '200' status
  • The request property `dayOfWeek` became optional
  • 새로운 선택 사항 요청 속성 'WaveAssignment'가 추가되었습니다.
  • Added the new 'M300_GEN_2' enum value to the 'results/items/instanceSize/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Removed the enum value `TRANSACTIONS_TOTAL_ABORTED` from the property `items/` of the `query` request parameter `m`
  • Removed the enum value `TRANSACTIONS_TOTAL_COMMITTED` from the property `items/` of the `query` request parameter `m`
  • Removed the enum value `TRANSACTIONS_TOTAL_STARTED` from the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_ABORTED` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_COMMITTED` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_STARTED` to the property `items/` of the `query` request parameter `m`
  • Added the new 'M300_GEN_2' enum value to the 'results/items/providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • Added the new 'M300_GEN_2' enum value to the 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP Instance Sizes]/' response property for the response status '200'
  • The request property `secretExpiresAfterHours` became nullable
  • The request property `secretExpiresAfterHours` became optional
  • Added the new optional request property 'withoutInitialSecret'
  • The request property `serviceAccount/secretExpiresAfterHours` became nullable
  • The request property `serviceAccount/secretExpiresAfterHours` became optional
  • Added the new optional request property 'serviceAccount/withoutInitialSecret'
  • Added the enum value `SCIM_CLIENT_CREATED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_DELETED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_SECRET_CREATED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_SECRET_DELETED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_UPDATED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_CREATED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_DELETED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_SECRET_CREATED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_SECRET_DELETED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SCIM_CLIENT_UPDATED` to the property `items/oneOf[subschema #6: Federation Settings Event Types]/` of the `query` request parameter `eventType`
  • Added the new 'SCIM_CLIENT_CREATED, SCIM_CLIENT_DELETED, SCIM_CLIENT_SECRET_CREATED, SCIM_CLIENT_SECRET_DELETED, SCIM_CLIENT_UPDATED' enum values to the 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #1: Federation Settings Event Types]/' response property for the response status '200'
  • Added the new 'SCIM_CLIENT_CREATED, SCIM_CLIENT_DELETED, SCIM_CLIENT_SECRET_CREATED, SCIM_CLIENT_SECRET_DELETED, SCIM_CLIENT_UPDATED' enum values to the 'oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #1: Federation Settings Event Types]/' response property for the response status '200'
  • 엔드포인트 추가됨
  • The request property `secretExpiresAfterHours` became nullable
  • The request property `secretExpiresAfterHours` became optional
  • Added the new optional request property 'withoutInitialSecret'

2026년 9월 03일 출시

  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'results/items/dataProcessRegion/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'results/items/failoverRegions/items/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'dataProcessRegion/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'failoverRegions/items/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the request property 'dataProcessRegion/region/'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the request property 'failoverRegions/items/region/'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'dataProcessRegion/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'failoverRegions/items/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'dataProcessRegion/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'failoverRegions/items/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the request property 'failoverRegions/items/region/'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the request property 'region/'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'dataProcessRegion/region/' response property for the response status '200'
  • Added the new 'US_WEST1, eastasia, northeurope, southeastasia' enum values to the 'failoverRegions/items/region/' response property for the response status '200'

2026년 8월 27일 릴리스

  • The response property `apiKey` became optional for the status `200`
  • Added the required property 'ipAddress' to the response with the '200' status
  • Added the optional property 'user' to the response with the '200' status

2026년 8월 21일 릴리스

  • `query` 요청 매개변수 `eventType`의 속성 `items/oneOf[subschema #29: Atlas 감사 Types]/`에 열거형 값 `LOG_STREAMING_REPLAY_FAILED`가 추가되었습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #1: 기타 경고 구성]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: 기타 경고 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 요청 속성 'oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 Types]/'에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값이 추가되었습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: 기타 경고 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: 기타 경고 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: 기타 경고 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 요청 속성 'oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 Types]/'에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값이 추가되었습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #8: 기타 경고]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #8: 기타 경고]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 속성 '/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/'에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 속성 '/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #7: Atlas Audit Types]/'에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #1: 기타 경고 구성]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • `query` 요청 매개변수 `eventType`의 속성 `items/oneOf[subschema #29: Atlas 감사 Types]/`에 열거형 값 `LOG_STREAMING_REPLAY_FAILED`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 속성 `items/oneOf[subschema #29: Atlas 감사 Types]/`에 열거형 값 `LOG_STREAMING_REPLAY_FAILED`가 추가되었습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 'oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 새로운 'LOG_STREAMING_REPLAY_FAILED' 열거형 값을 추가했습니다.

2026년 8월 20일 릴리스

  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `results/items/oneOf[subschema #1: SAML]/pemFileInfo` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `oneOf[subschema #1: SAML]/pemFileInfo` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `405`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `oneOf[subschema #1: SAML]/pemFileInfo` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `405`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the enum value `DISK_WARMING_PROCESS_DISK_TAG_READY_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_INSTANCE_CANCELLED_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_NODE_HIDDEN_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_NODE_UNHIDDEN_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `ENDPOINT_SERVICE_CREATION_RETRIED` to the property `items/oneOf[subschema #40: Private Link Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `FTS_INDEX_DEFINITION_ROLLED_BACK` to the property `items/oneOf[subschema #20: FTS Index Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SQL_INTERFACE_DISABLED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SQL_INTERFACE_ENABLED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property for the response status `200`
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property `oneOf` list for the response status `200`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` request property
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` request property `oneOf` list
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property for the response status `200`
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property `oneOf` list for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property for the response status `200`
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property `oneOf` list for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property for the response status `200`
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property `oneOf` list for the response status `200`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` request property
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` request property `oneOf` list
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property for the response status `200`
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property `oneOf` list for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `results/items/oneOf[subschema #5: Host Metric Alerts]/` response property for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `results/items/oneOf[subschema #5: Host Metric Alerts]/` response property for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #5: Host Metric Alerts]/` response property for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #5: Host Metric Alerts]/` response property for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property for the response status `200`
  • Added `#/components/schemas/ConnectionsEstablishmentRateLimitRejectedRawMetricThresholdView` to the `results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold` response property `oneOf` list for the response status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `405`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Removed the 'INDEX_BUILD_FAILED' enum value from the 'results/items/state' response property for the response status '200'
  • Removed the enum value 'INDEX_BUILD_FAILED' from the 'query' request parameter 'state'
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Removed the 'INDEX_BUILD_FAILED' enum value from the 'state' response property for the response status '200'
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `405`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `503`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `503`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `503`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the enum value `DISK_WARMING_PROCESS_DISK_TAG_READY_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_DISK_TAG_READY_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `DISK_WARMING_PROCESS_INSTANCE_CANCELLED_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_INSTANCE_CANCELLED_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `DISK_WARMING_PROCESS_NODE_HIDDEN_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_NODE_HIDDEN_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `DISK_WARMING_PROCESS_NODE_UNHIDDEN_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `DISK_WARMING_PROCESS_NODE_UNHIDDEN_BY_ADMIN` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `ENDPOINT_SERVICE_CREATION_RETRIED` to the property `items/oneOf[subschema #40: Private Link Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `ENDPOINT_SERVICE_CREATION_RETRIED` to the property `items/oneOf[subschema #40: Private Link Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `FTS_INDEX_DEFINITION_ROLLED_BACK` to the property `items/oneOf[subschema #20: FTS Index Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `FTS_INDEX_DEFINITION_ROLLED_BACK` to the property `items/oneOf[subschema #20: FTS Index Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `SQL_INTERFACE_DISABLED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SQL_INTERFACE_DISABLED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • Added the enum value `SQL_INTERFACE_ENABLED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `eventType`
  • Added the enum value `SQL_INTERFACE_ENABLED` to the property `items/oneOf[subschema #29: Atlas Audit Types]/` of the `query` request parameter `excludedEventType`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `results/items/oneOf[subschema #14: Host Metric Events]/` response property for the response status `200`
  • Added the new 'DISK_WARMING_PROCESS_DISK_TAG_READY_BY_ADMIN, DISK_WARMING_PROCESS_INSTANCE_CANCELLED_BY_ADMIN, DISK_WARMING_PROCESS_NODE_HIDDEN_BY_ADMIN, DISK_WARMING_PROCESS_NODE_UNHIDDEN_BY_ADMIN, SQL_INTERFACE_DISABLED, SQL_INTERFACE_ENABLED' enum values to the 'results/items/oneOf[subschema #15: Atlas Project Audits]/eventTypeName' response property for the response status '200'
  • Added the new 'ENDPOINT_SERVICE_CREATION_RETRIED' enum value to the 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #22: Private Link Audit Types]/' response property for the response status '200'
  • Added the new 'FTS_INDEX_DEFINITION_ROLLED_BACK' enum value to the 'results/items/oneOf[subschema #12: FTS Index Audits]/eventTypeName' response property for the response status '200'
  • Removed the optional property 'results/items/oneOf[subschema #25: Stream Processor Events]/modifiedBy' from the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added `CONNECTIONS_ESTABLISHMENT_RATE_LIMIT_REJECTED` discriminator mapping keys to the `oneOf[subschema #14: Host Metric Events]/` response property for the response status `200`
  • Added the new 'DISK_WARMING_PROCESS_DISK_TAG_READY_BY_ADMIN, DISK_WARMING_PROCESS_INSTANCE_CANCELLED_BY_ADMIN, DISK_WARMING_PROCESS_NODE_HIDDEN_BY_ADMIN, DISK_WARMING_PROCESS_NODE_UNHIDDEN_BY_ADMIN, SQL_INTERFACE_DISABLED, SQL_INTERFACE_ENABLED' enum values to the 'oneOf[subschema #15: Atlas Project Audits]/eventTypeName' response property for the response status '200'
  • Added the new 'ENDPOINT_SERVICE_CREATION_RETRIED' enum value to the 'oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #22: Private Link Audit Types]/' response property for the response status '200'
  • Added the new 'FTS_INDEX_DEFINITION_ROLLED_BACK' enum value to the 'oneOf[subschema #12: FTS Index Audits]/eventTypeName' response property for the response status '200'
  • Removed the optional property 'oneOf[subschema #25: Stream Processor Events]/modifiedBy' from the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'results/items/oneOf[subschema #3: DATADOG]/sendShardingMetrics' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'oneOf[subschema #3: DATADOG]/sendShardingMetrics' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'results/items/oneOf[subschema #3: DATADOG]/sendShardingMetrics' to the response with the '200' status
  • Added the new optional request property 'oneOf[subschema #3: DATADOG]/sendShardingMetrics'
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'results/items/oneOf[subschema #3: DATADOG]/sendShardingMetrics' to the response with the '200' status
  • Added the new optional request property 'oneOf[subschema #3: DATADOG]/sendShardingMetrics'
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The request property `sharding` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The request property `sharding` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the pattern `^[\p{L}\p{N}\-_.,' ]*$` to the request property `mcpConfigName`
  • The `mcpConfigName` request property's maxLength was set to `64`
  • The `mcpConfigName` request property's minLength was decreased from `1` to `0`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The `roles` request property's minItems was increased to `1`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • 요청 속성 `oneOf[subschema3 #: GCP ]/gcpProjectId`의 패턴 `^p-[0-9az]{24}$`에서 `^([az][az]로09{428}0909{1변경됨 - -],[az -]|[20} -],)$`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'regionName' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'regionName' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the enum value `AVG_MAJORITY_WRITE_CONCERN_WRITE_TIME` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `CACHE_PRESSURE_PERCENTAGE` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `CATALOG_ACTIVE_COLLECTIONS_AND_INDEXES` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `INGRESS_QUEUE_WAIT_TIME` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `QUERY_SPILL_FILE_SPILLED_SIZE` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_BYTES_READ` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_BYTES_WRITTEN` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_READ_IOPS` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_READ_LATENCY` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_SPACE_FREE` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_SPACE_PERCENT_FREE` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_SPACE_PERCENT_USED` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_SPACE_USED` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_THROUGHPUT_UTILIZATION` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_WRITE_IOPS` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `STORAGE_WRITE_LATENCY` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_CURRENT_ACTIVE` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_CURRENT_INACTIVE` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_CURRENT_OPEN` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_TOTAL_ABORTED` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_TOTAL_COMMITTED` to the property `items/` of the `query` request parameter `m`
  • Added the enum value `TRANSACTIONS_TOTAL_STARTED` to the property `items/` of the `query` request parameter `m`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'isAtlasHomePageAiAssistantEnabled' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the optional property 'isAtlasHomePageAiAssistantEnabled' to the response with the '200' status
  • Added the new optional request property 'isAtlasHomePageAiAssistantEnabled'
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `results/items/connections/items/dbRoleToExecute` became not nullable for the status `200`
  • The request property `connections/items/dbRoleToExecute` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `connections/items/dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `connections/items/dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `connections/items/dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `results/items/dbRoleToExecute` became not nullable for the status `200`
  • The request property `dbRoleToExecute` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `dbRoleToExecute` became not nullable for the status `200`
  • The request property `dbRoleToExecute` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `results/items/dbRoleToExecute` became not nullable for the status `200`
  • The request property `dbRoleToExecute` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `dbRoleToExecute` became not nullable for the status `201`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `dbRoleToExecute` became not nullable for the status `200`
  • The request property `dbRoleToExecute` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the required property 'effectiveTier' to the response with the '200' status
  • Added the optional property 'options/autoscaling' to the response with the '200' status
  • Added the new optional request property 'options/autoscaling'
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the required property 'effectiveTier' to the response with the '200' status
  • Added the optional property 'options/autoscaling' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the required property 'effectiveTier' to the response with the '200' status
  • Added the optional property 'options/autoscaling' to the response with the '200' status
  • Added the new optional request property 'options/autoscaling'
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the new optional request property 'autoscaling'
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the required property 'results/items/effectiveTier' to the response with the '200' status
  • Added the optional property 'results/items/options/autoscaling' to the response with the '200' status
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `connections/items/dbRoleToExecute` became not nullable for the status `200`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The request property `serviceAccount` became not nullable
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `402`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the enum value `AI_MODELS_APIS_RATE_LIMIT_ADMIN_OVERRIDE` to the property `items/oneOf[subschema #17: AI Models APIs Event Types]/` of the `query` request parameter `eventType`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the enum value `AI_MODELS_APIS_RATE_LIMIT_ADMIN_OVERRIDE` to the property `items/oneOf[subschema #17: AI Models APIs Event Types]/` of the `query` request parameter `eventType`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the new 'AI_MODELS_APIS_RATE_LIMIT_ADMIN_OVERRIDE' enum value to the 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #6: AI Models APIs Event Types]/' response property for the response status '200'
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the new 'AI_MODELS_APIS_RATE_LIMIT_ADMIN_OVERRIDE' enum value to the 'oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #6: AI Models APIs Event Types]/' response property for the response status '200'
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • Added the pattern `^[\p{L}\p{N}\-_.,' ]*$` to the request property `mcpConfigName`
  • The `mcpConfigName` request property's maxLength was set to `64`
  • The `mcpConfigName` request property's minLength was decreased from `1` to `0`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The `roles` request property's minItems was increased to `1`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `409`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `400`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`
  • The response property `badRequestDetail` became not nullable for the status `401`
  • The response property `badRequestDetail` became not nullable for the status `403`
  • The response property `badRequestDetail` became not nullable for the status `404`
  • The response property `badRequestDetail` became not nullable for the status `429`
  • The response property `badRequestDetail` became not nullable for the status `500`

2026년 8월 12일 릴리스

  • 요청에 필요한 속성 `oneOf[subschema #4: OTel Log Export Integration Request]/otelSuppliedHeaders/items/value`가 쓰기 전용이 되었습니다.
  • 요청에 필요한 속성 `oneOf[subschema #4: OTel Log Export Integration Request]/otelSuppliedHeaders/items/value`가 쓰기 전용이 되었습니다.

2026년 8월 11일 릴리스

  • 엔드포인트 추가됨
  • 엔드포인트 추가됨
  • Added the enum value `ORG_DATA_SHARING_AI_MODELS_DISABLED` to the property `items/oneOf[subschema #10: Org Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `ORG_DATA_SHARING_AI_MODELS_ENABLED` to the property `items/oneOf[subschema #10: Org Event Types]/` of the `query` request parameter `eventType`
  • 엔드포인트 추가됨
  • Added the enum value `ORG_DATA_SHARING_AI_MODELS_DISABLED` to the property `items/oneOf[subschema #10: Org Event Types]/` of the `query` request parameter `eventType`
  • Added the enum value `ORG_DATA_SHARING_AI_MODELS_ENABLED` to the property `items/oneOf[subschema #10: Org Event Types]/` of the `query` request parameter `eventType`
  • Added the new 'ORG_DATA_SHARING_AI_MODELS_DISABLED, ORG_DATA_SHARING_AI_MODELS_ENABLED' enum values to the 'results/items/oneOf[subschema #8: Organization Events]/eventTypeName' response property for the response status '200'
  • Added the new 'ORG_DATA_SHARING_AI_MODELS_DISABLED, ORG_DATA_SHARING_AI_MODELS_ENABLED' enum values to the 'oneOf[subschema #8: Organization Events]/eventTypeName' response property for the response status '200'
  • 엔드포인트 추가됨
  • 엔드포인트 추가됨

2026년 8월 10일 릴리스

  • The `cloud` request property's minLength was decreased from `1` to `0`
  • `geography` 요청 속성의 minLength가 `1`에서 `0`(으)로 감소했습니다.
  • 요청 속성 'cloud'에서 'ANY' 패턴을 제거했습니다.
  • 요청 속성 'geography'에서 `ANY` 패턴을 제거했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'results/items/connections/items/authentication/AWS'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'connections/items/인증/AWS'을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'connections/items/authentication/aws'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'results/items/authenticationScheme'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'authenticationScheme'을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'authenticationScheme'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'authenticationScheme'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'authenticationScheme'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'connections/items/인증/AWS'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'connections/items/인증/AWS'을 추가했습니다.
  • '200' 상태의 응답에 선택 속성 'results/items/인증/Amazon Web Services'를 추가했습니다.
  • '200' 상태로 응답에 선택 사항 속성 'authentication/aws'가 추가되었습니다.
  • 새로운 선택적 요청 속성 '인증/Amazon Web Services'을 추가했습니다.
  • '200' 상태로 응답에 선택 사항 속성 'authentication/aws'가 추가되었습니다.
  • '200' 상태로 응답에 선택 사항 속성 'authentication/aws'가 추가되었습니다.
  • 새로운 선택적 요청 속성 '인증/Amazon Web Services'을 추가했습니다.
  • '200' 상태의 응답에 선택 속성 'results/items/인증/Amazon Web Services'를 추가했습니다.
  • '201' 상태로 응답에 선택 사항 속성 'authentication/aws'가 추가되었습니다.
  • 새로운 선택적 요청 속성 '인증/Amazon Web Services'을 추가했습니다.
  • '200' 상태로 응답에 선택 사항 속성 'authentication/aws'가 추가되었습니다.
  • '200' 상태로 응답에 선택 사항 속성 'authentication/aws'가 추가되었습니다.
  • 새로운 선택적 요청 속성 '인증/Amazon Web Services'을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'connections/items/인증/AWS'을 추가했습니다.

2026년 8월 07일 릴리스

  • 새로운 선택 사항 요청 속성 '페일오버/clearCheckpoint' 추가
  • '200' 상태의 응답에 선택 사항 속성 'gateways'를 추가했습니다.

2026년 8월 05일 릴리스

  • '200' 상태의 응답에 선택 속성 'results/items/lineItems/items/cloudProvider'가 추가되었습니다.
  • '200' 상태의 응답에 선택 속성 'lineItems/items/cloudProvider'를 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'results/items/cloudProvider'를 추가했습니다.

2026년 8월 03일 릴리스

2026년 7월 31일 릴리스

  • '200' 상태로 응답에 선택 사항 속성 'results/items/oneOf[subschema #25: Stream Processor 이벤트]/리전'을 추가했습니다.
  • Added the optional property 'oneOf[subschema #25: Stream Processor Events]/region' to the response with the '200' status

2026년 7월 29일 릴리스

  • 쿼리 `eventType` 요청 매개변수의 `items/oneOf[subschema #20: Full Text Search 인덱스 감사 유형]/` 속성에 `FTS_INDEX_PARTITIONS_CHANGED` 열거형 값을 추가했습니다.
  • `쿼리` 요청 매개변수 `eventType`의 `items/oneOf[subschema #20: FTS Index 감사 Types]/` 속성에 열거형 값 `FTS_INDEX_REBUILT`가 추가되었습니다.
  • 쿼리 요청 매개변수 `eventType`의 `items/oneOf[subschema #29: Atlas 감사 유형]/` 속성에 열거형 값 `SEARCH_HOST_PAUSE_INITIAL_SYNC_ON_INDEX_IDS`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `eventType`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_AUTOSCALE_INITIATED`를 추가했습니다.
  • 쿼리 요청 매개변수 `eventType`의 속성 `items/oneOf[subschema #49: Stream Processor Event Types]/`에 열거형 값 `STREAM_PROCESSOR_CREATED`가 추가되었습니다.
  • 쿼리 요청 매개변수 `이벤트Type`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_DROPPED`을 추가했습니다.
  • `query` 요청 매개변수 `eventType`의 `items/oneOf[subschema #49: 스트림 프로세서 이벤트 유형]/` 속성에 `STREAM_PROCESSOR_MODIFIED` 열거형 값을 추가했습니다.
  • `쿼리` 요청 매개변수 `eventType`의 `items/oneOf[subschema #49: Stream Processor Event Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_STOPPED`가 추가되었습니다.
  • 요청 매개변수 `eventType`의 속성 `items/oneOf[subschema #29: Atlas 감사 Types]/`에 열거형 값 `VOLUME_IMPAIRED`가 추가되었습니다. 쿼리 요청 매개변수
  • 쿼리 요청 매개변수 `eventType`의 `items/oneOf[subschema #29: Atlas 감사 Types]/` 속성에 열거형 값 `VOLUME_IMPAIRED_RESOLVED`를 추가했습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other 경고 Configurations]/이벤트TypeName/oneOf[subschema #12: Stream Processor 이벤트 Types]/' 응답 속성에 응답 상태 '200'에 대한 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: Any Other 경고 Configurations]/이벤트TypeName/oneOf[subschema #12: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 요청 속성 'oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName'에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 요청 속성 'oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: Stream Processor Event Types]/'에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: Any Other 경고 Configurations]/이벤트TypeName/oneOf[subschema #12: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: Any Other 경고 Configurations]/이벤트TypeName/oneOf[subschema #12: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: Any Other 경고 Configurations]/이벤트TypeName/oneOf[subschema #12: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 요청 속성 'oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName'에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 요청 속성 'oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: Stream Processor Event Types]/'에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'results/items/oneOf[subschema #8: Any Other 경고]/이벤트TypeName/oneOf[subschema #15: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'results/items/oneOf[subschema #8: Any Other 경고]/이벤트TypeName/oneOf[subschema #15: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #8: Any Other 경고]/eventTypeName/oneOf[subschema #15: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #8: Any Other 경고]/eventTypeName/oneOf[subschema #15: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #17: Stream Processor 경고 Configuration]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other 경고 Configurations]/이벤트TypeName/oneOf[subschema #12: Stream Processor 이벤트 Types]/' 응답 속성에 응답 상태 '200'에 대한 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED' 열거형 값을 추가했습니다.
  • 요청 선택적 속성 `clusterDescription/mongoDBEmployeeAccessGrant`가 읽기 전용이 되었습니다.
  • 요청 선택 사항 속성 `mongoDBEmployeeAccessGrant`가 읽기 전용이 되었습니다.
  • 요청 선택 사항 속성 `mongoDBEmployeeAccessGrant`가 읽기 전용이 되었습니다.
  • 요청 선택 사항 속성 `mongoDBEmployeeAccessGrant`가 읽기 전용이 되었습니다.
  • 새로운 선택 사항 `쿼리` 요청 매개변수 `envelope` 추가
  • '200' 상태의 응답에 필수 속성 'content, status'를 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'links, 위치'를 추가했습니다.
  • '200' 상태의 응답에서 선택 속성 'hiddenIndexes, redundantIndexes, unusedIndexes'를 제거했습니다.
  • 새로운 선택 사항 `쿼리` 요청 매개변수 `envelope` 추가
  • '200' 상태의 응답에 필수 속성 'content, status'를 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'links, 위치'를 추가했습니다.
  • '200' 상태의 응답에서 선택 사항 속성 'recommendations'를 제거했습니다.
  • 새로운 선택 사항 `쿼리` 요청 매개변수 `envelope` 추가
  • '200' 상태의 응답에 필수 속성 'content, status'를 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'links, 위치'를 추가했습니다.
  • '200' 상태의 응답에서 선택 사항 속성 'shapes, suggestedIndexes'를 제거했습니다.
  • 쿼리 `eventType` 요청 매개변수의 `items/oneOf[subschema #20: Full Text Search 인덱스 감사 유형]/` 속성에 `FTS_INDEX_PARTITIONS_CHANGED` 열거형 값을 추가했습니다.
  • `쿼리` 요청 매개변수의 `items/oneOf[subschema #20: FTS Index 감사 Types]/` 속성에 `FTS_INDEX_PARTITIONS_CHANGED` 열거형 값을 추가했습니다.
  • `쿼리` 요청 매개변수 `eventType`의 `items/oneOf[subschema #20: FTS Index 감사 Types]/` 속성에 열거형 값 `FTS_INDEX_REBUILT`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #20: FTS Index 감사 Types]/` 속성에 열거형 값 `FTS_INDEX_REBUILT`를 추가했습니다.
  • 쿼리 요청 매개변수 `eventType`의 `items/oneOf[subschema #29: Atlas 감사 유형]/` 속성에 열거형 값 `SEARCH_HOST_PAUSE_INITIAL_SYNC_ON_INDEX_IDS`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #29: Atlas 감사 Types]/` 속성에 열거형 값 `SEARCH_HOST_PAUSE_INITIAL_SYNC_ON_INDEX_IDS`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `eventType`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_AUTOSCALE_INITIATED`를 추가했습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_AUTOSCALE_INITIATED`가 추가되었습니다.
  • 쿼리 요청 매개변수 `eventType`의 속성 `items/oneOf[subschema #49: Stream Processor Event Types]/`에 열거형 값 `STREAM_PROCESSOR_CREATED`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_CREATED`가 추가되었습니다.
  • 쿼리 요청 매개변수 `이벤트Type`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_DROPPED`을 추가했습니다.
  • 쿼리 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_DROPPED`를 추가했습니다.
  • `query` 요청 매개변수 `eventType`의 `items/oneOf[subschema #49: 스트림 프로세서 이벤트 유형]/` 속성에 `STREAM_PROCESSOR_MODIFIED` 열거형 값을 추가했습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #49: 스트림 프로세서 이벤트 유형]/` 속성에 `STREAM_PROCESSOR_MODIFIED` 열거형 값을 추가했습니다.
  • `쿼리` 요청 매개변수 `eventType`의 `items/oneOf[subschema #49: Stream Processor Event Types]/` 속성에 열거형 값 `STREAM_PROCESSOR_STOPPED`가 추가되었습니다.
  • `쿼리` 요청 매개변수 `excludedEventType`의 `items/oneOf[subschema #49: Stream Processor 이벤트 Types]/` 속성에 `STREAM_PROCESSOR_STOPPED` 열거형 값을 추가했습니다.
  • 요청 매개변수 `eventType`의 속성 `items/oneOf[subschema #29: Atlas 감사 Types]/`에 열거형 값 `VOLUME_IMPAIRED`가 추가되었습니다. 쿼리 요청 매개변수
  • `쿼리` 요청 매개변수의 `items/oneOf[subschema #29: Atlas 감사 유형]/` 속성에 `VOLUME_IMPAIRED` 열거형 값을 추가했습니다.
  • 쿼리 요청 매개변수 `eventType`의 `items/oneOf[subschema #29: Atlas 감사 Types]/` 속성에 열거형 값 `VOLUME_IMPAIRED_RESOLVED`를 추가했습니다.
  • `excludedEventType` 쿼리 요청 매개변수의 `items/oneOf[subschema #29: Atlas 감사 유형]/` 속성에 `VOLUME_IMPAIRED_RESOLVED` 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #12: FTS 인덱스 감사]/eventTypeName' 응답 속성에 새로운 'FTS_INDEX_PARTITIONS_CHANGED, FTS_INDEX_REBUILT' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 새로운 'SEARCH_HOST_PAUSE_INITIAL_SYNC_ON_INDEX_IDS, VOLUME_IMPAIRED, VOLUME_IMPAIRED_RESOLVED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대해 'results/items/oneOf[subschema #1: Any Other 이벤트]/이벤트TypeName/oneOf[subschema #30: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED, STREAM_PROCESSOR_CREATED, STREAM_PROCESSOR_DROPPED, STREAM_PROCESSOR_MODIFIED, STREAM_PROCESSOR_STOPPED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'의 'results/items/oneOf[subschema #25: Stream Processor 이벤트]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED, STREAM_PROCESSOR_CREATED, STREAM_PROCESSOR_DROPPED, STREAM_PROCESSOR_MODIFIED, STREAM_PROCESSOR_STOPPED' 열거형 값을 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'results/items/delegatePrincipal, results/items/oneOf[subschema #10: 데이터 탐색기 Accessed 이벤트]/delegatePrincipal, results/items/oneOf[subschema #11: 데이터 탐색기 이벤트]/delegatePrincipal, results/items/oneOf[subschema #12: Full Text Search 인덱스 감사]/delegatePrincipal, results/items/oneOf[subschema #13: 호스팅하다 이벤트]/delegatePrincipal, results/items/oneOf[subschema #14: 호스팅하다 지표 이벤트]/delegatePrincipal, results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/delegatePrincipal, results/items/oneOf[subschema #16: 자동 확장 감사]/delegatePrincipal, results/items/oneOf[subschema #17: 서버리스 인스턴스 감사]/delegatePrincipal, results/items/oneOf[subschema #18: 테넌트 엔드포인트 감사]/delegatePrincipal, results/items/oneOf[subschema #1: Any Other 이벤트]/delegatePrincipal, results/items/oneOf[subschema #20: Search 배포서버 감사]/delegatePrincipal, results/items/oneOf[subschema #21: 팀 이벤트]/delegatePrincipal, results/items/oneOf[subschema #22: User 이벤트]/delegatePrincipal, results/items/oneOf[subschema #23: 리소스 이벤트]/delegatePrincipal, results/items/oneOf[subschema #25: Stream Processor 이벤트]/fromTier, results/items/oneOf[subschema #25: Stream Processor 이벤트]/modifiedBy, results/items/oneOf[subschema #25: Stream Processor 이벤트]/reason, results/items/oneOf[subschema #25: Stream Processor 이벤트]/toTier, results/items/oneOf[subschema #27: Atlas 리소스 정책 감사 For Atlas Group]/delegatePrincipal, results/items/oneOf[subschema #2: 경고 감사]/delegatePrincipal, results/items/oneOf[subschema #3: 경고 Config 감사]/delegatePrincipal, results/items/oneOf[subschema #4: API User 이벤트]/delegatePrincipal, results/items/oneOf[subschema #5: ServiceAccount 이벤트]/delegatePrincipal, results/items/oneOf[subschema #6: 자동화 Config 이벤트]/delegatePrincipal, results/items/oneOf[subschema #8: 청구, 결제 이벤트]/delegatePrincipal'을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #12: FTS 인덱스 감사]/eventTypeName' 응답 속성에 새로운 'FTS_INDEX_PARTITIONS_CHANGED, FTS_INDEX_REBUILT' 열거형 값을 추가했습니다.
  • 'oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 응답 상태 '200'에 대한 새로운 'SEARCH_HOST_PAUSE_INITIAL_SYNC_ON_INDEX_IDS, VOLUME_IMPAIRED, VOLUME_IMPAIRED_RESOLVED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 '/oneOf[subschema #1: Any Other 이벤트]/이벤트TypeName/oneOf[subschema #30: Stream Processor 이벤트 Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED, STREAM_PROCESSOR_CREATED, STREAM_PROCESSOR_DROPPED, STREAM_PROCESSOR_MODIFIED, STREAM_PROCESSOR_STOPPED' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 속성 '/oneOf[subschema #25: 스트림 프로세서 이벤트]/eventTypeName'에 새로운 'STREAM_PROCESSOR_AUTOSCALE_INITIATED, STREAM_PROCESSOR_CREATED, STREAM_PROCESSOR_DROPPED, STREAM_PROCESSOR_MODIFIED, STREAM_PROCESSOR_STOPPED' 열거형 값을 추가했습니다.
  • 선택 사항인 속성 '데리가트 주체, oneOf[subschema #10: 데이터 탐색기 액세스 이벤트]/delegatePrincipal, oneOf[subschema #11: 데이터 탐색기 이벤트]/delegatePrincipal, oneOf[subschema #12: Full Text Search 인덱스 감사]/delegatePrincipal, oneOf[subschema #13: 호스팅 이벤트]/delegatePrincipal, oneOf[subschema #14: 호스팅 지표 이벤트]/delegatePrincipal, oneOf[subschema #15: Atlas 프로젝트 감사]/delegatePrincipal, oneOf[subschema #16: 자동 확장 감사]/delegatePrincipal, oneOf[subschema #17: 서버리스 인스턴스 감사]/delegatePrincipal, oneOf[subschema #18: 테넌트 엔드포인트 감사]/delegatePrincipal, oneOf[subschema #1: 기타 이벤트]/delegatePrincipal, oneOf[subschema #20: 검색 배포서버 감사]/delegatePrincipal, oneOf[subschema #21: 팀 이벤트]/delegatePrincipal, oneOf[subschema #22: 사용자 이벤트]/delegatePrincipal, oneOf[subschema #23: 리소스 이벤트]/delegatePrincipal, oneOf[subschema #25: 스트림 프로세서 이벤트]/fromTier, oneOf[subschema #25: 스트림 프로세서 이벤트]/modifiedBy, oneOf[subschema #25: 스트림 프로세서 이벤트]/reason, oneOf[subschema #25: 스트림 프로세서 이벤트]/toTier, oneOf[subschema #27: Atlas 그룹의 Atlas 리소스 정책 감사]/delegatePrincipal, oneOf[subschema #2: 경고 감사]/delegatePrincipal, oneOf[subschema #3: 경고 구성 감사]/delegatePrincipal, oneOf[subschema #4: API 사용자 이벤트]/delegatePrincipal, oneOf[subschema #5: 서비스 계정 이벤트]/delegatePrincipal, oneOf[subschema #6: 자동화 구성 이벤트]/delegatePrincipal, oneOf[subschema #8: 청구, 결제 이벤트]/delegatePrincipal'을 '200' 상태의 응답에 추가했습니다.
  • 요청 선택 사항 속성 `mongoDBEmployeeAccessGrant`가 읽기 전용이 되었습니다.
  • 선택 사항인 속성 'slowQueries/items/지표/hasAutoEmbedding, slowQueries/items/지표/hasRerank, slowQueries/items/지표/tokensUsed'를 '200' 상태의 응답에 추가했습니다.
  • `secretExpiresAfterHours` 요청 속성의 exclusiveMinimum이 `true`로 설정되었습니다.
  • `secretExpiresAfterHours` 요청 속성의 최소값이 `0.00`으(로) 설정되었습니다.
  • '200' 상태의 응답에 선택 속성 'results/items/connections/items/publicPrivateNetworking'을 추가했습니다.
  • 선택적 속성 'connections/items/publicPrivateNetworking'을 '200' 상태와 함께 응답에 추가했습니다.
  • 새로운 선택 사항 요청 속성 'connections/items/publicPrivateNetworking'이 추가되었습니다.
  • 선택적 속성 'connections/items/publicPrivateNetworking'을 '200' 상태와 함께 응답에 추가했습니다.
  • 선택적 속성 'connections/items/publicPrivateNetworking'을 '200' 상태와 함께 응답에 추가했습니다.
  • '200' 상태의 응답에 선택 사항 속성 'results/items/publicPrivateNetworking'을 추가했습니다.
  • '200' 상태의 응답에 'publicPrivateNetworking' 선택 사항 속성을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'publicPrivateNetworking' 추가
  • '200' 상태의 응답에 'publicPrivateNetworking' 선택 사항 속성을 추가했습니다.
  • '200' 상태의 응답에 'publicPrivateNetworking' 선택 사항 속성을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'publicPrivateNetworking' 추가
  • 응답 상태 `200`에 대한 `results/items/` 응답 속성의 판별자 키 `클러스터`의 매핑된 값이 `#/components/스키마/StreamsClusterConnection`에서 `#/components/스키마/StreamsFailoverClusterConnection`으로 변경되었습니다.
  • 응답 상태 `200`에 대한 `results/items/` 응답 속성의 디스크리미네이터 키 `Kafka`의 매핑된 값이 `#/components/schemas/StreamsKafkaConnection`에서 `#/components/schemas/StreamsFailoverKafkaConnection`으로 변경되었습니다.
  • 응답 상태 `200`에 대한 응답 판별자에서 `GCPPubSub, S3, 샘플, AzureBlobStorage, HTTPS, SchemaRegistry, AWSKinesisDataStreams, AWSLambda` 판별자 매핑 키를 제거했습니다.
  • 응답 상태200에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsFailoverClusterConnection, #/components/schemas/StreamsFailoverKafkaConnection'를 추가했습니다.
  • 응답 상태 `200`의 응답 속성 `oneOf` 목록의 `results/items/` 속성에서 `#/components/스키마/StreamsSampleConnection, #/components/스키마/StreamsClusterConnection, #/components/스키마/StreamsKafkaConnection, #/components/스키마/StreamsHttpsConnection, #/components/스키마/StreamsAWSLambdaConnection, #/components/스키마/StreamsS3Connection, #/components/스키마/StreamsAWSKinesisDataStreamsConnection, #/components/스키마/StreamsSchemaRegistryConnection, #/components/스키마/StreamsAzureBlobStorageConnection, #/components/스키마/StreamsGCPPubSubConnection`을(를) 제거했습니다.
  • 응답 상태 '200'의 응답 속성 'results/items/type'에서 'AWSKinesisDataStreams, AWSLambda, AzureBlobStorage, GCPPubSub, HTTPS, 샘플, SchemaRegistry' 열거형 값을 제거했습니다.
  • 요청 본문 `oneOf` 목록에서 `#/components/스키마/StreamsSampleConnection, #/components/스키마/StreamsClusterConnection, #/components/스키마/StreamsKafkaConnection, #/components/스키마/StreamsHttpsConnection, #/components/스키마/StreamsAWSLambdaConnection, #/components/스키마/StreamsS3Connection, #/components/스키마/StreamsAWSKinesisDataStreamsConnection, #/components/스키마/StreamsSchemaRegistryConnection, #/components/스키마/StreamsAzureBlobStorageConnection, #/components/스키마/StreamsGCPPubSubConnection`이(가) 제거되었습니다.
  • 요청 판별자에서 `클러스터` 키의 매핑된 값이 `#/components/schemas/StreamsClusterConnection`에서 `#/components/schemas/StreamsFailoverClusterConnection`로 변경되었습니다.
  • 요청 판별자에서 `Kafka` 키의 매핑된 값이 `#/components/스키마/StreamsKafkaConnection`에서 `#/components/스키마/StreamsFailoverKafkaConnection`으로 변경되었습니다.
  • 요청 구분자에서 `S3, 샘플, HTTPS, SchemaRegistry, AWSKinesisDataStreams, GCPPubSub, AzureBlobStorage, AWSLambda` 매핑 키를 제거했습니다.
  • 요청 본문 `oneOf` 목록에 `#/components/스키마/StreamsFailoverClusterConnection, #/components/스키마/StreamsFailoverKafkaConnection`를 추가했습니다.
  • 키 `클러스터`의 매핑된 값이 응답 상태 '201'에 대한 응답 판별자에서 '#/components/스키마/Streams클러스터Connection'에서 '#/components/스키마/StreamsFailover클러스터Connection'로 변경되었습니다.
  • 키 `Kafka`의 매핑된 값이 응답 상태 `201`에 대한 응답 판별자에서 `#/components/스키마/StreamsKafkaConnection`에서 `#/components/스키마/StreamsFailoverKafkaConnection`으로 변경되었습니다.
  • 응답 상태 '201'에 대한 응답 판별자에서 `AzureBlobStorage, SchemaRegistry, AWSKinesisDataStreams, GCPPubSub, 샘플, HTTPS, AWSLambda, S3` 매핑 키를 제거했습니다.
  • 응답 상태 `201`에 대한 응답 본문 `oneOf` 목록에 `#/components/스키마/StreamsFailoverClusterConnection, #/components/스키마/StreamsFailoverKafkaConnection`을 추가했습니다.
  • 응답 상태 `201`의 응답 본문 `oneOf` 목록에서 `#/components/스키마/StreamsSampleConnection, #/components/스키마/StreamsClusterConnection, #/components/스키마/StreamsKafkaConnection, #/components/스키마/StreamsHttpsConnection, #/components/스키마/StreamsAWSLambdaConnection, #/components/스키마/StreamsS3Connection, #/components/스키마/StreamsAWSKinesisDataStreamsConnection, #/components/스키마/StreamsSchemaRegistryConnection, #/components/스키마/StreamsAzureBlobStorageConnection, #/components/스키마/StreamsGCPPubSubConnection`을 제거했습니다.
  • 응답 상태 '201'의 응답 속성 'type'에서 'AWSKinesisDataStreams, AWSLambda, AzureBlobStorage, GCPPubSub, HTTPS, 샘플, SchemaRegistry' 열거형 값을 제거했습니다.
  • 요청 속성 'type'의 열거형 값 'AWSKinesisDataStreams, AWSLambda, AzureBlobStorage, GCPPubSub, HTTPS, 샘플, SchemaRegistry'를 제거했습니다.
  • 키 `클러스터`의 매핑된 값이 응답 상태 '200'에 대한 응답 판별자에서 '#/components/스키마/Streams클러스터Connection'에서 '#/components/스키마/StreamsFailover클러스터Connection'로 변경되었습니다.
  • 키 `Kafka`의 매핑된 값이 응답 상태 `200`에 대한 응답 판별자에서 `#/components/스키마/StreamsKafkaConnection`에서 `#/components/스키마/StreamsFailoverKafkaConnection`으로 변경되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에서 `HTTPS, S3, SchemaRegistry, AWSKinesisDataStreams, AWSLambda, GCPPubSub, 샘플, AzureBlobStorage` 매핑 키를 제거했습니다.
  • 응답 상태 `200`에 대한 응답 본문 `oneOf` 목록에 `#/components/스키마/StreamsFailoverClusterConnection, #/components/스키마/StreamsFailoverKafkaConnection`을 추가했습니다.
  • 응답 상태 `200`의 응답 본문 `oneOf` 목록에서 `#/components/스키마/StreamsSampleConnection, #/components/스키마/StreamsClusterConnection, #/components/스키마/StreamsKafkaConnection, #/components/스키마/StreamsHttpsConnection, #/components/스키마/StreamsAWSLambdaConnection, #/components/스키마/StreamsS3Connection, #/components/스키마/StreamsAWSKinesisDataStreamsConnection, #/components/스키마/StreamsSchemaRegistryConnection, #/components/스키마/StreamsAzureBlobStorageConnection, #/components/스키마/StreamsGCPPubSubConnection`을 제거했습니다.
  • 응답 상태 '200'의 응답 속성 'type'에서 'AWSKinesisDataStreams, AWSLambda, AzureBlobStorage, GCPPubSub, HTTPS, 샘플, SchemaRegistry' 열거형 값을 제거했습니다.
  • 요청 본문 `oneOf` 목록에서 `#/components/스키마/StreamsSampleConnection, #/components/스키마/StreamsClusterConnection, #/components/스키마/StreamsKafkaConnection, #/components/스키마/StreamsHttpsConnection, #/components/스키마/StreamsAWSLambdaConnection, #/components/스키마/StreamsS3Connection, #/components/스키마/StreamsAWSKinesisDataStreamsConnection, #/components/스키마/StreamsSchemaRegistryConnection, #/components/스키마/StreamsAzureBlobStorageConnection, #/components/스키마/StreamsGCPPubSubConnection`이(가) 제거되었습니다.
  • 요청 판별자에서 `클러스터` 키의 매핑된 값이 `#/components/schemas/StreamsClusterConnection`에서 `#/components/schemas/StreamsFailoverClusterConnection`로 변경되었습니다.
  • 요청 판별자에서 `Kafka` 키의 매핑된 값이 `#/components/스키마/StreamsKafkaConnection`에서 `#/components/스키마/StreamsFailoverKafkaConnection`으로 변경되었습니다.
  • 요청 구분자에서 `GCPPubSub, S3, 샘플, AWSKinesisDataStreams, AzureBlobStorage, HTTPS, SchemaRegistry, AWSLambda` 매핑 키를 제거했습니다.
  • 요청 본문 `oneOf` 목록에 `#/components/스키마/StreamsFailoverClusterConnection, #/components/스키마/StreamsFailoverKafkaConnection`를 추가했습니다.
  • 키 `클러스터`의 매핑된 값이 응답 상태 '200'에 대한 응답 판별자에서 '#/components/스키마/Streams클러스터Connection'에서 '#/components/스키마/StreamsFailover클러스터Connection'로 변경되었습니다.
  • 키 `Kafka`의 매핑된 값이 응답 상태 `200`에 대한 응답 판별자에서 `#/components/스키마/StreamsKafkaConnection`에서 `#/components/스키마/StreamsFailoverKafkaConnection`으로 변경되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에서 `SchemaRegistry, AWSKinesisDataStreams, AWSLambda, GCPPubSub, S3, 샘플, AzureBlobStorage, HTTPS` 매핑 키를 제거했습니다.
  • 응답 상태 `200`에 대한 응답 본문 `oneOf` 목록에 `#/components/스키마/StreamsFailoverClusterConnection, #/components/스키마/StreamsFailoverKafkaConnection`을 추가했습니다.
  • 응답 상태 `200`의 응답 본문 `oneOf` 목록에서 `#/components/스키마/StreamsSampleConnection, #/components/스키마/StreamsClusterConnection, #/components/스키마/StreamsKafkaConnection, #/components/스키마/StreamsHttpsConnection, #/components/스키마/StreamsAWSLambdaConnection, #/components/스키마/StreamsS3Connection, #/components/스키마/StreamsAWSKinesisDataStreamsConnection, #/components/스키마/StreamsSchemaRegistryConnection, #/components/스키마/StreamsAzureBlobStorageConnection, #/components/스키마/StreamsGCPPubSubConnection`을 제거했습니다.
  • 응답 상태 '200'의 응답 속성 'type'에서 'AWSKinesisDataStreams, AWSLambda, AzureBlobStorage, GCPPubSub, HTTPS, 샘플, SchemaRegistry' 열거형 값을 제거했습니다.
  • 요청 속성 'type'의 열거형 값 'AWSKinesisDataStreams, AWSLambda, AzureBlobStorage, GCPPubSub, HTTPS, 샘플, SchemaRegistry'를 제거했습니다.
  • 새로운 선택 사항 요청 속성 '계층'가 추가되었습니다.
  • 선택적 속성 'connections/items/publicPrivateNetworking'을 '200' 상태와 함께 응답에 추가했습니다.
  • '200' 상태의 응답에 선택 속성 'results/items/oneOf[subschema #10: 사용자 이벤트]/delegatePrincipal, results/items/oneOf[subschema #11: 리소스 이벤트]/delegatePrincipal, results/items/oneOf[subschema #12: Atlas 리소스 정책 감사]/delegatePrincipal, results/items/oneOf[subschema #1: 기타 모든 이벤트]/delegatePrincipal, results/items/oneOf[subschema #2: 경고 감사]/delegatePrincipal, results/items/oneOf[subschema #3: 경고 구성 감사]/delegatePrincipal, results/items/oneOf[subschema #4: API 사용자 이벤트]/delegatePrincipal, results/items/oneOf[subschema #5: 서비스 계정 이벤트]/delegatePrincipal, results/items/oneOf[subschema #6: 청구, 결제 이벤트]/delegatePrincipal, results/items/oneOf[subschema #7: Atlas 조직 감사]/delegatePrincipal, results/items/oneOf[subschema #8: 조직 이벤트]/delegatePrincipal, results/items/oneOf[subschema #9: 팀 이벤트]/delegatePrincipal'을 추가했습니다.
  • `200` 상태의 응답에 선택 사항 속성 'oneOf[subschema #10: 사용자 이벤트]/delegatePrincipal, oneOf[subschema #11: 리소스 이벤트]/delegatePrincipal, oneOf[subschema #12: Atlas 리소스 정책 감사]/delegatePrincipal, oneOf[subschema #1: 기타 모든 이벤트]/delegatePrincipal, oneOf[subschema #2: 경고 감사]/delegatePrincipal, oneOf[subschema #3: 경고 구성 감사]/delegatePrincipal, oneOf[subschema #4: API 사용자 이벤트]/delegatePrincipal, oneOf[subschema #5: 서비스 계정 이벤트]/delegatePrincipal, oneOf[subschema #6: 청구, 결제 이벤트]/delegatePrincipal, oneOf[subschema #7: Atlas 조직 감사]/delegatePrincipal, oneOf[subschema #8: 조직 이벤트]/delegatePrincipal, oneOf[subschema #9: 팀 이벤트]/delegatePrincipal'을 추가했습니다.
  • `secretExpiresAfterHours` 요청 속성의 exclusiveMinimum이 `true`로 설정되었습니다.
  • `secretExpiresAfterHours` 요청 속성의 최소값이 `0.00`으(로) 설정되었습니다.

2026년 7월 14일 릴리스

  • 엔드포인트 추가됨
  • 엔드포인트 추가됨
  • 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성에 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/'에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값이 추가되었습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/'에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값이 추가되었습니다.
  • 'results/items/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성에 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 추가했습니다.
  • 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 '/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성에 추가했습니다.
  • 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 '/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성에 추가했습니다.
  • 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성에 추가했습니다.
  • 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값이 'results/items/oneOf[subschema #1: 기타 이벤트]/eventTypeName/oneOf[subschema #12: 그룹 이벤트 유형]/' 응답 속성에 추가되었습니다.
  • 새로운 'WEBHOOK_TEMPLATE_RENDER_FAILED' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 엔드포인트 추가됨
  • 엔드포인트 추가됨

2026년 7월 08일 릴리스

  • 응답에 선택 사항 속성 'results/items/instantUserProvisioningDisabled'을 추가했습니다.
  • 응답에 선택 사항 속성 'instantUserProvisioningDisabled' 추가
  • 요청 속성 'identityProviderId'가 널허지게 되었습니다.
  • 요청 속성 'postAuthRoleGrants/items/'가 널을 허용하도록 변경되었습니다.
  • 응답에 선택 사항 속성 'instantUserProvisioningDisabled' 추가
  • 새로운 선택적 요청 속성 'instantUserProvisioningDisabled' 추가
  • 응답에 선택 사항 속성 'results/items/associatedOrgs/items/instantUserProvisioningDisabled, results/items/oneOf[subschema #1: SAML]/associatedOrgs/items/instantUserProvisioningDisabled, results/items/oneOf[subschema #2: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, results/items/oneOf[subschema #3: OIDC 워크로드]/associatedOrgs/items/instantUserProvisioningDisabled'을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: OIDC WORKFORCE]/설명'이 널을 허용하게 되었습니다.
  • 요청 속성 '/oneOf[subschema #2: OIDC 워크로드]/설명'이 널할이 되었습니다.
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 응답에 선택 속성 '/oneOf[subschema #1: OIDC 워크포스]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #2: OIDC 워크로드]/associatedOrgs/items/instantUserProvisioningDisabled, associatedOrgs/items/instantUserProvisioningDisabled'을 추가했습니다.
  • 응답에 선택 속성 '/oneOf[subschema #1: SAML]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #2: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #3: OIDC WORKLOAD]/associatedOrgs/items/instantUserProvisioningDisabled, associatedOrgs/items/instantUserProvisioningDisabled'을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: SAML]/description'이(u)는 널을 허용하도록 변경되었습니다.
  • 요청 속성 '/oneOf[subschema #1: SAML]/status'가 널헀 값을 가지게 되었습니다.
  • 요청 속성 '/oneOf[subschema #2: OIDC WORKFORCE]/설명'이 널을 허용하게 되었습니다.
  • 요청 속성 '/oneOf[subschema #3: OIDC 워크로드]/설명'이 널할이 되었습니다.
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 응답에 선택 속성 '/oneOf[subschema #1: SAML]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #2: OIDC WORKFORCE]/associatedOrgs/items/instantUserProvisioningDisabled, /oneOf[subschema #3: OIDC WORKLOAD]/associatedOrgs/items/instantUserProvisioningDisabled, associatedOrgs/items/instantUserProvisioningDisabled'을 추가했습니다.
  • 응답에 선택 사항 속성 'results/items/oneOf[subschema #10: 지능형 워크로드 관리 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #10: 지능형 워크로드 관리 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #11: NDS 자동 확장 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #11: NDS 자동 확장 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #12: X509 사용자 인증 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #12: X509 사용자 인증 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #13: 복제본 세트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #13: 복제본 세트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #14: 복제본 세트 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #14: 복제본 세트 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #15: 서버리스 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #15: 서버리스 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #16: Flex 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #16: Flex 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #17: 스트림 프로세서 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #17: 스트림 프로세서 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #18: 스트림 프로세서 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #18: 스트림 프로세서 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #1: 기타 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #1: 기타 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #2: 앱 Services 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #2: 앱 Services 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #3: 앱 Services 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #3: 앱 Services 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #5: 클러스터 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #5: 클러스터 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #7: 암호화 키 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #7: 암호화 키 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #8: 호스트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #8: 호스트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #9: 호스트 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #9: 호스트 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate'을 추가했습니다.
  • 응답에 선택 속성 '/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'을 추가했습니다.
  • 새로운 선택 사항 요청 속성 '/oneOf[subschema #10: Intelligent 워크로드 관리 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent 워크로드 관리 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS 자동 확장 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS 자동 확장 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 사용자 인증 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 사용자 인증 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: 복제본 세트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: 복제본 세트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: 복제본 세트 Threshold 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: 복제본 세트 Threshold 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: 서버리스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: 서버리스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: 앱 서비스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: 앱 서비스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: 앱 서비스 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: 앱 서비스 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: 청구 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: 청구 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: 클러스터 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: 클러스터 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps 백업 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps 백업 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: 암호화 키 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: 암호화 키 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: 호스트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: 호스트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: 호스트 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: 호스트 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'를 추가했습니다.
  • 응답에 선택 속성 '/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'을 추가했습니다.
  • 응답에 선택 속성 '/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'을 추가했습니다.
  • 응답에 선택 속성 '/oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent Workload Management Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS Auto-Scaling Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 User Authentication Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: Replica Set Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: Replica Set Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: Serverless Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other Alert Configurations]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: App Services Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: App Services Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: Billing Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: Cluster Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps Backup Threshold Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: Encryption Key Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: Host Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: Host Metric Alert Configuration]/notifications/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'을 추가했습니다.
  • 새로운 선택 사항 요청 속성 '/oneOf[subschema #10: Intelligent 워크로드 관리 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #10: Intelligent 워크로드 관리 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #11: NDS 자동 확장 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #11: NDS 자동 확장 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #12: X509 사용자 인증 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #12: X509 사용자 인증 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #13: 복제본 세트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #13: 복제본 세트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #14: 복제본 세트 Threshold 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #14: 복제본 세트 Threshold 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #15: 서버리스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #15: 서버리스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #16: Flex 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #16: Flex 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #17: Stream Processor 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #17: Stream Processor 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #18: Stream Processor 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #18: Stream Processor 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #1: Any Other 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #1: Any Other 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #2: 앱 서비스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #2: 앱 서비스 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #3: 앱 서비스 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #3: 앱 서비스 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #4: 청구 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #4: 청구 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #5: 클러스터 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #5: 클러스터 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #6: Cps 백업 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #6: Cps 백업 임계값 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #7: 암호화 키 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #7: 암호화 키 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #8: 호스트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #8: 호스트 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate, /oneOf[subschema #9: 호스트 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookBodyTemplate, /oneOf[subschema #9: 호스트 지표 경고 구성]/알림/items/oneOf[subschema #14: Webhook Notification]/webhookHeadersTemplate'를 추가했습니다.
  • 응답에 선택 사항 속성 'results/items/oneOf[subschema #10: 지능형 워크로드 관리 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #10: 지능형 워크로드 관리 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #11: NDS 자동 확장 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #11: NDS 자동 확장 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #12: X509 사용자 인증 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #12: X509 사용자 인증 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #13: 복제본 세트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #13: 복제본 세트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #14: 복제본 세트 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #14: 복제본 세트 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #15: 서버리스 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #15: 서버리스 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #16: Flex 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #16: Flex 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #17: 스트림 프로세서 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #17: 스트림 프로세서 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #18: 스트림 프로세서 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #18: 스트림 프로세서 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #1: 기타 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #1: 기타 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #2: 앱 Services 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #2: 앱 Services 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #3: 앱 Services 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #3: 앱 Services 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #5: 클러스터 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #5: 클러스터 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #7: 암호화 키 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #7: 암호화 키 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #8: 호스트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #8: 호스트 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate, results/items/oneOf[subschema #9: 호스트 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookBodyTemplate, results/items/oneOf[subschema #9: 호스트 지표 경고 구성]/notifications/items/oneOf[subschema #14: 웹훅 알림]/webhookHeadersTemplate'을 추가했습니다.
  • 요청의 보디가 널이 되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/analyticsSpecs/instanceSize'요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 '열거형 값 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 이란 새로운 열거형 값을 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'에 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 값 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 추가되었습니다.
  • 요청 속성 'clusterDescription/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새 '버전 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 추가
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveAnalyticsSpecs/instanceSize'에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 'searchDeploymentSpec/instanceSize'에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 새 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/electableSpecs/instanceSize' 의 응답 속성에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 이란 새로운 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 새로운 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/readOnlySpecs/instanceSize' 의 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 지역 복제 사양]/electableSpecs/instanceSize'의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 '열거형 값 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '결과/items/복제사양/items/지역 구성/items/oneOf[섑스키마 #1: Amazon Web Services 지역 복제 사양]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 추가했습니다.
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/instanceSize '응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'results/items/복제 사양/items/지역 구성/items/oneOf[subschema #2: Azure 지역 복제 사양]/유효 선택 가능 사양/인스턴스 크기' 응답 속성에 추가했습니다.
  • 응답 속성 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 의 응답 속성에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로 추가되었습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 이란 새로운 열거형 값을 'results/items/복제Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '유효복제사양/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 이란 새로운 열거형 값을 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 의 응답 속성에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '복제사양/items/지역 구성/items/oneOf[섑스키마 #2: Azure 지역 복제 사양]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 추가
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/readOnlySpecs/instanceSize'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize' 의 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로 추가되었습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '요청 속성' effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveAnalyticsSpecs/instanceSize에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 '열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '응답 속성 'providerSettings/oneOf[subschema #3: 클러스터에 대한 클라우드 서비스 제공자 설정]/instanceSizeName'에 새로운 '열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 추가되었습니다.
  • 요청 속성 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'providerSettings/oneOf[subschema #3: 클러스터용 클라우드 서비스 제공자 속성]/autoScaling/compute/minInstanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '제공자Settings/oneOf[subschema #3: 클라우드 Service 제공자 Settings for a 클러스터]/instanceSizeName'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '유효복제사양/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 이란 새로운 열거형 값을 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 의 응답 속성에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '복제사양/items/지역 구성/items/oneOf[섑스키마 #2: Azure 지역 복제 사양]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '유효복제사양/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 이란 새로운 열거형 값을 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize' 응답 속성에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 의 응답 속성에 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 의 응답 속성에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 의 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '복제사양/items/지역 구성/items/oneOf[섑스키마 #2: Azure 지역 복제 사양]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize' 응답 속성에 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize' 응답 속성에 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/readOnlySpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 추가
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/readOnlySpecs/instanceSize'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize' 의 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로 추가되었습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '요청 속성' effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveAnalyticsSpecs/instanceSize에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 '열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청의 보디가 널이 되었습니다.
  • 'EffectiveSpecs/items/instanceSize' 응답 속성 에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 'specs/items/instanceSize' 응답 속성에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 요청 속성 'defaultNodeCount'가 null이 될 수 있게 되었습니다.
  • 요청 속성 'specs/items/cloudProvider'가 null이 될 수 있게 됨
  • 요청 속성 'specs/items/nodeCount'가 널을 허용하도록 변경되었습니다.
  • 요청 속성 'specs/items/regionName'이(가) nullable이(가) 되었습니다.
  • 'EffectiveSpecs/items/instanceSize' 응답 속성 에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 'specs/items/instanceSize' 응답 속성에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 요청 속성 'specs/items/instanceSize'에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 요청 속성 'defaultNodeCount'가 null이 될 수 있게 되었습니다.
  • 요청 속성 'specs/items/cloudProvider'가 null이 될 수 있게 됨
  • 요청 속성 'specs/items/nodeCount'가 널을 허용하도록 변경되었습니다.
  • 요청 속성 'specs/items/regionName'이(가) nullable이(가) 되었습니다.
  • 'EffectiveSpecs/items/instanceSize' 응답 속성 에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 'specs/items/instanceSize' 응답 속성에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 요청 속성 'specs/items/instanceSize'에 새로운 'S10_HIGHCPU' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterName'이(u)는 널이 될 수 있게 되었습니다.
  • 'results/items/oneOf[subschema #1: Azure]/vnetName' 응답의 속성 패턴이 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • 요청 속성 '/oneOf[subschema #1: AZURE]/vnetName'의 패턴을 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경
  • '/oneOf[subschema #1: AZURE]/vnetName' 응답의 속성 패턴이 '^([-\w._()])+$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • 'results/items/oneOf[subschema #1: Azure]/vnetName' 응답의 속성 패턴이 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • '/oneOf[subschema #1: AZURE]/vnetName' 응답의 속성 패턴이 '^([-\w._()])+$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • 요청 속성 '/oneOf[subschema #1: AZURE]/vnetName'의 패턴을 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경
  • '/oneOf[subschema #1: AZURE]/vnetName' 응답의 속성 패턴이 '^([-\w._()])+$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • '/items/actions/items/조치' 응답 속성에 새로운 'ANALYZE' 열거형 값을 추가했습니다.
  • '/items/actions/items/ 조치' 응답 속성에 새로운 '분석' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/action'에 새로운 'ANALYZE' 열거형 값을 추가했습니다.
  • '/items/actions/items/ 조치' 응답 속성에 새로운 '분석' 열거형 값을 추가했습니다.
  • '/items/actions/items/ 조치' 응답 속성에 새로운 '분석' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/action'에 새로운 'ANALYZE' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 새로운 'AGENT_FORCE_RESTART_REQUESTED' 열거형 값을 추가했습니다.
  • 새로운 'CPS_RESTORE_AUTH_AUDIT' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #7: Disk Backup Event Types]/' 응답 속성에 추가했습니다.
  • 답변 속성 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/'에 새로운 'STREAM_PROCESSOR_STARTED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #25: Stream Processor Events]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_STARTED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 새로운 'AGENT_FORCE_RESTART_REQUESTED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #7: Disk Backup Event Types]/' 응답 속성에 새로운 'CPS_RESTORE_AUTH_AUDIT' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #30: Stream Processor Event Types]/' 응답 속성에 새로운 'STREAM_PROCESSOR_STARTED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #25: Stream Processor Events]/eventTypeName' 응답 속성에 새로운 'STREAM_PROCESSOR_STARTED' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 추가
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/readOnlySpecs/instanceSize'에 새 열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize' 의 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로 추가되었습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • '요청 속성' effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveAnalyticsSpecs/instanceSize에 '열거형 값' M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 새로 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가되었습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값이 추가됨
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP 인스턴스 크기]/' 요청 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • '요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 '열거형 값 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2'이 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/instanceSize'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 지역 복제 사양]/readOnlySpecs/instanceSize'에 새로 추가된 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #3: GCP Instance Sizes]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/max인스턴스Size/oneOf[subschema #3: GCP 인스턴스 Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/autoScaling/compute/min인스턴스Size/oneOf[subschema #3: GCP Instance Sizes]/'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveAnalyticsSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveElectableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/effectiveReadOnlySpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/electableSpecs/instanceSize'에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값 추가
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/readOnlySpecs/instanceSize'에 새 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/instanceSize'에 새로운 '열거형 M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 값을 추가했습니다.
  • 응답에 선택 속성 'results/items/oneOf[subschema #7: WEBHOOK]/bodyTemplate, results/items/oneOf[subschema #7: WEBHOOK]/headersTemplate'을 추가했습니다.
  • 응답에 '/oneOf[subschema #7: WEBHOOK]/bodyTemplate, /oneOf[subschema #7: WEBHOOK]/headersTemplate'의 선택 사항 속성이 추가되었습니다.
  • 응답에 선택 속성 'results/items/oneOf[subschema #7: WEBHOOK]/bodyTemplate, results/items/oneOf[subschema #7: WEBHOOK]/headersTemplate'을 추가했습니다.
  • 새 선택 요청 속성 '/oneOf[subschema #7: WEBHOOK]/bodyTemplate, /oneOf[subschema #7: WEBHOOK]/headersTemplate'을 추가했습니다.
  • 응답에 선택 속성 'results/items/oneOf[subschema #7: WEBHOOK]/bodyTemplate, results/items/oneOf[subschema #7: WEBHOOK]/headersTemplate'을 추가했습니다.
  • 새 선택 요청 속성 '/oneOf[subschema #7: WEBHOOK]/bodyTemplate, /oneOf[subschema #7: WEBHOOK]/headersTemplate'을 추가했습니다.
  • 요청 속성 'destination/privateLinkId'가 널이 되었습니다.
  • 요청 속성 '샤딩'이 null이 될 수 있게 되었습니다.
  • 요청 속성 'source/caCertificatePath'가 널헐 가능해졌습니다.
  • 요청 속성 'source/password'가 널헐 값을 허용하게 되었습니다.
  • 요청 속성 'source/username'이(u)가 널이 되었습니다.
  • 요청 속성 'destination/privateLinkId'가 널이 되었습니다.
  • 요청 속성 '샤딩'이 null이 될 수 있게 되었습니다.
  • 요청 속성 'source/caCertificatePath'가 널헐 가능해졌습니다.
  • 요청 속성 'source/password'가 널헐 값을 허용하게 되었습니다.
  • 요청 속성 'source/username'이(u)가 널이 되었습니다.
  • 'results/items/instanceSize/oneOf[subschema #3: GCP Instance Sizes]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #2: Azure]/vnetName' 응답의 속성 패턴이 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • 요청 속성 '/oneOf[subschema #2: AZURE]/vnetName'의 패턴을 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경
  • '/oneOf[subschema #2: AZURE]/vnetName' 응답의 속성 패턴이 '^([-\w._()])+$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • '/oneOf[subschema #2: AZURE]/vnetName' 응답의 속성 패턴이 '^([-\w._()])+$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • 요청 속성 '/oneOf[subschema #2: AZURE]/vnetName'의 패턴을 '^([-\w._()])$'에서 '^([-\w._()])+$'로 변경
  • '/oneOf[subschema #2: AZURE]/vnetName' 응답의 속성 패턴이 '^([-\w._()])+$'에서 '^([-\w._()])+$'로 변경되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 'results/items/providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 추가했습니다.
  • 'providerSettings/effectiveInstanceSizeName/oneOf[subschema #3: GCP 인스턴스 크기]/' 응답 속성에 새로운 'M140_GEN_2, M200_GEN_2, M30_GEN_2, M40_GEN_2, M50_GEN_2, M60_GEN_2, M80_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R80_GEN_2' 열거형 값을 추가했습니다.
  • 새로운 선택 사항 'query' 요청 매개변수 'includeSystemManaged'가 추가되었습니다.
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 요청 속성 'name'이(u)가 nullable이 되었습니다.
  • 요청 속성 '/items/cidrBlock'이(u)가 널이 될 수 있게 되었습니다.
  • '/items/ipAddress' 요청 속성이 널할 수 있게 되었습니다.
  • 요청 속성 '/items/lastUsedAddress'가 널할 수 있게 되었습니다.
  • 요청 속성 '/items/lastUsedAt'이 널이 되었습니다.
  • 요청 속성 'connections/items/clusterGroupId'가 널을 허용합니다.
  • 요청 속성 'connections/items/dbRoleToExecute'이(u)가 nullable이 되었습니다.
  • 요청 속성 'processorStatus/mode'가 null이 될 수 있게 되었습니다.
  • 요청 속성 'processorStatus/리전'이 null이 될 수 있게 되었습니다.
  • 요청 속성 '/clusterGroupId'이(u)가 널이 될 수 있게 되었습니다.
  • 요청 속성 '/dbRoleToExecute'가 null이 될 수 있게 되었습니다.
  • 요청 속성 '/clusterGroupId'이(u)가 널이 될 수 있게 되었습니다.
  • 요청 속성 '/dbRoleToExecute'가 null이 될 수 있게 되었습니다.
  • 요청 속성 '/clusterGroupId'이(u)가 널이 될 수 있게 되었습니다.
  • 요청 속성 '/dbRoleToExecute'가 null이 될 수 있게 되었습니다.
  • 요청 속성 '/clusterGroupId'이(u)가 널이 될 수 있게 되었습니다.
  • 요청 속성 '/dbRoleToExecute'가 null이 될 수 있게 되었습니다.
  • 요청 속성 'apiKey/역할/items/'이(u)는 null이 될 수 있게 되었습니다.
  • 요청 속성 'serviceAccount'가 널할 수 있게 되었습니다.
  • 요청 속성 'roles/items/'가 널 허용이 되었습니다.
  • 요청 속성 'roles/items/'가 널 허용이 되었습니다.
  • 요청 속성 'services/items/'에 새로운 'AI 모델 API' 열거형 값 추가
  • 요청 속성 'services/items/'의 열거형 값 'AI 모델'을 제거했습니다.
  • 엔드포인트 추가됨
  • 엔드포인트 추가됨
  • 'results/items/oneOf[subschema #7: Atlas 조직 감사]/eventTypeName' 응답 속성에 새로운 'ATLAS_MAINTENANCE_FLEET_ACTIVE_WAVE_CLOSED_BY_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성에 새로운 'OPERATIONS_CONTACT_MODIFIED' 열거형 값을 추가했습니다.
  • 새로운 'ATLAS_MAINTENANCE_FLEET_ACTIVE_WAVE_CLOSED_BY_ADMIN' 열거형 값을 '/oneOf[subschema #7: Atlas 조직 감사]/eventTypeName' 응답 속성에 추가했습니다.
  • '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성에 새로운 'OPERATIONS_CONTACT_MODIFIED' 열거형 값을 추가했습니다.
  • 요청 속성 'filters/skuServices/items/'에 새로운 'AI 모델 API' 열거형 값 추가
  • 요청 속성 'filters/skuServices/items/'의 열거형 값 'AI 모델' 제거
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 요청 속성 'name'이(u)가 nullable이 되었습니다.
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 새로운 선택 사항 'query' 요청 매개변수 'includeSystemManaged'가 추가되었습니다.
  • 요청의 보디가 널이 되었습니다.
  • 요청 속성 '설명'이 null이 될 수 있게 되었습니다.
  • 요청 속성 'name'이(u)가 nullable이 되었습니다.
  • 요청 속성 '/items/cidrBlock'이(u)가 널이 될 수 있게 되었습니다.
  • '/items/ipAddress' 요청 속성이 널할 수 있게 되었습니다.
  • 요청 속성 '/items/lastUsedAddress'가 널할 수 있게 되었습니다.
  • 요청 속성 '/items/lastUsedAt'이 널이 되었습니다.
  • 응답에 선택 속성 'operationsContact'를 추가했습니다.
  • 응답에 선택 속성 'operationsContact'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'operationsContact' 추가

2026년 6월 25일 출시

  • 응답에 대한 'results/items/oneOf[subschema #1: 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #7: OAuth 감사 유형' 을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #7: OAuth Audit Types'를 추가했습니다.

2026년 6월 22일 출시

  • 새로운 'SEOUL_KOR' 열거형 값을 'results/items/dataProcessRegion/region/' 응답 속성에 추가했습니다.
  • 응답에 선택 사항 속성 'results/items/failoverRegions'을 추가했습니다.
  • 'dataProcessRegion/리전/' 응답 속성에 새로운 'SEOUL_KOR' 열거형 값을 추가했습니다.
  • 요청 속성 'dataProcessRegion/리전/'에 새로운 'SEOUL_KOR' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'failoverRegions' 추가
  • 새로운 선택 사항 요청 속성 'failoverRegions'이(가) 추가되었습니다.
  • 'dataProcessRegion/리전/' 응답 속성에 새로운 'SEOUL_KOR' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'failoverRegions' 추가
  • 'dataProcessRegion/리전/' 응답 속성에 새로운 'SEOUL_KOR' 열거형 값을 추가했습니다.
  • 요청 속성 'region/'에 새로운 'SEOUL_KOR' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'failoverRegions' 추가
  • 새로운 선택 사항 요청 속성 'failoverRegions'이(가) 추가되었습니다.
  • 응답에 선택 사항 속성 'failoverEnabled'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'failoverEnabled'가 추가되었습니다.
  • 응답에 선택 사항 속성 'eligibleForFailover, failoverEnabled'을 추가했습니다.
  • 응답에 선택 사항 속성 'eligibleForFailover, failoverEnabled'을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'failoverEnabled'가 추가되었습니다.
  • 응답에 선택 사항 속성 'results/items/eligibleForFailover, results/items/failoverEnabled'을 추가했습니다.
  • 'dataProcessRegion/리전/' 응답 속성에 새로운 'SEOUL_KOR' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'failoverRegions' 추가

2026년 6월 17일 출시

  • 응답에 선택 사항 속성 'results/items/vpcRegionName' 추가
  • 응답에 선택 사항 속성 'vpcRegionName'을 추가했습니다.
  • 새로운 선택 요청 속성 'vpcRegionName' 추가
  • 응답에 선택 사항 속성 'vpcRegionName'을 추가했습니다.
  • 요청 속성 'clusterDescription/diskWarmingMode'에 새 'ENHANCED_FULLY_WARMED' 열거형 값을 추가했습니다.
  • 'results/items/diskWarmingMode' 응답 속성에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값 추가
  • 'diskWarmingMode' 응답 속성에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값을 추가했습니다.
  • 요청 속성 'diskWarmingMode'에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값 추가
  • 'diskWarmingMode' 응답 속성에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값을 추가했습니다.
  • 요청 속성 'diskWarmingMode'에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값 추가
  • 'diskWarmingMode' 응답 속성에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값을 추가했습니다.
  • 'diskWarmingMode' 응답 속성에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값을 추가했습니다.
  • 요청 속성 'diskWarmingMode'에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값 추가
  • 응답에 선택 사항 속성 'effectiveSpecs'를 추가했습니다.
  • 응답에 선택 사항 속성 'effectiveSpecs'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'defaultNodeCount, specs/items/cloudProvider, specs/items/regionName'을 추가했습니다.
  • 응답에 선택 사항 속성 'effectiveSpecs'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'defaultNodeCount, specs/items/cloudProvider, specs/items/regionName'을 추가했습니다.
  • '/items/actions/items/ 조치' 응답 속성에 새로운 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 열거형 값을 추가했습니다.
  • 'actions/items/action' 응답 속성에 새로운 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/ 조치 ' 에 새로운 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 열거형 값을 추가했습니다.
  • 'actions/items/action' 응답 속성에 새로운 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 열거형 값을 추가했습니다.
  • 'actions/items/action' 응답 속성에 새로운 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/ 조치 ' 에 새로운 'CREATE_SEARCH_INDEX, DROP_SEARCH_INDEX, LIST_SEARCH_INDEXES, UPDATE_SEARCH_INDEX' 열거형 값을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #39: AI 모델 API 이벤트 유형'을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #39: Ai Models 이벤트 유형' 제거
  • 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 새로운 'CLUSTER_MONGODB_VERSION_UPDATED, PROJECT_ENABLE_DATA_VALIDATION_UPDATED' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #39: AI Models APIs Event Types'를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #39: AI 모델스 이벤트 타입스'를 제거했습니다.
  • 새로운 'CLUSTER_MONGODB_VERSION_UPDATED, PROJECT_ENABLE_DATA_VALIDATION_UPDATED' 열거형 값을 '/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 추가했습니다.
  • 요청 속성 'diskWarmingMode'에 새로운 'ENHANCED_FULLY_WARMED' 열거형 값 추가
  • 응답에 선택 사항 속성 'isDataValidationEnabled' 추가
  • 응답에 선택 사항 속성 'isDataValidationEnabled' 추가
  • 새로운 선택 사항 요청 속성 'isDataValidationEnabled'을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'processorStatus' 추가
  • 새로운 선택 사항 요청 속성 '페일오버' 추가
  • 응답에 대한 'results/items/oneOf[subschema #1: 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #6: AI 모델 API 이벤트 유형'을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #6: Ai Models 이벤트 유형' 제거
  • 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성에 새로운 'ORG_DELEGATION_SETTINGS_UPDATED' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #6: AI Models APIs Event Types'를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #6: AI 모델스 이벤트 타입스'를 제거했습니다.
  • '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성에 새로운 'ORG_DELEGATION_SETTINGS_UPDATED' 열거형 값을 추가했습니다.
  • 응답에 선택 사항 속성 'results/items/additionalData'를 추가했습니다.

2026년 6월 02일 출시

  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effective복제Specs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새 열거형 값 'HIGH_PERFORMANCE'를 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsSpecs/oneOf[subschema #1: AWS Cluster hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'clusterDescription/복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'clusterDescription/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새 'HIGH_PERFORMANCE' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'의 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어에 추가되었습니다. 설정]/ebsVolumeType '응답 속성
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. ' 응답 속성
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/ebsVolumeType에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. ' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 '열거형 HIGH_PERFORMANCE' 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'의 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새 열거형 값 'HIGH_PERFORMANCE'를 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 '유효한 복제 사양/items/리전 구성/items/oneOf[subschema #3: GCP 리전 복제 사양]/유효한 읽기 전용 사양/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 요청 속성에 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값이 추가되었습니다.
  • 요청 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다. 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 요청 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'providerSettings/oneOf[subschema #1: 클라우드 서비스 제공자 클러스터 설정]/volumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'providerSettings/oneOf[subschema #1: 클라우드 서비스 제공자 클러스터 설정]/volumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. ' 응답 속성
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/ebsVolumeType에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. ' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 '열거형 HIGH_PERFORMANCE' 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'의 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 '고성능' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. ' 응답 속성
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMance' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/ebsVolumeType에 추가되었습니다. ' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/ebsVolumeType에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. ' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 '열거형 HIGH_PERFORMANCE' 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'의 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 응답 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType' 응답 속성에 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType' 응답 속성에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새 열거형 값 'HIGH_PERFORMANCE'를 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 '유효한 복제 사양/items/리전 구성/items/oneOf[subschema #3: GCP 리전 복제 사양]/유효한 읽기 전용 사양/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 요청 속성에 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값이 추가되었습니다.
  • 요청 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다. 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 요청 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새 열거형 값 'HIGH_PERFORMANCE'를 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 '유효한 복제 사양/items/리전 구성/items/oneOf[subschema #3: GCP 리전 복제 사양]/유효한 읽기 전용 사양/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 요청 속성에 추가했습니다.
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional 복제 Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]에 새로운 'HIGH_PERFORMance' 열거형 값을 추가했습니다. /ebsVolumeType'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값이 추가되었습니다.
  • 요청 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다. 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType' 요청 속성에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE'열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새 '고성능' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/electableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값이 추가되었습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 지역 복제 사양]/electableSpecs/oneOf[subschema #1: Amazon Web Services 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.
  • 새로운 'HIGH_PERFORMANCE' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ebsVolumeType'에 새로운 'HIGH_PERFORMANCE' 열거형 값을 추가했습니다.

28 5월 2026 출시

  • 상태가 '401'인 응답에 대해 미디어 유형 ' 애플리케이션/json'을 추가했습니다.
  • 응답에 대한 '/items/' 응답 속성 'oneOf' 목록에 'subschema #8: NDS 자동 확장 매처 필드'를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema 응답 속성 #{1]/' Atlas 응답 속성 감사 #7:
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값이 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas Audit types]/' 응답 속성 에 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 Types]/'에 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값이 추가되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값이 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas Audit types]/' 응답 속성 에 추가되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값이 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas Audit types]/' 응답 속성 에 추가되었습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값이 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas Audit types]/' 응답 속성 에 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: Atlas 감사 Types]/'에 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값이 추가되었습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값을 'results/items/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema 응답 속성 #7: Atlas Audit Types]/' 응답 속성
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값을 'results/items/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema 응답 속성 #7: Atlas Audit Types]/' 응답 속성
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값을 '/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 추가되었습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값을 '/oneOf[subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #7: Atlas 감사 유형]/' 응답 속성에 추가되었습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/NDSAutoscalingAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'LOG_STREAMING_EXPORT_FAILED_NONRERYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema 응답 속성 #{1]/' Atlas 응답 속성 감사 #7:
  • 미디어 유형 ' 애플리케이션/vnd.atlas.2024-05-30+json' 응답 상태 '503'에 대해 보다 일반적인 미디어 유형 ' 애플리케이션/json'으로 변경되었습니다.
  • 미디어 유형 ' 애플리케이션/vnd.atlas.2024-05-30+json' 응답 상태 '503'에 대해 보다 일반적인 미디어 유형 ' 애플리케이션/json'으로 변경되었습니다.
  • 미디어 유형 ' 애플리케이션/vnd.atlas.2024-05-30+json' 응답 상태 '503'에 대해 보다 일반적인 미디어 유형 ' 애플리케이션/json'으로 변경되었습니다.
  • 'results/items/eventTypeName' 응답 속성 에 새로운 'CHARTS_DASHBOARD_EXPORTED, CHARTS_DASHBOARD_EXPORT_FAILED, CHARTS_DASHBOARD_IMPORTED, CHARTS_DASHBOARD_IMPORT_FAILED' 열거형 값이 추가되었습니다.
  • Added the new 'CLUSTER_APPLY_CONNECTION_RATE_LIMIT_REQUESTED, LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED, LOG_STREAMING_EXPORT_RECOVERED, LOG_STREAMING_REPLAY_COMPLETE, LOG_STREAMING_REPLAY_STARTED' 열거형 values to the 'results/items/oneOf[subschema #15: Atlas Project Audits]/eventTypeName' response 속성
  • '/eventTypeName' 응답 속성 에 새로운 'CHARTS_DASHBOARD_EXPORTED, CHARTS_DASHBOARD_EXPORT_FAILED, CHARTS_DASHBOARD_IMPORTED, CHARTS_DASHBOARD_IMPORT_FAILED' 열거형 값이 추가되었습니다.
  • Added the new 'CLUSTER_APPLY_CONNECTION_RATE_LIMIT_REQUESTED, LOG_STREAMING_EXPORT_FAILED_NONRETRYABLE, LOG_STREAMING_EXPORT_FAILED_RETRIES_EXHAUSTED, LOG_STREAMING_EXPORT_RECOVERED, LOG_STREAMING_REPLAY_COMPLETE, LOG_STREAMING_REPLAY_STARTED' 열거형 values to the '/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' response 속성
  • 응답에 선택적 속성 'EffectiveWaveAssignment, WaveAssignment'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'WaveAssignment'가 추가되었습니다.
  • 응답에 선택적 속성 'results/items/roles'를 추가했습니다.

21 5월 2026 출시

  • 'results/items/oneOf[subschema #15: Atlas Project Audits]/eventTypeName' 응답 속성 에 새로운 'PROJECT_COLLECT_DATABASE_STATISTICS_UPDATED, SEARCH_HOST_DISABLE_FTS, SEARCH_HOST_PAUSE_ALL_INITIAL_SYNCS' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성 에 새로운 'PROJECT_COLLECT_DATABASE_STATISTICS_UPDATED, SEARCH_HOST_DISABLE_FTS, SEARCH_HOST_PAUSE_ALL_INITIAL_SYNCS' 열거형 값을 추가했습니다.

12 5월 2026 출시

  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #15: Host Event types]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 'results/items/oneOf[subschema #8: 호스트 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/'에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/'에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 'results/items/oneOf[subschema #8: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 'results/items/oneOf[subschema #8: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #3: 호스팅하다 경고]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #7: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #8: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #3: 호스팅하다 경고]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #7: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #8: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #15: Host Event types]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 'results/items/oneOf[subschema #8: 호스트 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #13: 호스트 이벤트]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_PROCESS_NOT_THROTTLING, HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_PROCESS_NOT_THROTTLING, HOST_SEARCH_PROCESS_THROTTLING' 열거형 값을 '/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 추가했습니다.

07 5월 2026 출시

  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.
  • 결제 정보를 찾을 수 없는 경우 사용자가 결제 수단을 추가할 수 있는 링크를 포함하도록 NO_PAYMENT_INFORMATION_FOUND 오류 메시지를 업데이트했습니다.

06 5월 2026 출시

  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: 자동 확장 Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: 기타 모든 경고 구성]/eventTypeName/oneOf[subschema #13: 자동 확장 감사 유형]/'에 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: Auto Scaling Audit Types]/' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: 기타 모든 경고 구성]/eventTypeName/oneOf[subschema #13: 자동 확장 감사 유형]/'에 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/스키마/FlexMetricAlert'가 추가되었습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts -> subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #16: 자동 확장 Audit types]/' 응답 속성
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/스키마/FlexMetricAlert'가 추가되었습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts -> subschema #8: Any Other Alerts]/eventTypeName/oneOf[subschema #16: 자동 확장 Audit types]/' 응답 속성
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/FlexMetricAlert'를 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #7: Any 기타 경고 -> 하위 스키마 #8: Any 기타 경고]/eventTypeName/oneOf[subschema #16: 자동 확장 감사 유형에 추가했습니다. ]/' 응답 속성
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/FlexMetricAlert'를 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #7: Any 기타 경고 -> 하위 스키마 #8: Any 기타 경고]/eventTypeName/oneOf[subschema #16: 자동 확장 감사 유형에 추가했습니다. ]/' 응답 속성
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: 자동 확장 Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성)
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기에 열거형 . ]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize ' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize ' 응답 속성
  • 선택 사항 속성 'results/items/adaptiveCapacity, results/items/effectiveReplicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS Cluster hardware Settings]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/effectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput'을 응답에 추가합니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성에 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ 요청 속성 에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 선택 사항 속성 'adoptiveCapacity, 효과적인ReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, expiresReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정] /diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThrou ghput, 실효 복제 사양/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 실효복제 사양/items/regionConfigs/items/ oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 H ardware 설정]/diskThroughput, 효과적인 복제 사양/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/ oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[sub schema #1: AWS 클러스터 hardware 설정]/diskThroughput, refineReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정 ]/diskThroughput,fluentReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/ items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/ selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[ subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정 ]/diskThrou ghput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ diskThroughput, replication nSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양 ]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regio nConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/ oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput'을 응답에 추가합니다.
  • 새로운 선택 사항 요청 속성 'adaptiveCapacity'가 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 '제공자 설정/oneOf[subschema #1: 클라우드 서비스 제공자 설정 for a 클러스터]/autoScaling/compute/maxInstanceSize' 응답 속성에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 '제공자Settings/oneOf[subschema #1: 클라우드 Service 제공자 Settings for a 클러스터]/instanceSizeName' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/maxInstanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/autoScaling/compute/minInstanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/instanceSizeName'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'providerSettings/Effective인스턴스SizeName/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'providerSettings/EffectiveInstanceSizeName/oneOf[subschema #1: AWS Instance Sizes]/'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성에 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 선택 사항 속성 'adoptiveCapacity, 효과적인ReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, expiresReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정] /diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThrou ghput, 실효 복제 사양/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 실효복제 사양/items/regionConfigs/items/ oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 H ardware 설정]/diskThroughput, 효과적인 복제 사양/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/ oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[sub schema #1: AWS 클러스터 hardware 설정]/diskThroughput, refineReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정 ]/diskThroughput,fluentReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/ items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/ selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[ subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정 ]/diskThrou ghput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ diskThroughput, replication nSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양 ]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regio nConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/ oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput'을 응답에 추가합니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/electableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'effective복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware Settings]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional Replication Specifications]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 '복제Specs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성에 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/' 응답에 열거형 . 속성
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ 요청 속성 에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 선택 사항 속성 'adoptiveCapacity, 효과적인ReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, expiresReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정] /diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThrou ghput, 실효 복제 사양/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 실효복제 사양/items/regionConfigs/items/ oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 H ardware 설정]/diskThroughput, 효과적인 복제 사양/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/ regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/ oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[sub schema #1: AWS 클러스터 hardware 설정]/diskThroughput, refineReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정 ]/diskThroughput,fluentReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, 효과적인ReplicationSpecs/items/regionConfigs/ items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput,EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/ selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/ items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[ subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정 ]/diskThrou ghput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/ oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/ diskThroughput, replication nSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[ subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양 ]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regio nConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/ oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/diskThroughput, replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/diskThroughput'을 응답에 추가합니다.
  • 새로운 선택 사항 요청 속성 'adaptiveCapacity'가 추가되었습니다.
  • 요청 속성 'specs/items/nodeCount'가 선택 사항이 되었습니다.
  • 요청 속성 'specs/items/nodeCount'가 선택 사항이 되었습니다.
  • 응답 속성 'results/items/oneOf[subschema #19: ReplicaSet 이벤트]/replicaSetName'이 null 허용이 됨
  • 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #39: AI model Event Types]/' 응답 속성에 새로운 'AI_MODELS_API_KEY_UPDATED, AI_MODELS_RATE_LIMIT_RESET, AI_MODELS_RATE_LIMIT_UPDATED' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_MONGUARD_DISABLED, CLUSTER_MONGUARD_ENABLED, CLUSTER_RESET_FORCE_RECONFIG_REQUESTED, MAINTENANCE_WAVE_ASSIGNMENT_ADDED, MAINTENANCE_WAVE_ASSIGNMENT_MODIFIED, MAINTENANCE_WAVE_ASSIGNMENT_REMOVED' 열거형 값을 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 추가했습니다.
  • 'results/items/oneOf[subschema #16: 자동 확장 감사]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 추가했습니다.
  • 응답에 선택 사항 속성 'results/items/oneOf[subschema #19: ReplicaSet Events]/hostname'을 추가했습니다.
  • 응답 속성 '/oneOf[subschema #19: ReplicaSet Events]/replicaSetName'이 null 허용이 됨
  • '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #39: Ai model 이벤트 유형]/' 속성 에 새로운 'AI_MODELS_API_KEY_UPDATED, AI_MODELS_RATE_LIMIT_RESET, AI_MODELS_RATE_LIMIT_UPDATED' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_MONGUARD_DISABLED, CLUSTER_MONGUARD_ENABLED, CLUSTER_RESET_FORCE_RECONFIG_REQUESTED, MAINTENANCE_WAVE_ASSIGNMENT_ADDED, MAINTENANCE_WAVE_ASSIGNMENT_MODIFIED, MAINTENANCE_WAVE_ASSIGNMENT_REMOVED' 열거형 값을 '/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 속성에 추가했습니다.
  • 새로운 'CLUSTER_RESHARDING_COMPLETED' 열거형 값을 '/oneOf[subschema #16: 자동 확장 Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • 응답에 선택적 속성 '/oneOf[subschema #19: ReplicaSet 이벤트]/hostname'을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/effectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'effectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/max인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'EffectiveReplicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/selectableSpecs/oneOf[subschema #1: AWS Cluster Hardware Settings]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure Regional 복제 Specifications]/analyticsAutoScaling/compute/min인스턴스Size/oneOf[subschema #1: AWS 인스턴스 Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize'
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]/analyticsAutoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS Instance Sizes]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ 요청 속성 에 열거형 . '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 요청 열거형 값 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize/oneOf[subschema #1: AWS 인스턴스 크기]/ '
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 하드웨어 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize' 요청 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/selectableSpecs/oneOf[subschema #1: AWS 클러스터 hardware 설정]/instanceSize'
  • 새로운 선택 사항 요청 속성 'adaptiveCapacity'가 추가되었습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/instanceSize/oneOf[subschema #1: AWS Instance Sizes]/' 응답 속성 에 열거형 .
  • 요청 판별자 추가
  • 새로운 선택 사항 요청 속성 '/oneOf[subschema #1: AWS]/cloudProvider, /oneOf[subschema #2: AZURE]/cloudProvider, /oneOf[subschema #3: GCP]/cloudProvider, cloudProvider '
  • 'results/items/endpointId' 응답의 속성 패턴 '^vpce-[0-9af]{17}$'가 제거되었습니다.
  • 'results/items/ 제공자' 응답 속성 에 새로운 'AZURE' 열거형 값을 추가했습니다.
  • 요청 속성 'endpointId'에서 '^vpce-[0-9af]{17}$' 패턴 제거했습니다.
  • 'results/items/endpointId' 응답의 속성 패턴 '^vpce-[0-9af]{17}$'가 제거되었습니다.
  • 'results/items/ 제공자' 응답 속성 에 새로운 'AZURE' 열거형 값을 추가했습니다.
  • 요청 속성 '제공자'에 새로운 'AZURE' 열거형 값을 추가했습니다.
  • 'endpointId' 응답의 속성 패턴 '^vpce-[0-9af]{17}$'가 제거되었습니다.
  • ' 제공자' 응답 속성 에 새로운 'AZURE' 열거형 값을 추가했습니다.
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'results/items/providerSettings/EffectiveInstanceSizeName/oneOf[subschema #1: AWS Instance Sizes]/' 응답 속성 에 열거형 .
  • 새로운 'M140_GEN_2, M200_GEN_2, M200_NVME_GEN_2, M300_GEN_2, M30_GEN_2, M400_NVME_GEN_2, M40_GEN_2, M40_NVME_GEN_2, M50_GEN_2, M50_NVME_GEN_2, M60_GEN_2, M60_NVME_GEN_2, M80_GEN_2, M80_NVME_GEN_2, R200_GEN_2, R300_GEN_2, R400_GEN_2, R40_GEN_2, R50_GEN_2, R60_GEN_2, R700_GEN_2, R80_GEN_2' 열거형 값을 'providerSettings/Effective인스턴스SizeName/oneOf[subschema #1: AWS 인스턴스 Sizes]/' 응답 속성 에 열거형 .
  • 'results/items/dataProcessRegion/ 리전/' 응답 속성 에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • 요청 속성 'dataProcessRegion/ 리전 /'에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • 요청 속성 ' 리전 /'에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'PAIS_FRA, australiaeast,brazilsouth' 열거형 값을 추가했습니다.
  • ' 쿼리' 요청 매개 변수 'orgMembershipStatus'는 종료 날짜 없이 더 이상 사용되지 않습니다.
  • 응답 속성 'results/items/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 'results/items/invitationExpiresAt'이 선택 사항이 되었습니다.
  • 새로운 선택적 '쿼리' 요청 매개변수 'orgMembershipStatuses'가 추가되었습니다.
  • 'results/items/' 응답 속성 에 'INVITATION_REJECTED, INVITATION_EXPIRED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '201'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 새로운 선택적 '쿼리' 요청 매개변수 'orgMembershipStatuses'가 추가되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 응답 속성 에 새로운 'CREDIT_AWS_ACCOUNT_ID_MODIFIED, CREDIT_AWS_LICENSE_ARN_MODIFIED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #8: Organization Events]/eventTypeName' 응답 속성 에 새로운 'ORG_WAVE_ASSIGNMENT_mode_ENV_TAG_MAPPING, ORG_WAVE_ASSIGNMENT_mode_MANUAL' 열거형 값을 추가했습니다.
  • 새로운 'CREDIT_AWS_ACCOUNT_ID_MODIFIED, CREDIT_AWS_LICENSE_ARN_MODIFIED' 열거형 값을 '/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'ORG_WAVE_ASSIGNMENT_mode_ENV_TAG_MAPPING, ORG_WAVE_ASSIGNMENT_mode_MANUAL' 열거형 값을 추가했습니다.
  • ' 쿼리' 요청 매개 변수 'orgMembershipStatus'는 종료 날짜 없이 더 이상 사용되지 않습니다.
  • 응답 속성 'results/items/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 'results/items/invitationExpiresAt'이 선택 사항이 되었습니다.
  • 새로운 선택적 '쿼리' 요청 매개변수 'orgMembershipStatuses'가 추가되었습니다.
  • 'results/items/' 응답 속성 에 'INVITATION_EXPIRED, INVITATION_REJECTED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_REJECTED, INVITATION_EXPIRED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • ' 쿼리' 요청 매개 변수 'orgMembershipStatus'는 종료 날짜 없이 더 이상 사용되지 않습니다.
  • 응답 속성 'results/items/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 'results/items/invitationExpiresAt'이 선택 사항이 되었습니다.
  • 새로운 선택적 '쿼리' 요청 매개변수 'orgMembershipStatuses'가 추가되었습니다.
  • 'results/items/' 응답 속성 에 'INVITATION_EXPIRED, INVITATION_REJECTED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '201'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 새로운 선택적 '쿼리' 요청 매개변수 'orgMembershipStatuses'가 추가되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 응답 속성 '/invitationExpiresAt'이(가) null을 허용하게 되었습니다.
  • 응답 속성 '/invitationExpiresAt'가 선택 사항이 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'INVITATION_EXPIRED, INVITATION_REJECTED' 매핑 키를 추가했습니다.
  • '/orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.
  • 'orgMembershipStatus' 응답 속성 에 새로운 'INVITATION_EXPIRED, INVITATION_REJECTED' 열거형 값을 추가했습니다.

2026년 4월 29일 출시

  • 새로운 'CLUSTER_CONNECTION_find_DOCUMENTS' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #1: Any Other 이벤트]/eventTypeName/oneOf[subschema #4: 클러스 Connection 감사 Types]/' 응답 속성 에 새로운 'CLUSTER_CONNECTION_finD_DOCUMENTS' 열거형 값을 추가했습니다.
  • 선택적 속성 'results/items/oneOf[subschema #1: S3 로그 Export Integration Response]/useLegacyPathStructure'를 응답에 추가했습니다.
  • 선택 사항 속성 '/oneOf[subschema #1: S3 로그 Export Integration Response]/useLegacyPathStructure'를 응답에 추가했습니다.
  • 새로운 선택적 요청 속성 '/oneOf[subschema #1: S3 Log Export Integration Request]/useLegacyPathStructure' 추가
  • 선택 사항 속성 '/oneOf[subschema #1: S3 로그 Export Integration Response]/useLegacyPathStructure'를 응답에 추가했습니다.
  • 선택 사항 속성 '/oneOf[subschema #1: S3 로그 Export Integration Response]/useLegacyPathStructure'를 응답에 추가했습니다.
  • 새로운 선택적 요청 속성 '/oneOf[subschema #1: S3 Log Export Integration Request]/useLegacyPathStructure' 추가

2026년 4월 28일 출시

  • 선택적 속성 'results/items/oneOf[subschema #17: Stream Processor 지표 경고 Configuration]/metricThreshold'를 응답에 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold'를 응답에 추가했습니다.
  • 새로운 선택적 요청 속성 '/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold'
  • 선택적 속성 '/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold'를 응답에 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold'를 응답에 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold'를 응답에 추가했습니다.
  • 새로운 선택적 요청 속성 '/oneOf[subschema #17: Stream Processor Metric Alert Configuration]/metricThreshold'
  • 선택적 속성 'results/items/oneOf[subschema #17: Stream Processor 지표 경고 Configuration]/metricThreshold'를 응답에 추가했습니다.

2026년 4월 20일 출시

  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView' 추가
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView'가 추가되었습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView'가 추가되었습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView'를 추가했습니다.
  • 'results/items/oneOf[subschema #4: 호스팅하다 Metric 경고]/' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 'results/items/oneOf[subschema #4: 호스팅하다 Metric 경고]/' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchProcessThrottlingRawMetricThresholdView' 추가
  • 'results/items/oneOf[subschema #14: Host Metric Events]/' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #14: Host 지표 이벤트]/' 응답 속성 에 'SEARCH_PROCESS_THROTTLING' 판별자 매핑 키를 추가했습니다.

2026년 4월 16일 출시

  • 응답에 선택 사항 속성 '계층'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 '계층'가 추가되었습니다.

2026년 4월 15일 출시

  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/items/oneOf[subschema #3: Host Matcher Fields]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName' 응답 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName' 응답 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다.
  • 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: 자동 확장 감사 유형]/' 응답 속성에 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 'results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/eventType 경고 구성' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 'results/items/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #13: Auto Scaling 감사 유형]/' 감사 속성에 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #4: 청구 임계값 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다. '/oneOf[subschema #8: Host 경고 Configuration]/matchers/items/fieldName'
  • 요청 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다. '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName'
  • 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 요청 속성 '/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName/oneOf[subschema #13: 자동 확장 감사 유형]/'에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #4: 청구 임계값 경고 구성]/eventTypeName'에 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값이 추가되었습니다.14
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #13: Auto Scaling 감사 유형]/' 감사 속성에 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #4: 청구 임계값 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #13: Auto Scaling 감사 유형]/' 감사 속성에 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #4: 청구 임계값 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • 새로운 'ATLAS_NODE_TYPE' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #13: Auto Scaling 감사 유형]/' 감사 속성에 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #4: 청구 임계값 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다. '/oneOf[subschema #8: Host 경고 Configuration]/matchers/items/fieldName'
  • 요청 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다. '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName'
  • 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 요청 속성 '/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName/oneOf[subschema #13: 자동 확장 감사 유형]/'에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #4: 청구 임계값 경고 구성]/eventTypeName'에 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값이 추가되었습니다.14
  • 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName/oneOf16 자동 확장 감사 속성 에 새로운 'COMPUT_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUT_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 'results/items/oneOf[subschema #7: Any 기타 유형 경고]/eventTypeName/oneOf[subschema #1: Billing Event Types]/' 응답 속성
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName/oneOf[subschema #4: Full Text Search 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName/oneOf16 자동 확장 감사 속성 에 새로운 'COMPUT_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUT_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 'results/items/oneOf[subschema #7: Any 기타 유형 경고]/eventTypeName/oneOf[subschema #1: Billing Event Types]/' 응답 속성
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName/oneOf[subschema #4: Full Text Search 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf16: 자동 확장 감사 유형 응답 속성 에 새로운 'COMPUT_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPURE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #1: 청구 이벤트 Types]/' 응답 속성에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf16: 자동 확장 감사 유형 응답 속성 에 새로운 'COMPUT_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPURE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #1: 청구 이벤트 Types]/' 응답 속성에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/fieldName' 응답 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/fieldName' 응답 속성 에 새로운 'ATLAS_NODE_TYPE' 열거형 값을 추가했습니다.
  • 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #13: 자동 확장 감사 유형]/' 응답 속성에 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 'results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/eventType 경고 구성' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_CLEANED_UP' 열거형 값을 'results/items/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 선택 사항인 '쿼리' 요청 매개변수 'oplogInc' 추가
  • 새로운 선택적 '쿼리' 요청 매개변수 'oplogTs'가 추가되었습니다.
  • 새로운 선택적 '쿼리' 요청 매개 변수 'pointInTimeUtcSeconds' 추가
  • 상태가 '409 '인 실패 응답을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #37: 샤드 키 관리자 이벤트 유형'을 추가했습니다.
  • Added the new 'CLUSTER_CREATED_VIA_ANIS, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_CREATED, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_DELETED, OTEL_METRIC_INTEGRATION_CONFIGURATION_UPDATED, OTEL_METRIC_INTEGRATION_DISABLED, OTEL_METRIC_INTEGRATION_ENABLED' 열거형 values to the 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' response 속성
  • 'results/items/oneOf[subschema #16: 자동 확장 감사]/eventTypeName' 응답 속성 에 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • Added the new 'DAILY_BILLING_CHANGE_NORMAL, DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_NORMAL, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_NORMAL, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 values to the 'results/items/oneOf[subschema #8: 청구 이벤트]/eventTypeName' response 속성
  • 응답에 대한 '/oneOf[subschema #1: Any Other 이벤트]/이벤트TypeName' 응답 속성 'oneOf' 목록에 'subschema #37: 샤드 키 Advisor 이벤트 유형'를 추가했습니다.
  • Added the new 'CLUSTER_CREATED_VIA_ANIS, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_CREATED, ENCRYPTION_AT_REST_PRIVATE_ENDPOINT_DELETED, OTEL_METRIC_INTEGRATION_CONFIGURATION_UPDATED, OTEL_METRIC_INTEGRATION_DISABLED, OTEL_METRIC_INTEGRATION_ENABLED' 열거형 values to the '/oneOf[subschema #15: Atlas Project Audits]/eventTypeName' response 속성
  • '/oneOf[subschema #16: 자동 확장 감사]/eventTypeName' 응답 속성 에 새로운 'COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_ANALYTICS, COMPUTE_AUTO_SCALE_DOWNSCALE_SKIPPED_FALLBACK_BASE' 열거형 값을 추가했습니다.
  • 새로운 'DAILY_BILLING_CHANGE_NORMAL, DAILY_BILLING_CHANGE_OVER_THRESHOLD, MONTHLY_BILLING_CHANGE_NORMAL, MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_NORMAL, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD' 열거형 값을 '/oneOf[subschema #8: 청구 이벤트]/eventTypeName' 응답 속성에 추가했습니다.
  • 요청 속성 'services/items/'에 새로운 '네이티브 Reranking' 열거형 값을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Any Other 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #6: Ai Models 이벤트 Types'를 추가했습니다.
  • Added the new 'ORG_DAILY_BILLING_CHANGE_NORMAL, ORG_DAILY_BILLING_CHANGE_OVER_THRESHOLD, ORG_MONTHLY_BILLING_CHANGE_NORMAL, ORG_MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, ORG_WEEKLY_BILLING_CHANGE_NORMAL, ORG_WEEKLY_BILLING_CHANGE_OVER_THRESHOLD, PROJECT_CREATED_VIA_ANIS' 열거형 값 to the 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #6: Ai Models Event Types'를 추가했습니다.
  • Added the new 'ORG_DAILY_BILLING_CHANGE_NORMAL, ORG_DAILY_BILLING_CHANGE_OVER_THRESHOLD, ORG_MONTHLY_BILLING_CHANGE_NORMAL, ORG_MONTHLY_BILLING_CHANGE_OVER_THRESHOLD, ORG_WEEKLY_BILLING_CHANGE_NORMAL, ORG_WEEKLY_BILLING_CHANGE_OVER_THRESHOLD, PROJECT_CREATED_VIA_ANIS' 열거형 values to the '/oneOf[subschema #8: Organization Events]/eventTypeName' response 속성
  • 요청 속성 'filters/skuServices/items/'에 새로운 '네이티브 재순위 지정' 열거형 값이 추가되었습니다.

2026년 4월 03일 출시

  • 새로운 선택적 요청 속성 'withDefaultAlertsSettings' 추가
  • 새로운 'GROUP_DEFAULT_ALERTS_SETTINGS_CHANGED' 열거형 값이 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #11: Group Audit Types]/' 응답 속성 에 추가되었습니다.
  • 새로운 'GROUP_DEFAULT_ALERTS_SETTINGS_CHANGED' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #11: Group Audit Types]/' 응답 속성 에 추가했습니다.

2026년 3월 30일 출시

  • 응답에 선택적 속성 'summaries/items/cpuTime'을 추가했습니다.
  • 응답에 선택적 속성 'queryStats/cpuTime'을 추가했습니다.
  • 'results/items/connections/items/' 응답 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/connections/items/' 응답 속성 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection'을 추가했습니다.
  • 'results/items/connections/items/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 'connections/items/' 요청 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 'connections/items/' 요청 속성 'oneOf' 목록에 '#/components/schemas/StreamsGCPPubSubConnection' 추가
  • 'connections/items/' 응답 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsGCPPubSubConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값을 추가했습니다.
  • 요청 속성 'connections/items/type'에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 'connections/items/' 응답 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsGCPPubSubConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsGCPPubSubConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값을 추가했습니다.
  • 'results/items/' 응답 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection'을 추가했습니다.
  • 'results/items/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 요청 판별자에 'GCPPubSub' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'GCPPubSub' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 'type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 요청 속성 '/type'에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 요청 속성 'type'에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'GCPPubSub' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 'type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 요청 판별자에 'GCPPubSub' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'GCPPubSub' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/스키마/StreamsGCPPubSubConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 'type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 요청 속성 '/type'에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 요청 속성 'type'에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값이 추가되었습니다.
  • 'connections/items/' 응답 속성 에 'GCPPubSub' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsGCPPubSubConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AzureBlobStorage, GCPPubSub' 열거형 값을 추가했습니다.

2026년 3월 26일 출시

  • 응답에 선택적 속성 'summaries/items/cpuNanos'를 추가했습니다.
  • 응답에 선택 사항 속성 'queryStats/cpuNanos'를 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Any Other 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #38: Ai Models 이벤트 Types'를 추가했습니다.
  • 'results/items/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성 에 새로운 'ENCRYPTION_AT_REST_KEY_ROTATION_STARTED, NODE_HIDDEN_BY_ADMIN, NODE_UNHIDDEN_BY_ADMIN' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #38: Ai Models Event Types'를 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_KEY_ROTATION_STARTED, NODE_HIDDEN_BY_ADMIN, NODE_UNHIDDEN_BY_ADMIN' 열거형 값을 '/oneOf[subschema #15: Atlas 프로젝트 감사]/eventTypeName' 응답 속성에 추가했습니다.
  • 새로운 선택적 요청 속성 'supportedRemoteRegions' 추가
  • 응답에 선택적 속성 'isNativeRerankingEnabled'를 추가했습니다.
  • 응답에 선택적 속성 'isNativeRerankingEnabled'를 추가했습니다.
  • 새로운 선택적 요청 속성 'isNativeRerankingEnabled'가 추가되었습니다.
  • 'results/items/connections/items/' 응답 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택적 속성 'results/items/connections/items/ID'를 추가했습니다.
  • 'connections/items/' 요청 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 'connections/items/' 요청 속성 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택 사항 속성 'connections/items/id'를 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택 사항 속성 'connections/items/id'를 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택 사항 속성 'connections/items/id'를 추가했습니다.
  • 'results/items/' 응답 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/스키마/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택적 속성 'results/items/ID '를 추가했습니다.
  • 요청 판별자에 'AzureBlobStorage' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/스키마/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AzureBlobStorage' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택적 속성 '/id, id'를 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AzureBlobStorage' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택적 속성 '/id, id'를 추가했습니다.
  • 요청 판별자에 'AzureBlobStorage' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/스키마/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AzureBlobStorage' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택적 속성 '/id, id'를 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AzureBlobStorage' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAzureBlobStorageConnection'을 추가했습니다.
  • 응답에 선택 사항 속성 'connections/items/id'를 추가했습니다.
  • 상태가 '402 '인 실패 응답을 추가했습니다.
  • 'results/items/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 응답 속성 에 새로운 'PAYMENT_DUE_DATE_EXTENDED' 열거형 값을 추가했습니다.
  • 새로운 'PAYMENT_DUE_DATE_EXTENDED' 열거형 값을 '/oneOf[subschema #6: 결제 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.

2026년 3월 23일 출시

  • 새로운 'INTERFACE_ENDPOINT_RETRIED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #22: Private Link 감사 types]/' 응답 속성 에 추가했습니다.
  • 새로운 'INTERFACE_ENDPOINT_RETRIED' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #22: Private Link Audit Types]/' 응답 속성 에 추가했습니다.

2026년 3월 18일 출시

  • 응답에 선택 사항 속성 'isClusterAiAssistantEnabled'를 추가했습니다.
  • 응답에 선택 사항 속성 'isClusterAiAssistantEnabled'를 추가했습니다.
  • 새로운 선택적 요청 속성 'isClusterAiAssistantEnabled'가 추가되었습니다.

2026년 3월 10일 출시

  • 응답에 선택 사항 속성 'autoCopySettingsEnabled'를 추가했습니다.
  • 응답에 선택 사항 속성 'autoCopySettingsEnabled'를 추가했습니다.
  • 응답에 선택 사항 속성 'autoCopySettingsEnabled'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'autoCopySettingsEnabled'가 추가되었습니다.
  • 새로운 'VERCEL_INVOICE_OVERDUE' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName/oneOf[subschema #4: 파트너 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'VERCEL_INVOICE_OVERDUE' 열거형 값을 '/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName/oneOf[subschema #4: 파트너 이벤트 유형]/' 응답 속성 에 추가했습니다.

2026년 3월 06일 출시

  • 요청 속성 '/oneOf[subschema #1: S3 Log Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, mongod_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #2: Datadog 로그 내보내기 통합 요청]/logTypes/items/'에 새로운 'MONGOD, Mongod_AUDIT, Mongos, mongos_audit' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #3: GCS Log Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, MongOD_AUDIT, MongOS, MongOS_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #4: OTel 로그 Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, MONGOD_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #5: Splunk 로그 Export Integration Request]/logTypes/items/'에 새로운 'mongod, MONGOD_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #6: Azure 로그 Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, MONGOD_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 'logTypes/items/'에 새로운 'MONGOD, mongod_AUDIT, MongOS, Mongos_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: S3 Log Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, mongod_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #2: Datadog 로그 내보내기 통합 요청]/logTypes/items/'에 새로운 'MONGOD, Mongod_AUDIT, Mongos, mongos_audit' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #3: GCS Log Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, MongOD_AUDIT, MongOS, MongOS_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #4: OTel 로그 Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, MONGOD_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #5: Splunk 로그 Export Integration Request]/logTypes/items/'에 새로운 'mongod, MONGOD_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #6: Azure 로그 Export Integration Request]/logTypes/items/'에 새로운 'MONGOD, MONGOD_AUDIT, MONGOS, MONGOS_AUDIT' 열거형 값을 추가했습니다.
  • 요청 속성 'logTypes/items/'에 새로운 'MONGOD, mongod_AUDIT, MongOS, Mongos_AUDIT' 열거형 값을 추가했습니다.

2026년 3월 05일 출시

  • 응답 속성 'apiKey/accessList, apiKey/roles'가 필수가 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results, results/items/roleMappings/items/roleAssignments'가 필수 항목이 되었습니다.
  • 응답 속성 'roleMappings/items/roleAssignments'가 필수 항목이 되었습니다.
  • 응답 속성 'roleMappings/items/roleAssignments'가 필수 항목이 되었습니다.
  • 응답 속성 'results, results/items/roleAssignments'가 필수 항목이 되었습니다.
  • 응답 속성 'results, results/items/ associatedOrgs/items/roleMappings/items/roleAssignments, results/items/oneOf[subschema #1: SAML]/ associatedOrgs/items/roleMappings/items/roleAssignments, results/items/oneOf [subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments, results/items/oneOf[subschema #3: OIDC 워크로드]/relatedOrgs/items/roleMappings/items/roleAssignments'가 필수 항목이 됨
  • 응답 속성 '/oneOf[subschema #1: OIDC WORKFORCE]/associatedOrgs/items/roleMappings/items/roleAssignments, /oneOf[subschema #2: OIDC 워크로드]/associatedOrgs/items/roleMappings/items/roleAssignments, associatedOrgs/items/roleMappings/items/roleAssignments' 필수 항목이 되었습니다.
  • 응답 속성 '/oneOf[subschema #1: SAML]/ associatedOrgs/items/roleMappings/items/roleAssignments, /oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments, / oneOf[subschema #3: OIDC 워크로드]/ associatedOrgs/items/roleMappings/items/roleAssignments, associatedOrgs/items/roleMappings/items/roleAssignments'가 필수가 되었습니다.
  • 응답 속성 '/oneOf[subschema #1: SAML]/ associatedOrgs/items/roleMappings/items/roleAssignments, /oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments, / oneOf[subschema #3: OIDC 워크로드]/ associatedOrgs/items/roleMappings/items/roleAssignments, associatedOrgs/items/roleMappings/items/roleAssignments'가 필수가 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 'results/items/oneOf[subschema #8: Host 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #8: Host 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값이 추가되었습니다.115
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #8: Host 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #8: Host 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #8: Host 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값이 추가되었습니다.115
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #19: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #15: 호스트 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 'results/items/oneOf[subschema #8: Host 경고 Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 'awsIamRoles/items/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 'azureServicePrincipals/items/featureUsages/items/' 응답 속성 에 추가했습니다.
  • 'gcpServiceAccounts/items/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • 'awsIamRoles/items/featureUsages/items/featureType' 응답 속성 에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • 'azureServicePrincipals/items/featureUsages/items/featureType' 응답 속성 에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • 'gcpServiceAccounts/items/featureUsages/items/featureType' 응답 속성 에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • '/featureUsages/items/' 요청 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 요청 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 요청 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/featureType' 응답 속성 에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • 요청 속성 '/featureUsages/items/featureType'에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/featureType' 응답 속성 에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/' 응답 속성 에 'ATLAS_LOG_INTEGRATION' 판별자 매핑 키를 추가했습니다.
  • '/featureUsages/items/featureType' 응답 속성 에 새로운 'ATLAS_LOG_INTEGRATION' 열거형 값을 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 '정책, 정책/항목/정책 항목'이 필수 항목이 되었습니다.
  • 응답 속성 '정책, 정책/항목/정책 항목'이 필수 항목이 되었습니다.
  • 응답 속성 '정책, 정책/항목/정책 항목'이 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'pinnedNamespaces'가 필수가 되었습니다.
  • 응답 속성 'pinnedNamespaces'가 필수가 되었습니다.
  • 응답 속성 'pinnedNamespaces'가 필수가 되었습니다.
  • 응답 속성 'pinnedNamespaces'가 필수가 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 새로운 선택적 요청 속성 'definition/oneOf[subschema #2: 벡터 검색 인덱스 Definition]/nestedRoot' 추가
  • 새로운 선택적 요청 속성 'definition/oneOf[subschema #2: 벡터 검색 인덱스 Definition]/nestedRoot' 추가
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'rankedNamespaces'가 필수 항목이 되었습니다.
  • 응답 속성 'results, results/items/oneOf[subschema #2: GCP]/regions'이 필수 항목이 되었습니다.
  • 응답 속성 '/oneOf[subschema #2: GCP]/regions' 필수가 되었습니다.
  • 응답 속성 'results, results/items/oneOf[subschema #2: GCP]/regions'이 필수 항목이 되었습니다.
  • 응답 속성 '/oneOf[subschema #2: GCP]/regions' 필수가 되었습니다.
  • 응답 속성 '/oneOf[subschema #2: GCP]/regions' 필수가 되었습니다.
  • 응답 속성 '/items/조치/items/리소스'가 필수 항목이 되었습니다.
  • 응답 속성 'actions/items/resources'가 필수 항목이 되었습니다.
  • 응답 속성 'actions/items/resources'가 필수 항목이 되었습니다.
  • 응답 속성 'actions/items/resources'가 필수 항목이 되었습니다.
  • 응답 속성 'results, results/items/roles'이 필수 항목이 되었습니다.
  • 응답 속성 'roles'가 필수 항목이 되었습니다.
  • 응답 속성 'roles'가 필수 항목이 되었습니다.
  • 응답 속성 'roles'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • ' 쿼리' 요청 매개 변수 'end'의 경우 최소값이 '1199145600000.00'로 설정하다 되었습니다.
  • ' 쿼리' 요청 매개변수 'start'의 경우, 최소값이 '1199145600000.00'로 설정하다 되었습니다.
  • ' 쿼리' 요청 매개 변수 'end'의 경우 최소값이 '1199145600000.00'로 설정하다 되었습니다.
  • ' 쿼리' 요청 매개변수 'start'의 경우, 최소값이 '1199145600000.00'로 설정하다 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 새로운 'CROSS_REGION_SUPPORTED_REGION_MODIFIED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #22: Private Link Audit Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_RESTARTED, PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 새로운 'CROSS_REGION_SUPPORTED_REGION_MODIFIED' 열거형 값을 '/oneOf[subschema #1: Any Other 이벤트]/eventTypeName/oneOf[subschema #22: Private Link 감사 Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_RESTARTED, PROFILER_CONFIGURED_TOO_WIDELY' 열거형 값을 '/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 추가했습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'hardwareMetrics, indexMetrics, statusMetrics'이 필수 항목이 됨
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 'results/items/' 응답 속성 에 'GCS_LOG_EXPORT, OTEL_LOG_EXPORT, SPLUNK_LOG_EXPORT, AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT' 판별자 매핑 키를 추가했습니다.
  • 추가된 '#/components/schemas/DatadogLogIntegrationResponse, #/components/schemas/GcsLogIntegrationResponse, #/components/schemas/OtelLogIntegrationResponse, #/components/schemas/SplunkLogIntegrationResponse, #/components/schemas/Azu' 응답에 대한 응답 속성 'oneOf' 목록
  • 'results/items/oneOf[subschema #1: S3 Log Export Integration Response]/iamRoleId' 응답의 속성 패턴 '^[a-fA-F0-9]{24}$'이(가) 추가되었습니다.
  • 응답 속성 'results, results/items/logTypes, results/items/oneOf[subschema #1: S3 로그 내보내기 통합 응답]/logTypes'이 필수 항목이 되었습니다.
  • 요청 속성 '/oneOf[subschema #1: S3 로그 내보내기 통합 요청에 '^[a-fA-F0-9]{24}$' 패턴 추가했습니다. ]/iamRoleId'
  • 요청 판별자에 'GCS_LOG_EXPORT, OTEL_LOG_EXPORT, SPLUNK_LOG_EXPORT, AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 추가된 '#/components/schemas/DatadogLogIntegrationRequest, #/components/components/스키마/GcsLogIntegrationRequest, #/components/스키마/OtelLogIntegrationRequest, #/components/스키마/SplunkLogIntegrationRequest, #/components/스키마 / Azu
  • 응답 상태 '201'에 대한 응답 판별자에 'SPLUNK_LOG_EXPORT, AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT, GCS_LOG_EXPORT, OTEL_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 응답 본문 'oneOf' 목록에 '#/components/스키마/DatadogLogIntegrationResponse, #/components/스키마/GcsLogIntegrationResponse, #/components/스키마/OtelLogIntegrationResponse, #/components/스키마/SplunkLogIntegrationResponse, #/components/스키마/AzureLogIntegrationResponse'를 추가했습니다.
  • '/oneOf[subschema #1: S3 로그 Export Integration Response]/iamRoleId' 응답의 속성 패턴 '^[a-fA-F0-9]{24}$ '이(가) 추가되었습니다.
  • 요청 속성 'type'에 새로운 'AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT, GCS_LOG_EXPORT, OTEL_LOG_EXPORT, SPLUNK_LOG_EXPORT' 열거형 값이 추가되었습니다.
  • 응답 속성 '/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes, logTypes' 필수가 되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT, GCS_LOG_EXPORT, OTEL_LOG_EXPORT, SPLUNK_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 응답 본문 'oneOf' 목록에 '#/components/스키마/DatadogLogIntegrationResponse, #/components/스키마/GcsLogIntegrationResponse, #/components/스키마/OtelLogIntegrationResponse, #/components/스키마/SplunkLogIntegrationResponse, #/components/스키마/AzureLogIntegrationResponse'를 추가했습니다.
  • '/oneOf[subschema #1: S3 로그 Export Integration Response]/iamRoleId' 응답의 속성 패턴 '^[a-fA-F0-9]{24}$ '이(가) 추가되었습니다.
  • 응답 속성 '/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes, logTypes' 필수가 되었습니다.
  • 요청 속성 '/oneOf[subschema #1: S3 로그 내보내기 통합 요청에 '^[a-fA-F0-9]{24}$' 패턴 추가했습니다. ]/iamRoleId'
  • 요청 판별자에 'SPLUNK_LOG_EXPORT, AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT, GCS_LOG_EXPORT, OTEL_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 추가된 '#/components/schemas/DatadogLogIntegrationRequest, #/components/components/스키마/GcsLogIntegrationRequest, #/components/스키마/OtelLogIntegrationRequest, #/components/스키마/SplunkLogIntegrationRequest, #/components/스키마 / Azu
  • 응답 상태 '200'에 대한 응답 판별자에 'AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT, GCS_LOG_EXPORT, OTEL_LOG_EXPORT, SPLUNK_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 응답 본문 'oneOf' 목록에 '#/components/스키마/DatadogLogIntegrationResponse, #/components/스키마/GcsLogIntegrationResponse, #/components/스키마/OtelLogIntegrationResponse, #/components/스키마/SplunkLogIntegrationResponse, #/components/스키마/AzureLogIntegrationResponse'를 추가했습니다.
  • '/oneOf[subschema #1: S3 로그 Export Integration Response]/iamRoleId' 응답의 속성 패턴 '^[a-fA-F0-9]{24}$ '이(가) 추가되었습니다.
  • 요청 속성 'type'에 새로운 'AZURE_LOG_EXPORT, DATADOG_LOG_EXPORT, GCS_LOG_EXPORT, OTEL_LOG_EXPORT, SPLUNK_LOG_EXPORT' 열거형 값이 추가되었습니다.
  • 응답 속성 '/oneOf[subschema #1: S3 Log Export Integration Response]/logTypes, logTypes' 필수가 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'rankedNamespaces'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 요청 선택적 속성 'connections/items/ 리전'이 읽기 전용이 아닙니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '/ 리전'이(가) 읽기 전용이 아닙니다.
  • 요청 선택 사항 속성 '리전'이(가) 읽기 전용이 아닙니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'federatedDomains'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 '/items/배포서버, /items/migrationHosts'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results, results/items/roles'이 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'results'가 필수 항목이 되었습니다.
  • 응답 속성 'roles'가 필수 항목이 되었습니다.
  • 응답 속성 'roles'가 필수 항목이 되었습니다.
  • 응답 속성 'roles'가 필수 항목이 되었습니다.

2026년 2월 24일 출시

  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.

2026년 2월 23일 출시

  • 엔드포인트 추가됨
  • 엔드포인트 추가됨

2026년 2월 18일 출시

  • 새로운 선택 사항 '쿼리' 요청 매개 변수 'spName' 추가

2026년 2월 17일 출시

  • 요청 속성 'services/items/'에 새로운 'DSC 컴퓨팅, DSC 저장' 열거형 값을 추가했습니다.
  • 요청 속성 '필터/skuServices/items/'에 새로운 'DSC 컴퓨팅, DSC 저장' 열거형 값을 추가했습니다.

2026년 2월 12일 출시

  • 7813'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록
  • 'results/items/oneOf[subschema #1]에서 'subschema #7: NDS 감사 유형, subschema #8: NDS 유지 관리 기간 감사 유형, subschema #13: NDS 자동 확장 감사 유형' 제거됨 : 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • '/oneOf[하위 스키마 #1: 기타 경고 구성]에 '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #13: 자동 확장 감사 유형'이 추가되었습니다. ]/eventTypeName' 요청 속성 'oneOf' 목록
  • '/oneOf[하위 스키마 #1: 기타 경고 구성]에 '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #13: 자동 확장 감사 유형'이 추가되었습니다. ]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록
  • 응답에 대한 '/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #7: NDS 감사 유형, subschema #8: NDS 유지 관리 기간 감사 유형, subschema #13: NDS 자동 확장 감사 유형'을 제거했습니다.
  • '/oneOf[하위 스키마 #1: 기타 경고 구성]에 '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #13: 자동 확장 감사 유형'이 추가되었습니다. ]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록
  • 응답에 대한 '/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #7: NDS 감사 유형, subschema #8: NDS 유지 관리 기간 감사 유형, subschema #13: NDS 자동 확장 감사 유형'을 제거했습니다.
  • '/oneOf[하위 스키마 #1: 기타 경고 구성]에 '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #13: 자동 확장 감사 유형'이 추가되었습니다. ]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록
  • 응답에 대한 '/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #7: NDS 감사 유형, subschema #8: NDS 유지 관리 기간 감사 유형, subschema #13: NDS 자동 확장 감사 유형'을 제거했습니다.
  • '/oneOf[하위 스키마 #1: 기타 경고 구성]에 '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #13: 자동 확장 감사 유형'이 추가되었습니다. ]/eventTypeName' 요청 속성 'oneOf' 목록
  • '/oneOf[하위 스키마 #1: 기타 경고 구성]에 '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #13: 자동 확장 감사 유형'이 추가되었습니다. ]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록
  • 응답에 대한 '/oneOf[subschema #1: Any Other 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #7: NDS 감사 유형, subschema #8: NDS 유지 관리 기간 감사 유형, subschema #13: NDS 자동 확장 감사 유형'을 제거했습니다.
  • '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #9: x509 사용자 인증 이벤트 유형, 하위 스키마 #16: 자동 확장 감사 유형'이 추가되었습니다. 응답에 대한 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName' 응답 속성 'oneOf' 목록
  • 제거된 '하위 스키마 #7: NDS 감사 유형, 하위 스키마 #8: NDS 유지 관리 기간 감사 유형, 하위 스키마 #9: NDS x509 사용자 인증 이벤트 유형, 하위 스키마 #16: NDS 자동 확장 감사 유형'은 'results/items/oneOf[subschema #7: 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에서
  • '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #9: x509 사용자 인증 이벤트 유형, 하위 스키마 #16: 자동 확장 감사 유형'이 추가되었습니다. 응답에 대한 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName' 응답 속성 'oneOf' 목록
  • 제거된 '하위 스키마 #7: NDS 감사 유형, 하위 스키마 #8: NDS 유지 관리 기간 감사 유형, 하위 스키마 #9: NDS x509 사용자 인증 이벤트 유형, 하위 스키마 #16: NDS 자동 확장 감사 유형'은 'results/items/oneOf[subschema #7: 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에서
  • '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #9: x509 사용자 인증 이벤트 유형, 하위 스키마 #16: 자동 확장 감사 유형'이 추가되었습니다. 응답에 대한 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName' 응답 속성 'oneOf' 목록
  • 제거된 '하위 스키마 #7: NDS 감사 유형, 하위 스키마 #8: NDS 유지 관리 기간 감사 유형, 하위 스키마 #9: NDS x509 사용자 인증 이벤트 유형, 하위 스키마 #16: NDS 자동 확장 감사 유형'을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName' 응답 속성 'oneOf' 목록에서 선택합니다.
  • '하위 스키마 #7: Atlas 감사 유형, 하위 스키마 #8: 유지 관리 기간 감사 유형, 하위 스키마 #9: x509 사용자 인증 이벤트 유형, 하위 스키마 #16: 자동 확장 감사 유형'이 추가되었습니다. 응답에 대한 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName' 응답 속성 'oneOf' 목록
  • 제거된 '하위 스키마 #7: NDS 감사 유형, 하위 스키마 #8: NDS 유지 관리 기간 감사 유형, 하위 스키마 #9: NDS x509 사용자 인증 이벤트 유형, 하위 스키마 #16: NDS 자동 확장 감사 유형'을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName' 응답 속성 'oneOf' 목록에서 선택합니다.
  • 7813'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록
  • 'results/items/oneOf[subschema #1]에서 'subschema #7: NDS 감사 유형, subschema #8: NDS 유지 관리 기간 감사 유형, subschema #13: NDS 자동 확장 감사 유형' 제거됨 : 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 응답에 선택적 속성 'results/items/EffectiveReplicationSpecs'를 추가했습니다.
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Fields-Replication-Specs' 추가
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다. 리전]/'
  • 요청 열거형 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 리전]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값 추가 리전]/'
  • 요청 열거형 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 리전]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/'에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'EffectiveReplicationSpecs' 추가
  • 요청 속성 'providerSettings/oneOf[subschema #2: Cloud Service Provider Settings for a Cluster]/regionName'에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 선택 사항 속성 'deleteAfterCreationHours, deleteAfterDate'를 응답에 추가했습니다.
  • 새로운 선택 사항 요청 속성 'deleteAfterCreationHours'가 추가되었습니다.
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Fields-Replication-Specs' 추가
  • 응답에 선택적 속성 'EffectiveReplicationSpecs' 추가
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Fields-Replication-Specs' 추가
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다. 리전]/'
  • 요청 열거형 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 리전]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값 추가 리전]/'
  • 요청 열거형 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 리전]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/'에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'EffectiveReplicationSpecs' 추가
  • 응답에 선택 사항인 쓰기 전용 속성 'deleteCopySnapshots'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'updateCopySnapshots'을 추가했습니다.
  • 응답에 선택적 속성 'copyPolicyItemsEnabled, copySettings/items/copyPolicyItems, copySettings/items/lastNumberOfSnapshots'를 추가했습니다.
  • 응답에 선택 사항인 쓰기 전용 속성 'deleteCopySnapshots'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'updateCopySnapshots'을 추가했습니다.
  • 응답에 선택적 속성 'copyPolicyItemsEnabled, copySettings/items/copyPolicyItems, copySettings/items/lastNumberOfSnapshots'를 추가했습니다.
  • 응답에 선택 사항인 쓰기 전용 속성 'deleteCopySnapshots'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'updateCopySnapshots'을 추가했습니다.
  • 응답에 선택적 속성 'copyPolicyItemsEnabled, copySettings/items/copyPolicyItems, copySettings/items/lastNumberOfSnapshots'를 추가했습니다.
  • 새로운 선택적 요청 속성 'copyPolicyItemsEnabled, copySettings/items/copyPolicyItems, copySettings/items/lastNumberOfSnapshots, deleteCopySnapshots, updateCopySnapshots'
  • 요청 속성 '/oneOf[subschema #1: AZURE]/ 리전 '에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: AZURE]/ 리전 '에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/ 조치 '에 새로운 'MODIFY_STREAM_PROCESSOR' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/ 조치 '에 새로운 'MODIFY_STREAM_PROCESSOR' 열거형 값을 추가했습니다.
  • 'azureKeyVault/azureEnvironment' 응답 속성 에 새로운 'AZURE_US_GOVERNMENT' 열거형 값을 추가했습니다.
  • 'azureKeyVault/azureEnvironment' 응답 속성 에 새로운 'AZURE_US_GOVERNMENT' 열거형 값을 추가했습니다.
  • 요청 속성 'azureKeyVault/azureEnvironment'에 새 'AZURE_US_GOVERNMENT' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운1 ' US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값이 추가되었습니다 .1
  • 요청 속성 '/oneOf[subschema #2: AWS Key Management Service EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure Regions]/'에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값이 추가되었습니다.
  • 요청 속성 'regionName/oneOf[subschema #1: Azure 리전]/'에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 추가된 'subschema #15: DB Check 감사 유형, subschema #16: Data 유효성 검사 감사 유형, subschema #17: 유지 관리 기간 감사 유형, subschema #18: 서버리스 자동 확장 감사 유형, subschema #19: 테넌트 엔드포인트 서비스 배포 감사 유형, 하위 스키마 #20: x509 사용자 인증 이벤트 유형'을 'results/items/oneOf[subschema #1: Any Other 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록을 사용하세요.
  • '하위 스키마 #15: NDS DB 검사 감사 유형, 하위 스키마 #16: NDS 데이터 유효성 검사 감사 유형, 하위 스키마 #17: NDS 유지 관리 기간 감사 유형, 하위 스키마 #18: NDS 서버리스 자동 확장 감사 유형, 하위 스키마 #19: NDS 테넌트 엔드포인트 서비스 배포 감사 유형, 하위 스키마 #20: NDS x509 사용자 인증 이벤트 유형'이 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에서 제거되었습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits -> subschema #15: Atlas Project Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_CANCELING_CONFIG_SERVER_TRANSITION_REQUESTED' 열거형 값을 추가했습니다.
  • 추가된 'subschema #15: DB Check 감사 유형, subschema #16: 데이터 유효성 검사 감사 유형, subschema #17: 유지 관리 기간 감사 유형, subschema #18: 서버리스 자동 확장 감사 유형, subschema #19: 테넌트 엔드포인트 서비스 배포 감사 유형, 하위 스키마 #20: x509 사용자 인증 이벤트 유형'을 '/oneOf[하위 스키마 #1: 기타 이벤트]/eventTypeName' 응답 속성 'oneOf' 목록에 추가합니다. 응답을 위해
  • 제거된 '하위 스키마 #15: NDS DB 검사 감사 유형, 하위 스키마 #16: NDS 데이터 유효성 검사 감사 유형, 하위 스키마 #17: NDS 유지 관리 기간 감사 유형, 하위 스키마 #18: NDS 서버리스 자동 확장 감사 유형 , 하위 스키마 #19: NDS 테넌트 엔드포인트 서비스 배포 감사 유형, 하위 스키마 #20: NDS x509 사용자 인증 이벤트 유형' from the '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답에 대한 응답 속성 'oneOf' 목록
  • '/oneOf[subschema #15: NDS Audits -> subschema #15: Atlas Project Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_CANCELING_CONFIG_SERVER_TRANSITION_REQUESTED' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다. 리전]/'
  • 요청 열거형 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 리전]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값 추가 리전]/'
  • 요청 열거형 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 값을 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #2: Azure 리전]/'에 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #2: Azure Regions]/'에 새로운 'US_GOV_ARIZONA, US_GOV_TEXAS, US_GOV_VIRGINIA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'results/items/logTypes'를 추가했습니다.
  • 요청 판별자 추가
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/S3LogIntegrationRequest'를 추가했습니다.
  • 응답에 선택적 속성 'logTypes'를 추가했습니다.
  • 응답에 선택적 속성 'logTypes'를 추가했습니다.
  • 응답에 선택적 속성 'logTypes'를 추가했습니다.
  • 새로운 선택적 요청 속성 'portMappingEnabled'가 추가되었습니다.
  • 응답에 선택적 속성 'results/items/connections/items/ 리전'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 리전'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 리전'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 리전'을 추가했습니다.
  • 새로운 선택적 요청 속성 'streamConfig' 추가
  • 응답에 선택 사항인 속성 'results/items/리전'을 추가했습니다.
  • 응답에 선택 사항 속성 '/ 리전, 리전'을 추가했습니다.
  • 응답에 선택 사항 속성 '/ 리전, 리전'을 추가했습니다.
  • 응답에 선택 사항 속성 '/ 리전, 리전'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 리전'을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Billing Events]/eventTypeName' 응답 속성 에 새로운 'MARKETPLACE_REFUND_ISSUED' 열거형 값을 추가했습니다.
  • 새로운 'ORG_LOCKED_ACCELERATED' 열거형 값을 'results/items/oneOf[subschema #8: 조직 이벤트 -> 하위 스키마 #8: 조직 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'MARKETPLACE_REFUND_ISSUED' 열거형 값을 '/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 응답 속성에 추가했습니다.
  • 새로운 'ORG_LOCKED_ACCELERATED' 열거형 값을 '/oneOf[subschema #8: Org Events -> subschema #8: 조직 이벤트]/eventTypeName' 응답 속성에 추가했습니다.
  • 'groupRoleAssignments/items/groupRole' 응답 속성 에서 'GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 제거했습니다.

2026년 2월 03일 출시

  • 새로운 선택적 요청 속성 'resumeFromCheckpoint'가 추가되었습니다.

2026년 1월 30일 출시

  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #9: Host Metric 경고 Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #9: 호스트 Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'가 추가되었습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #9: 호스트 Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'가 추가되었습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • 'results/items/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #9: Host Metric 경고 Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxNgramFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • 'results/items/oneOf[subschema #14: Host Metric Events]/' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #14: Host Metric Events]/' 응답 속성 에 'SEARCH_MAX_NGRAM_FIELDS_INEXED' 판별자 매핑 키를 추가했습니다.
  • 엔드포인트 사용 중단
  • 엔드포인트 사용 중단

2026년 1월 28일 출시

  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'를 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'가 추가되었습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'가 추가되었습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'를 추가했습니다.
  • 'results/items/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #4: Host Metric Alerts]/' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '#/components/schemas/SearchMaxFieldsIndexedRawMetricThresholdView'를 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가했습니다.
  • 'results/items/oneOf[subschema #14: Host 지표 Events]/' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.
  • '/oneOf[subschema #14: Host Metric Events]/' 응답 속성 에 'SEARCH_MAX_FIELDS_INDEXED' 판별자 매핑 키를 추가했습니다.

2026년 1월 22일 출시

  • 엔드포인트 추가됨
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/알림/items/oneOf[subschema #3: Group 알림]/역할/items/' 응답에서 'GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 제거했습니다. 속성
  • 응답에 선택 사항 속성 'results/items/retainBackups' 추가
  • 응답에 선택 사항 속성 'retainBackups' 추가
  • 새로운 선택적 요청 속성 'retainBackups' 추가
  • 응답에 선택 사항 속성 'retainBackups' 추가
  • 응답에 선택 사항 속성 'retainBackups' 추가
  • 새로운 선택적 요청 속성 'retainBackups' 추가
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • 새로운 선택적 요청 속성 'retainBackups' 추가
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-22'에 도달하여 제거되었습니다.
  • 응답에 선택 사항 속성 'results/items/connections/items/ 상태'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 상태'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 상태'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 상태'를 추가했습니다.
  • 응답에 선택 사항인 속성 'results/items/상태'를 추가했습니다.
  • 응답에 선택적 속성 '/ 상태, 상태'를 추가했습니다.
  • 응답에 선택적 속성 '/ 상태, 상태'를 추가했습니다.
  • 응답에 선택적 속성 '/ 상태, 상태'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 상태'를 추가했습니다.
  • 엔드포인트 추가됨
  • 엔드포인트 추가됨
  • 엔드포인트 추가됨

2026년 1월 21일 출시

  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/components/스키마/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/components/스키마/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/components/스키마/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/components/스키마/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/MongotuneAlertConfigViewForNdsGroup'을 추가했습니다.

2026년 1월 16일 출시

  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #5: 그룹 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값이 추가되었습니다.15
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #5: 그룹 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #5: 그룹 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #5: 그룹 이벤트 유형]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값이 추가되었습니다.15
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS, NO_ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값이 'results/items/oneOf[subschema #1: Any Other 이벤트]/eventTypeName/oneOf[subschema #12: Group 이벤트 types]/' 응답 속성 에 추가되었습니다.
  • 새로운 'ACTIVE_LEGACY_TLS_CONNECTIONS, NO_ACTIVE_LEGACY_TLS_CONNECTIONS' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #12: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #6: Billing Events]/eventTypeName' 응답 속성 에 새로운 'AWS_PAYMENT_PAID' 열거형 값을 추가했습니다.
  • 새로운 'AWS_PAYMENT_PAID' 열거형 값을 '/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 응답 속성에 추가했습니다.

2026년 1월 15일 출시

  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-15'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2026-01-15'에 도달하여 제거되었습니다.

2026년 1월 08일 출시

  • 새로운 선택 사항 요청 속성 'definition/oneOf[subschema #1: 텍스트 검색 인덱스 정의]/sort'가 추가되었습니다.
  • 새로운 선택 사항 요청 속성 'definition/oneOf[subschema #1: 텍스트 검색 인덱스 정의]/sort'가 추가되었습니다.
  • 'results/items/' 응답 속성 에서 'S3_LOG_EXPORT' 판별자 매핑 키를 제거했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/S3LogExport'가 제거되었습니다.
  • 응답 판별자에서 '200' 응답 상태에 대한 'S3_LOG_EXPORT' 매핑 키를 제거했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/S3LogExport'가 제거되었습니다.
  • 요청 판별자에서 'S3_LOG_EXPORT' 매핑 키를 제거했습니다.
  • 'results/items/' 응답 속성 에서 'S3_LOG_EXPORT' 판별자 매핑 키를 제거했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/S3LogExport'가 제거되었습니다.
  • 요청 판별자에서 'S3_LOG_EXPORT' 매핑 키를 제거했습니다.
  • 'results/items/' 응답 속성 에서 'S3_LOG_EXPORT' 판별자 매핑 키를 제거했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/S3LogExport'가 제거되었습니다.
  • 'results/items/connections/items/' 응답 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/connections/items/' 응답 속성 'oneOf' 목록에 '#/components/스키마/Streams스키마RegistryConnection'을 추가했습니다.
  • 'results/items/connections/items/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'connections/items/' 요청 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 'connections/items/' 요청 속성 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'이 추가되었습니다.
  • 'connections/items/' 응답 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 속성 'connections/items/type'에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'results/items/' 응답 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 'results/items/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 판별자에 'SchemaRegistry' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'SchemaRegistry' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 속성 '/type'에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 속성 'type'에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'SchemaRegistry' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 판별자에 'SchemaRegistry' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'SchemaRegistry' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 속성 '/type'에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 요청 속성 'type'에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'SchemaRegistry' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsSchemaRegistryConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'SchemaRegistry' 열거형 값을 추가했습니다.

2025년 12월 15일 릴리스

2025년 12월 11일 릴리스

  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/SearchPlannerAuditView'가 제거되었습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Any Other Events]/이벤트TypeName' 속성 'oneOf' 목록에서 'subschema #25: 검색하다 Planner 감사 Types'를 제거했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/SearchPlannerAuditView'가 제거되었습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에서 'subschema #25: 검색하다 Planner 감사 Types'를 제거했습니다.
  • 요청 속성 'cloudProvider'가 선택 사항이 됨
  • 요청 속성 ' 리전'이 선택 사항이 되었습니다.

2025년 12월 10일 릴리스

  • 응답에 대한 '/items/' 응답 속성 'oneOf' 목록에 'subschema #7: 글로벌 소프트웨어 유형 일치자 필드' 추가
  • 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf'에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스팅하다 이벤트 유형'이 추가되었습니다. 응답 목록
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 요청 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스팅하다 이벤트 유형'이 추가되었습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스트 이벤트 유형'이 추가되었습니다. 응답
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName'에 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스트 이벤트 유형'이 추가되었습니다. 응답
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스트 이벤트 유형'이 추가되었습니다. 응답
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 요청 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스팅하다 이벤트 유형'이 추가되었습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스트 이벤트 유형'이 추가되었습니다. 응답
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName'에 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #6: Mongotune 이벤트 types, subschema #19: 호스팅하다 이벤트 Types'가 추가되었습니다. 응답을 위해
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #6: 스트림 프로세서 경고]/eventTypeName' 응답 속성에 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #6: Mongotune 이벤트 types, subschema #19: 호스팅하다 이벤트 Types'가 추가되었습니다. 응답을 위해
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #6: 스트림 프로세서 경고]/eventTypeName' 응답 속성에 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #19: 호스팅 이벤트 유형'이 추가되었습니다.
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #3: 호스트 경고]/eventTypeName' 응답 속성에 추가했습니다.
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #19: 호스팅 이벤트 유형'이 추가되었습니다.
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #3: 호스트 경고]/eventTypeName' 응답 속성에 추가했습니다.
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf'에 '하위 스키마 #6: Mongotune 이벤트 유형, 하위 스키마 #15: 호스팅하다 이벤트 유형'이 추가되었습니다. 응답 목록
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 추가했습니다.
  • 응답에 선택 사항인 속성 'storedSource'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'storedSource'가 추가되었습니다.
  • 응답에 선택 사항 속성 '/items/storedSource'를 추가했습니다.
  • 응답에 선택 사항인 속성 'storedSource'를 추가했습니다.
  • 응답에 선택 사항인 속성 'storedSource'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'storedSource'가 추가되었습니다.
  • 응답에 선택 사항 속성 '/items/latestDefinition/storedSource, /items/statusDetail/items/mainIndex/definition/storedSource, /items/statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 응답에 선택 사항 속성 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 응답에 선택 사항 속성 '/items/latestDefinition/storedSource, /items/statusDetail/items/mainIndex/definition/storedSource, /items/statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 응답에 선택 사항 속성 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 응답에 선택 사항 속성 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'definition/oneOf[subschema #2: 벡터 검색 인덱스 정의]/storedSource' 추가
  • 응답에 선택 사항 속성 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 응답에 선택 사항 속성 'latestDefinition/storedSource, statusDetail/items/mainIndex/definition/storedSource, statusDetail/items/stagedIndex/definition/storedSource'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'definition/oneOf[subschema #2: 벡터 검색 인덱스 정의]/storedSource' 추가
  • 응답에 선택 사항 속성 'azureKeyVault/roleId'를 추가했습니다.
  • 응답에 선택 사항 속성 'azureKeyVault/roleId'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'azureKeyVault/roleId'가 추가되었습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/SearchPlannerAuditView'를 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf'에 'subschema #25: 검색 플래너 감사 유형, subschema #38: Mongotune 이벤트 유형'가 추가되었습니다. 응답 목록
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값이 'results/items/oneOf[subschema #13: 호스팅하다 이벤트]/eventTypeName' 속성 응답에 추가되었습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_SYSTEMD_OVERRIDES_CHANGED' 열거형 값을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/SearchPlannerAuditView'를 추가했습니다.
  • '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #25: Search Planner Audit Types, subschema #38: Mongotune Event Types'가 추가되었습니다. 응답
  • 새로운 'ALERT_HOST_SSH_SESSION_STARTED' 열거형 값을 '/oneOf[subschema #13: 호스팅하다 이벤트]/eventTypeName' 속성 응답에 추가했습니다.
  • 새로운 'CLUSTER_SYSTEMD_OVERRIDES_CHANGED' 열거형 값을 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • 엔드포인트 추가됨
  • Added the new 'ATLAS_AWS_BACKUP_EXPORT_PRIVATE_ENDPOINT, VOYAGE_EMBEDDING_2_CODE_API_FREE, VOYAGE_EMBEDDING_2_FINANCE_API_FREE, VOYAGE_EMBEDDING_2_LAW_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_3_CODE_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_TEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_NANO_API_FREE, VOYAGE_RERANK_2_5_API_FREE, VOYAGE_RERANK_2_5_LITE_API_FREE, VOYAGE_RERANK_2_API_FREE, VOYAGE_RERANK_2_LITE_API_FREE' enum values to the 'results/items/lineItems/items/sku' response property
  • Added the new 'ATLAS_AWS_BACKUP_EXPORT_PRIVATE_ENDPOINT, VOYAGE_EMBEDDING_2_CODE_API_FREE, VOYAGE_EMBEDDING_2_FINANCE_API_FREE, VOYAGE_EMBEDDING_2_LAW_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_API_FREE, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_3_CODE_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API_FREE, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API_FREE, VOYAGE_EMBEDDING_3_TEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_3_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LARGE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_LITE_API_FREE, VOYAGE_EMBEDDING_4_TEXT_NANO_API_FREE, VOYAGE_RERANK_2_5_API_FREE, VOYAGE_RERANK_2_5_LITE_API_FREE, VOYAGE_RERANK_2_API_FREE, VOYAGE_RERANK_2_LITE_API_FREE' enum values to the 'lineItems/items/sku' response property

2025년 12월 03일 릴리스

  • Added the new 'VOYAGE_EMBEDDING_4_TEXT_API, VOYAGE_EMBEDDING_4_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LARGE_API, VOYAGE_EMBEDDING_4_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LITE_API, VOYAGE_EMBEDDING_4_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_NANO_API, VOYAGE_EMBEDDING_4_TEXT_NANO_AUTOEMBED' enum values to the 'results/items/lineItems/items/sku' response property
  • Added the new 'VOYAGE_EMBEDDING_4_TEXT_API, VOYAGE_EMBEDDING_4_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LARGE_API, VOYAGE_EMBEDDING_4_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_LITE_API, VOYAGE_EMBEDDING_4_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_4_TEXT_NANO_API, VOYAGE_EMBEDDING_4_TEXT_NANO_AUTOEMBED' enum values to the 'lineItems/items/sku' response property

2025년 11월 19일 출시

  • 'results/items/oneOf[subschema #3: App Services 메트릭 경고 구성]/metricThreshold' 응답에 대한 응답 속성 'oneOf' 목록
  • 'results/items/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 응답 속성에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'maintenance_COMPLETED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: 앱 Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: 앱 Services 지표 경고 구성]/metricThreshold' 요청 속성 'oneOf' 목록
  • '/oneOf[subschema #3: App Services 메트릭 경고 구성]/metricThreshold' 응답 속성 ' oneOf' 목록을 사용하세요.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값 추가
  • ''/oneOf[subschema #16: Stream Processor Metric 경고 Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: 앱 Services Metric 경고 Configuration]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #9: 호스팅하다 Metric 경고 구성]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName'에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값이 추가되었습니다.17
  • 요청 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다. '/oneOf[subschema #11: Replica Set Alert Configuration]/threshold/units'
  • 요청 속성 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #13: 서버리스 경고 구성]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다. '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units'
  • 요청 속성 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값 추가
  • '/oneOf[subschema #3: App Services 메트릭 경고 구성]/metricThreshold' 응답 속성 ' oneOf' 목록을 사용하세요.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값 추가
  • ''/oneOf[subschema #16: Stream Processor Metric 경고 Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: 앱 Services Metric 경고 Configuration]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #9: 호스팅하다 Metric 경고 구성]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: App Services 메트릭 경고 구성]/metricThreshold' 응답 속성 ' oneOf' 목록을 사용하세요.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값 추가
  • ''/oneOf[subschema #16: Stream Processor Metric 경고 Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: 앱 Services Metric 경고 Configuration]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #9: 호스팅하다 Metric 경고 구성]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: 앱 Services 지표 경고 구성]/metricThreshold' 요청 속성 'oneOf' 목록
  • '/oneOf[subschema #3: App Services 메트릭 경고 구성]/metricThreshold' 응답 속성 ' oneOf' 목록을 사용하세요.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값 추가
  • ''/oneOf[subschema #16: Stream Processor Metric 경고 Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #3: 앱 Services Metric 경고 Configuration]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #9: 호스팅하다 Metric 경고 구성]/metricThreshold/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName'에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값이 추가되었습니다.17
  • 요청 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다. '/oneOf[subschema #11: Replica Set Alert Configuration]/threshold/units'
  • 요청 속성 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #13: 서버리스 경고 구성]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다. '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units'
  • 요청 속성 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값이 추가되었습니다.
  • 요청 속성 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units'에 새로운 '십억 픽셀, 백만 토큰' 열거형 값 추가
  • 'results/items/oneOf[subschema #3: 호스팅하다 경고]/eventTypeName' 응답 속성에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor 경고]/eventTypeName' 응답 속성에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #4: 호스트 지표 경고]/currentValue/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: 호스팅하다 경고]/eventTypeName' 응답 속성에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor 경고]/eventTypeName' 응답 속성에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #4: 호스트 지표 경고]/currentValue/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #3: 호스트 경고]/eventTypeName' 응답 속성에 추가했습니다.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #6: Stream Processor 경고]/eventTypeName' 응답 속성에 추가했습니다.
  • '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'maintenance_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #4: 호스팅하다 지표 경고]/currentValue/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #3: 호스트 경고]/eventTypeName' 응답 속성에 추가했습니다.
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 '/oneOf[subschema #6: Stream Processor 경고]/eventTypeName' 응답 속성에 추가했습니다.
  • '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'maintenance_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #4: 호스팅하다 지표 경고]/currentValue/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: App Services 메트릭 경고 구성]/metricThreshold' 응답에 대한 응답 속성 'oneOf' 목록
  • 'results/items/oneOf[subschema #8: 호스팅하다 경고 구성]/eventTypeName' 응답 속성에 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_MONGOT_PAUSE_INITIAL_SYNC' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #7: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'maintenance_COMPLETED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: 앱 Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 'results/items/advancedConfiguration/minimumEnabledTlsProtocol' 응답 속성 에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 선택 사항 속성 'results/items/advancedConfiguration/customOpensslCipherConfigTls13'를 응답에 추가했습니다.
  • 'advancedConfiguration/minimumEnabledTlsProtocol' 응답 속성 에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 요청 속성 'advancedConfiguration/minimumEnabledTlsProtocol'에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 선택 사항 속성 'advancedConfiguration/customOpensslCipherConfigTls13'를 응답에 추가했습니다.
  • 새로운 선택 사항 요청 속성 'advancedConfiguration/customOpensslCipherConfigTls13'가 추가되었습니다.
  • 'advancedConfiguration/minimumEnabledTlsProtocol' 응답 속성 에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 요청 속성 'advancedConfiguration/minimumEnabledTlsProtocol'에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 선택 사항 속성 'advancedConfiguration/customOpensslCipherConfigTls13'를 응답에 추가했습니다.
  • 새로운 선택 사항 요청 속성 'advancedConfiguration/customOpensslCipherConfigTls13'가 추가되었습니다.
  • 'advancedConfiguration/minimumEnabledTlsProtocol' 응답 속성 에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 선택 사항 속성 'advancedConfiguration/customOpensslCipherConfigTls13'를 응답에 추가했습니다.
  • 'advancedConfiguration/minimumEnabledTlsProtocol' 응답 속성 에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 요청 속성 'advancedConfiguration/minimumEnabledTlsProtocol'에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 선택 사항 속성 'advancedConfiguration/customOpensslCipherConfigTls13'를 응답에 추가했습니다.
  • 새로운 선택 사항 요청 속성 'advancedConfiguration/customOpensslCipherConfigTls13'가 추가되었습니다.
  • 응답에 선택 사항 속성 'expirationDate'를 추가했습니다.
  • 응답에 선택 사항 속성 'expirationDate'를 추가했습니다.
  • 응답에 선택 사항 속성 'expirationDate'를 추가했습니다.
  • 새로운 'TLS1_3' 열거형 값을 'minimumEnabledTlsProtocol' 응답 속성 에 추가했습니다.
  • 응답에 선택 사항 속성 'customOpensslCipherConfigTls13'를 추가했습니다.
  • 새로운 'TLS1_3' 열거형 값을 'minimumEnabledTlsProtocol' 응답 속성 에 추가했습니다.
  • 요청 속성 'minimumEnabledTlsProtocol'에 새 'TLS1_3' 열거형 값을 추가했습니다.
  • 응답에 선택 사항 속성 'customOpensslCipherConfigTls13'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'customOpensslCipherConfigTls13'가 추가되었습니다.
  • 응답에 선택 사항 속성 'results/items/deploymentJobId'를 추가했습니다.
  • 응답에 선택 사항 속성 'results/items/deploymentJobId'를 추가했습니다.
  • 응답에 선택 사항 속성 'deploymentJobId'를 추가했습니다.
  • 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 'results/items/oneOf[subschema #1: AZURE]/ 리전' 응답 속성 에 추가했습니다.
  • 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 '/oneOf[subschema #1: AZURE]/ 리전' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: AZURE]/ 리전 '에 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 추가했습니다.
  • 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 'results/items/oneOf[subschema #1: AZURE]/ 리전' 응답 속성 에 추가했습니다.
  • 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 '/oneOf[subschema #1: AZURE]/ 리전' 응답 속성 에 추가했습니다.
  • 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 '/oneOf[subschema #1: AZURE]/ 리전' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #1: AZURE]/ 리전 '에 새로운 'CHILE_CENTRAL, INDONESIA_CENTRAL, MALAYSIA_WEST' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_INSTANCE_SWAPPED, CLUSTER_INSTance_SWAP_CLEARED, CLUSTER_INSTANCE_VM_REBOOT_CLEARED, MONITORING_AGENT_REBALANCE_FLAG, MONITORING_AGENT_REBALANCE_TRIGGERED' 에 추가15 열거형 .
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_EXTERNAL_LOG_SINK_EXPORT_RESUMED, HOST_MONGOT_PAUSE_INITIAL_SYNC, HOST_MONGOT_UNPAUSE_INITIAL_SYNC' 열거형 값을 'results/items/oneOf[subschema #13: 호스팅하다 이벤트]/eventTypeName 속성' 응답에 추가
  • 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #17: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'maintenance_COMPLETED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #14: 호스트 지표 이벤트]/currentValue/units' 응답 속성 에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_INSTANCE_SWAPPED, CLUSTER_INSTance_SWAP_CLEARED, CLUSTER_INSTance_VM_REBOOT_CLEARED, MONITORING_AGENT_REBALance_FLAG, MONITORING_AGENT_REBALANCE_TRIGGERED0s_names/15 속성 ' 에 추가 열거형 .
  • 새로운 'HOST_EXTERNAL_LOG_SINK_EXPORT_DOWN, HOST_EXTERNAL_LOG_SINK_EXPORT_RESUMED, HOST_MONGOT_PAUSE_INITIAL_SYNC, HOST_MONGOT_UNPAUSE_INITIAL_SYNC' 속성 열거형 값을 '/oneOf[subschema #13:Type HostName Events]/oneOf[subschema #:
  • '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #17: NDS 유지 관리 기간 감사 유형]/' 응답 속성 에 새로운 'MAINTENANCE_COMPLETED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #14: 호스팅하다 지표 이벤트]/currentValue/속성' 응답 속성에 새로운 '십억 픽셀, 백만 토큰' 열거형 값을 추가했습니다.
  • 요청 속성 'advancedConfiguration/minimumEnabledTlsProtocol'에 새로운 'TLS1_3' 열거형 값을 추가했습니다.
  • 새로운 선택 사항 요청 속성 'advancedConfiguration/customOpensslCipherConfigTls13'가 추가되었습니다.
  • 'results/items/' 응답 속성 에 'S3_LOG_EXPORT' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/S3LogExport'를 추가했습니다.
  • 'results/items/type' 응답 속성 에 새로운 'S3_LOG_EXPORT' 열거형 값을 추가했습니다.
  • 'path' 요청 매개변수 'integrationType'에 새 열거형 값 'S3_LOG_EXPORT'를 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'S3_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/S3LogExport'를 추가했습니다.
  • 'type' 응답 속성 에 새로운 'S3_LOG_EXPORT' 열거형 값을 추가했습니다.
  • 'path' 요청 매개변수 'integrationType'에 새 열거형 값 'S3_LOG_EXPORT'를 추가했습니다.
  • 요청 판별자에 'S3_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/S3LogExport' 추가
  • 'results/items/' 응답 속성 에 'S3_LOG_EXPORT' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/S3LogExport'를 추가했습니다.
  • 'results/items/type' 응답 속성 에 새로운 'S3_LOG_EXPORT' 열거형 값을 추가했습니다.
  • 'path' 요청 매개변수 'integrationType'에 새 열거형 값 'S3_LOG_EXPORT'를 추가했습니다.
  • 요청 속성 'type'에 새 'S3_LOG_EXPORT' 열거형 값을 추가했습니다.
  • 요청 판별자에 'S3_LOG_EXPORT' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/S3LogExport' 추가
  • 'results/items/' 응답 속성 에 'S3_LOG_EXPORT' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/S3LogExport'를 추가했습니다.
  • 'results/items/type' 응답 속성 에 새로운 'S3_LOG_EXPORT' 열거형 값을 추가했습니다.
  • 'path' 요청 매개변수 'integrationType'에 새 열거형 값 'S3_LOG_EXPORT'를 추가했습니다.
  • 요청 속성 'type'에 새 'S3_LOG_EXPORT' 열거형 값을 추가했습니다.
  • 응답 속성 'results/items/roleNames, results/items/teamId'가 필수 항목이 되었습니다.
  • 응답 속성 'results/items/roleNames, results/items/teamId'가 필수 항목이 되었습니다.
  • 응답 속성 'roleNames, teamId'가 필수 항목이 되었습니다.
  • 응답 속성 'results/items/roleNames, results/items/teamId'가 필수 항목이 되었습니다.
  • 요청 속성 'services/items/'에 새로운 ' AI 모델, 자동 임베딩' 열거형 값 추가
  • 새로운 'ADMIN_OVERRIDE_PAYMENT_METHOD_DELETED, CREDIT_MOVED' 열거형 값을 'results/items/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 속성에 추가했습니다.
  • 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'ORG_BANK_ACCOUNT_ADDED, ORG_BANK_ACCOUNT_UPDATED, ORG_WALLET_ADDED, ORG_WALLET_UPDATED' 열거형 값을 추가했습니다.
  • 새로운 'ADMIN_OVERRIDE_PAYMENT_METHOD_DELETED, CREDIT_MOVED' 열거형 값을 '/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'ORG_BANK_ACCOUNT_ADDED, ORG_BANK_ACCOUNT_UPDATED, ORG_WALLET_ADDED, ORG_WALLET_UPDATED' 열거형 값을 추가했습니다.
  • Added the new 'VOYAGE_EMBEDDING_2_CODE_API, VOYAGE_EMBEDDING_2_CODE_AUTOEMBED, VOYAGE_EMBEDDING_2_FINANCE_API, VOYAGE_EMBEDDING_2_FINANCE_AUTOEMBED, VOYAGE_EMBEDDING_2_LAW_API, VOYAGE_EMBEDDING_2_LAW_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_API, VOYAGE_EMBEDDING_3_5_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API, VOYAGE_EMBEDDING_3_5_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_3_CODE_API, VOYAGE_EMBEDDING_3_CODE_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_API, VOYAGE_EMBEDDING_3_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LARGE_API, VOYAGE_EMBEDDING_3_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LITE_API, VOYAGE_EMBEDDING_3_TEXT_LITE_AUTOEMBED, VOYAGE_RERANK_2_5_API, VOYAGE_RERANK_2_5_LITE_API, VOYAGE_RERANK_2_API, VOYAGE_RERANK_2_LITE_API' enum values to the 'results/items/lineItems/items/sku' response property
  • Added the new 'VOYAGE_EMBEDDING_2_CODE_API, VOYAGE_EMBEDDING_2_CODE_AUTOEMBED, VOYAGE_EMBEDDING_2_FINANCE_API, VOYAGE_EMBEDDING_2_FINANCE_AUTOEMBED, VOYAGE_EMBEDDING_2_LAW_API, VOYAGE_EMBEDDING_2_LAW_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_5_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_API, VOYAGE_EMBEDDING_3_5_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_5_TEXT_LITE_API, VOYAGE_EMBEDDING_3_5_TEXT_LITE_AUTOEMBED, VOYAGE_EMBEDDING_3_CODE_API, VOYAGE_EMBEDDING_3_CODE_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_PIXELS_AUTOEMBED, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_API, VOYAGE_EMBEDDING_3_MULTIMODAL_TOKENS_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_API, VOYAGE_EMBEDDING_3_TEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_API, VOYAGE_EMBEDDING_3_TEXT_CONTEXT_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LARGE_API, VOYAGE_EMBEDDING_3_TEXT_LARGE_AUTOEMBED, VOYAGE_EMBEDDING_3_TEXT_LITE_API, VOYAGE_EMBEDDING_3_TEXT_LITE_AUTOEMBED, VOYAGE_RERANK_2_5_API, VOYAGE_RERANK_2_5_LITE_API, VOYAGE_RERANK_2_API, VOYAGE_RERANK_2_LITE_API' enum values to the 'lineItems/items/sku' response property
  • 요청 속성 'filters/skuServices/items/'에 새로운 'AI 모델, 자동 임베딩' 열거형 값 추가

2025년 11월 10일 출시

  • 'results/items/streamConfig/ 계층' 응답 속성 에 새로운 'SP2, SP5, SP50' 열거형 값을 추가했습니다.
  • 'streamConfig/ 계층' 응답 속성 에 새로운 'SP2, SP5, SP50' 열거형 값 추가
  • 요청 속성 'streamConfig/ 계층 '에 새로운 'SP2, SP5, SP50' 열거형 값을 추가했습니다.
  • 'streamConfig/ 계층' 응답 속성 에 새로운 'SP2, SP5, SP50' 열거형 값 추가
  • 'streamConfig/ 계층' 응답 속성 에 새로운 'SP2, SP5, SP50' 열거형 값 추가
  • 응답에 선택 사항 속성 '계층'를 추가했습니다.
  • 응답에 선택 사항 속성 '계층'를 추가했습니다.
  • 상태가 '400'인 실패 응답을 추가했습니다.
  • 새로운 선택 사항 요청 속성 '계층'가 추가되었습니다.
  • 응답에 선택 사항 속성 'results/items/계층'를 추가했습니다.
  • 'streamConfig/ 계층' 응답 속성 에 새로운 'SP2, SP5, SP50' 열거형 값 추가

2025년 11월 04일 출시

  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성 에 추가되었습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성 에 추가되었습니다.
  • 요청 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다. 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/'
  • 26요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema # {속성}2: Azure 리전 복제 사양]/regionName/oneOf[subschema1 #: AWS 리전]/'
  • 26요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema # {속성}3: GCP 리전 복제 사양]/regionName/oneOf[subschema1 #: AWS 리전]/'
  • 요청 속성 에 새로운 'AP_EAST_,2 AP_SOUTHEAST_64 ' 열거형 값이1 추가되었습니다.: AWS 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다.
  • 'providerSettings/oneOf[subschema #1: Cloud Service 제공자 Settings for a 클러스터]/regionName' 응답 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 요청 속성 'providerSettings/oneOf[subschema #1: Cloud Service Provider Settings for a Cluster]/regionName'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성 에 추가되었습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/oneOf[subschema #1에 추가되었습니다. : AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/' 응답 속성 에 추가되었습니다.
  • 요청 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다. 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/'
  • 26요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema # {속성}2: Azure 리전 복제 사양]/regionName/oneOf[subschema1 #: AWS 리전]/'
  • 26요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema # {속성}3: GCP 리전 복제 사양]/regionName/oneOf[subschema1 #: AWS 리전]/'
  • 요청 속성 에 새로운 'AP_EAST_,2 AP_SOUTHEAST_64 ' 열거형 값이1 추가되었습니다.: AWS 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다.
  • 'results/items/oneOf[subschema #3: AWS]/regionName' 응답 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 '/oneOf[subschema #3: AWS]/regionName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #3: AWS]/regionName'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: AWS]/regionName' 응답 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 '/oneOf[subschema #3: AWS]/regionName' 응답 속성 에 추가했습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 '/oneOf[subschema #3: AWS]/regionName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #3: AWS]/regionName'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 'awsKms/ 리전' 응답 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값 추가
  • 'awsKms/ 리전' 응답 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값 추가
  • 요청 속성 'awsKms/ 리전 '에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]/' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 'results/items/oneOf[subschema #2: AWS Key Management Service EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]/' 응답 속성
  • 'results/items/regionName/oneOf[subschema #2: AWS 리전]/' 응답 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 '/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]/에 추가되었습니다. ' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 '/oneOf[subschema #2: AWS Key Management Service EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]에 추가되었습니다. /' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 'regionName/oneOf[subschema #2: AWS 리전]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'AP_EAST_,2 AP_SOUTHEAST_61 ' 열거형 값이 추가되었습니다 . ]/'2
  • 요청 속성에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다. '/oneOf[subschema #2: AWS Key Management Service EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]/'
  • 요청 속성 'regionName/oneOf[subschema #2: AWS 리전]/'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 추가했습니다.
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 '/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]/에 추가되었습니다. ' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 '/oneOf[subschema #2: AWS Key Management Service EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: AWS 리전]에 추가되었습니다. /' 응답 속성
  • 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값을 'regionName/oneOf[subschema #2: AWS 리전]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS 감사]/eventTypeName' 응답 속성에 새로운 'STREAM_TENANT_OPERATIONAL_LOGS' 열거형 값을 추가했습니다.
  • 새로운 'STREAM_TENANT_OPERATIONAL_LOGS' 열거형 값을 '/oneOf[subschema #15: NDS 감사]/eventTypeName' 응답 속성에 추가했습니다.
  • 요청 속성 에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다. 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: AWS 리전 복제 사양]/regionName/oneOf[subschema #1: AWS 리전]/'
  • 26요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema # {속성}2: Azure 리전 복제 사양]/regionName/oneOf[subschema1 #: AWS 리전]/'
  • 26요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema # {속성}3: GCP 리전 복제 사양]/regionName/oneOf[subschema1 #: AWS 리전]/'
  • 요청 속성 에 새로운 'AP_EAST_,2 AP_SOUTHEAST_64 ' 열거형 값이1 추가되었습니다.: AWS 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: AWS 리전]/'에 새로운 'AP_EAST_2, AP_SOUTHEAST_6' 열거형 값이 추가되었습니다.

2025년 10월 23일 출시

  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: NDS 자동 확장 감사 Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 'results/items/oneOf[subschema #1 /'2 응답 속성
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: NDS 자동 확장 감사 types]/' 응답 속성에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 '/oneOf[subschema11/oneOfschema2 응답에 추가되었습니다. 속성
  • 요청 속성 에 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값이 추가되었습니다.112
  • 요청 속성에 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 요청 속성 에 추가했습니다.1 2'
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: NDS 자동 확장 감사 types]/' 응답 속성에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 '/oneOf[subschema11/oneOfschema2 응답에 추가되었습니다. 속성
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: NDS 자동 확장 감사 types]/' 응답 속성에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 '/oneOf[subschema11/oneOfschema2 응답에 추가되었습니다. 속성
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: NDS 자동 확장 감사 types]/' 응답 속성에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 '/oneOf[subschema11/oneOfschema2 응답에 추가되었습니다. 속성
  • 요청 속성 에 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값이 추가되었습니다.112
  • 요청 속성에 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 요청 속성 에 추가했습니다.1 2'
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName/oneOf[subschema #15: NDS 자동 확장 감사 유형]/' 속성 응답에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 'results/items/oneOf]/[subschema7 #Name]에 추가했습니다. '2 응답 속성
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 'results/items/oneOf[subschema #7: Any Other 경고]/eventTypeName/oneOf[subschema #15: NDS 자동 확장 감사 유형]/' 속성 응답에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 'results/items/oneOf]/[subschema7 #Name]에 추가했습니다. '2 응답 속성
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #7: 기타 경고]/eventTypeName/oneOf[subschema #15: NDS 자동 확장 감사 유형]/' 속성에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 '/oneOf[subschema #7: 기타 경고]/eventTypeName/oneOf[subschema #2: Cps 백업 이벤트 유형]/' 속성에 추가했습니다.
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #7: 기타 경고]/eventTypeName/oneOf[subschema #15: NDS 자동 확장 감사 유형]/' 속성에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 '/oneOf[subschema #7: 기타 경고]/eventTypeName/oneOf[subschema #2: Cps 백업 이벤트 유형]/' 속성에 추가했습니다.
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other 경고 Configurations]/eventTypeName/oneOf[subschema #12: NDS 자동 확장 감사 Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 'results/items/oneOf[subschema #1 /'2 응답 속성
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Instance-Fields' 추가
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Instance-Fields' 추가
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Instance-Fields' 추가
  • 새로운 선택 사항 '헤더' 요청 매개변수 'Use-Effective-Instance-Fields' 추가
  • 'results/items/oneOf[subschema #16: NDS 자동 확장 감사]/eventTypeName' 응답 속성에 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 추가했습니다.
  • Added the new 'CLUSTER_IMPORT_FAILED, DEPUTY_SETTINGS_UPDATED, PLAN_APPROVED, PLAN_DECLINED, PREDICTIVE_AUTOSCALING_DISABLED, PREDICTIVE_AUTOSCALING_ENABLED, SHADOW_CLUSTER_CREATE_EXPOSURE, SHADOW_CLUSTER_DELETE_EXPOSURE, SHADOW_CLUSTER_RECORDING_STATUS_UPDATE' 열거형 values to the 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' response 속성
  • 새로운 CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을 'results/items/oneOf/[subschemaNames]1 pstsubType5 Backup}에 추가했습니다. ' 응답 속성
  • 새로운 'CLUSTER_AUTO_SHARDING_INITIATED' 열거형 값을 '/oneOf[subschema #16: NDS 자동 확장 감사]/eventTypeName' 속성 응답에 추가했습니다.
  • Added the new 'CLUSTER_IMPORT_FAILED, DEPUTY_SETTINGS_UPDATED, PLAN_APPROVED, PLAN_DECLINED, PREDICTIVE_AUTOSCALING_DISABLED, PREDICTIVE_AUTOSCALING_ENABLED, SHADOW_CLUSTER_CREATE_EXPOSURE, SHADOW_CLUSTER_DELETE_EXPOSURE, SHADOW_CLUSTER_RECORDING_STATUS_UPDATE' 열거형 values to the '/oneOf[subschema #15: NDS 감사]/eventTypeName' response 속성
  • 새로운 'CPS_COLLECTION_RESTORE_CANCELED, CPS_COLLECTION_RESTORE_FAILED, CPS_COLLECTION_RESTORE_PARTIAL_SUCCESS, CPS_COLLECTION_RESTORE_SUCCESSFUL' 열거형 값을1 '/oneOf[subschema5 #/ / 속성 ]
  • 응답에 선택 사항 속성 'results/items/gcpConnectionIds'를 추가했습니다.
  • 응답에 선택 사항 속성 'gcpConnectionIds'를 추가했습니다.
  • 새로운 선택 사항 요청 속성 'gcpConnectionIds'가 추가되었습니다.
  • 응답에 선택 사항 속성 'gcpConnectionIds'를 추가했습니다.
  • 새로운 'AWS_PAYMENT_PAID' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName/oneOf[subschema #4: 제휴하다 이벤트 유형]/' 응답 속성에 추가했습니다.
  • 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'ORGANIZATION_VOYAGE_SETTINGS_CREATED, ORGANIZATION_VOYAGE_SETTINGS_DELETED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: NDS 감사]/eventTypeName' 응답 속성에 새로운 'SHADOW_CLUSTER_ORG_OPT_IN, SHADOW_CLUSTER_ORG_OPT_OUT' 열거형 값을 추가했습니다.
  • 새로운 'AWS_PAYMENT_PAID' 열거형 값을 '/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName/oneOf[subschema #4: 제휴하다 이벤트 유형]/' 속성 응답에 추가했습니다.
  • 새로운 'ORGANIZATION_VOYAGE_SETTINGS_CREATED, ORGANIZATION_VOYAGE_SETTINGS_DELETED' 열거형 값을 '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'SHADOW_CLUSTER_ORG_OPT_IN,SHADOW_CLUSTER_ORG_OPT_OUT' 열거형 값을 '/oneOf[subschema #7: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • Added the new 'ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_SAME_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP5' enum values to the 'results/items/lineItems/items/sku' response property
  • Added the new 'ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AWS_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AWS_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_AZURE_STREAM_PROCESSING_DATA_TRANSFER_SAME_CONTINENT, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_AZURE_STREAM_PROCESSING_INSTANCE_SP5, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_DIFFERENT_REGION, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_INTERNET, ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER_SAME_REGION, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP2, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP5' enum values to the 'lineItems/items/sku' response property

2025년 10월 21일 출시

  • 'results/items/oneOf[subschema #11: 복제본 세트 경고 구성]/threshold/units' 응답 속성에 새로운 'px, tokens' 열거형 값 추가
  • 'results/items/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #16: Stream Processor 지표 경고 구성]/threshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: 앱 Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #9: 호스팅하는 지표 경고 구성]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값 추가
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #11: 복제본 세트 경고 Configuration]/threshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'pixels, tokens' 열거형 값을 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units' 속성 응답에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #13: 서버리스 경고 구성]/metricThreshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units'
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #11: 복제본 세트 경고 Configuration]/threshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'pixels, tokens' 열거형 값을 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units' 속성 응답에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #11: 복제본 세트 경고 Configuration]/threshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'pixels, tokens' 열거형 값을 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units' 속성 응답에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #11: 복제본 세트 경고 Configuration]/threshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 속성 응답에 추가했습니다.
  • '/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • 새로운 'pixels, tokens' 열거형 값을 '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units' 속성 응답에 추가했습니다.
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #11: 복제본 세트 Alert Configuration]/threshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #13: 서버리스 경고 구성]/metricThreshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #16: Stream Processor Metric Alert Configuration]/threshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #3: App Services Metric Alert Configuration]/metricThreshold/units'
  • 요청 속성 에 새로운 'px, tokens' 열거형 값이 추가되었습니다. '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold/units'
  • 'results/items/oneOf[subschema #4: Host Metric Alerts]/currentValue/units' 응답 속성 에 새로운 'px, tokens' 열거형 값 추가
  • 'results/items/oneOf[subschema #4: Host Metric Alerts]/currentValue/units' 응답 속성 에 새로운 'px, tokens' 열거형 값 추가
  • '/oneOf[subschema #4: 호스팅하다 지표 경고]/currentValue/units' 응답 속성에 새로운 'pixels, tokens' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #4: 호스팅하다 지표 경고]/currentValue/units' 응답 속성에 새로운 'pixels, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #11: 복제본 세트 경고 구성]/threshold/units' 응답 속성에 새로운 'px, tokens' 열거형 값 추가
  • 'results/items/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/threshold/units' 응답 속성에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #13: 서버리스 경고 Configuration]/metricThreshold/units' 응답 속성에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #14: Flex 경고 Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #16: Stream Processor 지표 경고 구성]/threshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: 앱 Services Metric Alert Configuration]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #9: 호스팅하는 지표 경고 구성]/metricThreshold/units' 응답 속성 에 새로운 'px, tokens' 열거형 값 추가
  • 'results/items/oneOf[subschema #14: Host Metric Events]/currentValue/units' 응답 속성 에 새로운 'px, tokens' 열거형 값 추가
  • 새로운 'px, tokens' 열거형 값을 '/oneOf[subschema #14: Host Metric Events]/currentValue/units' 응답 속성 에 추가했습니다.

2025년 10월 10일 출시

  • 'results/items/oneOf[subschema #6: 청구 Events]/eventTypeName' 응답 속성 에 새로운 'BECAME_LINKED_ORG, CROSS_ORG_OPERATION_TICKET_TRACKING' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #6: 청구 이벤트]/eventTypeName' 응답 속성에 새로운 'BECAME_LINKED_ORG, CROSS_ORG_OPERATION_TICKET_TRACKING' 열거형 값을 추가했습니다.

2025년 10월 09일 출시

  • 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값을 추가했습니다.
  • 새로운 'FTS_INDEX_TALE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값이 추가되었습니다.14
  • 새로운 'FTS_INDEX_TALE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_TALE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'FTS_INDEX_TALE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값이 추가되었습니다.14
  • 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값을 추가했습니다.
  • 새로운 'FTS_INDEX_STALE' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #4: Full Text Search 인덱스 감사 유형]/' 속성 응답에 추가했습니다.
  • 새로운 'FTS_INDEX_STALE' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #4: Full Text Search 인덱스 감사 유형]/' 속성 응답에 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #4: FTS 인덱스 감사 유형]/' 응답 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #12: FTS 인덱스 감사]/eventTypeName' 응답 속성 에 새로운 'FTS_INDEX_TALE' 열거형 값을 추가했습니다.
  • 새로운 'FTS_INDEX_TALE' 열거형 값을 '/oneOf[subschema #12: FTS 인덱스 감사]/eventTypeName' 응답 속성 에 추가했습니다.

2025년 10월 01일 출시

  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED' 열거형 값을 추가했습니다.
  • 선택적 속성 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveAnalyticsSpecs, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveElectableSpecs, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveReadOnlySpecs, results/items/replicationSpecs /items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs , results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs, results/items/replicationSpecs/items/regionConf igs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs, results/ items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs, results/items/useAwsTimeBasedSnapshotCopyForFastInitialSync'를 응답에 추가합니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsSpecs'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 되었습니다.
  • 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs, useAwsTimeBasedSnapshotCopyForFastInitialSync 응답에
  • 새로운 선택적 요청 속성 'useAwsTimeBasedSnapshotCopyForFastInitialSync'가 추가되었습니다.
  • 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs, useAwsTimeBasedSnapshotCopyForFastInitialSync 응답에
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsSpecs'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 되었습니다.
  • 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/EffectiveReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/EffectiveReadOnlySpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveAnalyticsSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveElectableSpecs, replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/EffectiveReadOnlySpecs, useAwsTimeBasedSnapshotCopyForFastInitialSync 응답에
  • 새로운 선택적 요청 속성 'useAwsTimeBasedSnapshotCopyForFastInitialSync'가 추가되었습니다.
  • 응답에 선택적 쓰기 전용 속성 'deleteSnapshots'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'deleteSnapshots'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'deleteSnapshots'을 추가했습니다.
  • 새로운 선택적 요청 속성 'deleteSnapshots' 추가
  • 'dbName' 요청 속성의 maxLength가 '64'(으)로 설정하다 되었습니다.
  • 'definition/oneOf[subschema #1: 텍스트 검색 인덱스 정의]/mappings/dynamic' 요청 속성 유형/형식이 'boolean'/''에서 ' 객체'/''로 변경됨
  • 새로운 선택적 요청 속성 'definition/oneOf[subschema #1: 텍스트 검색 인덱스 정의]/typeSets'가 추가되었습니다.
  • 'definition/oneOf[subschema #1: 텍스트 검색 인덱스 정의]/mappings/dynamic' 요청 속성 유형/형식이 'boolean'/''에서 ' 객체'/''로 변경됨
  • 새로운 선택적 요청 속성 'definition/oneOf[subschema #1: 텍스트 검색 인덱스 정의]/typeSets'가 추가되었습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_INSTANCE_VM_RESTART_CLEARED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 새로운 'HOST_SEARCH_NODE_INDEX_FAILED, HOST_SEARCH_NODE_UNBLOCKED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_INSTANCE_VM_RESTART_CLEARED' 열거형 값을 추가했습니다.
  • 새로운 'HOST_SEARCH_NODE_INDEX_FAILED, HOST_SEARCH_NODE_UNBLOCKED' 열거형 값을 '/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsSpecs'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsSpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsSpecs'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/readOnlySpecs'가 읽기 전용이 되었습니다.
  • 새로운 선택적 요청 속성 'useAwsTimeBasedSnapshotCopyForFastInitialSync'가 추가되었습니다.
  • '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams'를 응답의 'results/items/' 응답 속성 'oneOf' 목록에 추가합니다.
  • '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams'를 응답 본문 'oneOf' 목록에 추가합니다.
  • '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams'를 요청 본문 'oneOf' 목록에 추가합니다.
  • '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams'를 응답의 'results/items/' 응답 속성 'oneOf' 목록에 추가합니다.
  • '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams'를 요청 본문 'oneOf' 목록에 추가합니다.
  • '#/components/schemas/PagerDuty, #/components/schemas/ Slack, #/components/schemas/DataDog, #/components/schemas/NewRelic, #/components/schemas/OpsGenie, #/components/schemas/VictorOps #/components/schemas/Webhook, #/components/schemas/Prometheus, #/components/schemas/MicrosoftTeams'를 응답의 'results/items/' 응답 속성 'oneOf' 목록에 추가합니다.
  • 응답에 선택적 속성 'results/items/streamConfig/maxTierSize'를 추가했습니다.
  • 응답에 선택적 속성 'streamConfig/maxTierSize'를 추가했습니다.
  • 새로운 선택적 요청 속성 'streamConfig/maxTierSize' 추가
  • 응답에 선택적 속성 'streamConfig/maxTierSize'를 추가했습니다.
  • 응답에 선택적 속성 'streamConfig/maxTierSize'를 추가했습니다.
  • 응답에 선택적 속성 'streamConfig/maxTierSize'를 추가했습니다.
  • 새로운 'ORG_BAAS_EOL_EXTENSION_ACCEPTED, ORG_BAAS_EOL_EXTENSION_CANCELED, ORG_BAAS_EOL_EXTENSION_PENDING, SANDBox_CONFIG_DELETED, SANDBox_TEMevenPLATE_UPDATED' 열거형 값을 'results/items/one0]/EventsName 속성 응답 유형}8 속성 에 추가했습니다.
  • '/oneOf]/[subschema #'8 Events 속성 에 새로운 'ORG_BAAS_EOL_EXTENSION_ACCEPTED, ORG_BAAS_EOL_EXTENSION_CANCELED, ORG_BAAS_EOL_EXTENSION_PENDING, SANDBox_CONFIG_DELETED, SANDBox_TEMPLATE_UPDATED' 열거형 값을 추가했습니다.
  • Added the new 'ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_1, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_2, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_3, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_4, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_5, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_6, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_7' 열거형 values to the 'results/items/lineItems/ items/sku '응답 속성
  • Added the new 'ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_1, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_2, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_3, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_4, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_5, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_6, ATLAS_AWS_TIME_BASED_SNAPSHOT_COPY_LEVEL_7' 열거형 values to the 'lineItems/items/sku' 응답 속성

2025년 9월 30일 출시

  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.
  • API 버전이 '2023-01-01'인 엔드포인트가 종료 날짜 '2025-09-30'에 도달하여 제거되었습니다.

2025년 9월 23일 출시

  • 응답에 대한 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #36: 쿼리 형태 이벤트 유형' 추가
  • 응답에 대한 '/oneOf[subschema #1: Any Other Events]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #36: 쿼리 형태 이벤트 유형'을 추가했습니다.

2025년 9월 22일 출시

  • 응답에 선택적 속성 'results/items/connections/items/ 인증/method'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/method'를 추가했습니다.
  • 새로운 선택적 요청 속성 'connections/items/ 인증/method' 추가
  • 응답에 선택적 속성 'connections/items/ 인증/method'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/method'를 추가했습니다.
  • 응답에 선택적 속성 'results/items/ 인증/method'를 추가했습니다.
  • 응답에 선택적 속성 '/ 인증/method'를 추가했습니다.
  • 새로운 선택적 요청 속성 '/ 인증/method' 추가
  • 응답에 선택적 속성 '/ 인증/method'를 추가했습니다.
  • 응답에 선택적 속성 '/ 인증/method'를 추가했습니다.
  • 새로운 선택적 요청 속성 '/ 인증/method' 추가
  • 응답에 선택적 속성 'connections/items/ 인증/method'를 추가했습니다.

2025년 9월 17일 출시

  • 응답에 선택적 속성 'customSessionTimeout'을 추가했습니다.
  • 응답에 선택적 속성 'customSessionTimeout'을 추가했습니다.
  • 새로운 선택적 요청 속성 'customSessionTimeout'이 추가되었습니다.

2025년 9월 11일 출시

  • 응답에 선택적 속성 'results/items/internalClusterRole'을 추가했습니다.
  • 응답에 선택적 속성 'internalClusterRole'을 추가했습니다.
  • 응답에 선택적 속성 'internalClusterRole'을 추가했습니다.
  • 응답에 선택적 속성 'internalClusterRole'을 추가했습니다.
  • 응답에 선택적 속성 'summaries/items/systemQuery'를 추가했습니다.
  • 응답에 선택적 속성 'queryStats/systemQuery'를 추가했습니다.
  • 새로운 'CLUSTER_CONNECTION_GET_NAMESPACES_AND_PROJECT_SQL_SCHEMA_DATA' 열거형 값을 'results/items/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName/oneOf[subschema #4: 클러스터 연결 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'SSH_KEY_NDS_HOST_ACCESS_LEVEL_CHANGED' 열거형 값을 'results/items/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_CONNECTION_GET_NAMESPACES_AND_PROJECT_SQL_SCHEMA_DATA' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'SSH_KEY_NDS_HOST_ACCESS_LEVEL_CHANGED' 열거형 값을 '/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 ' GCP' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/GCPAccountDetails'를 추가했습니다.
  • 응답에 선택적 속성 'results/items/gcpServiceAttachmentUris'를 추가했습니다.
  • 응답에 선택적 속성 'gcpServiceAttachmentUris'를 추가했습니다.
  • 새로운 선택적 요청 속성 'gcpServiceAttachmentUris'가 추가되었습니다.
  • 응답에 선택적 속성 'gcpServiceAttachmentUris'를 추가했습니다.

2025년 8월 29일 릴리스

  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal, #/components/schemas/CloudProviderAccessGCPServiceAccount'를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal, #/components/schemas/CloudProviderAccessGCPServiceAccount'를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/CloudProviderAccessAWSIAMRole, #/components/schemas/CloudProviderAccessAzureServicePrincipal, #/components/schemas/CloudProviderAccessGCPServiceAccount'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'results/items/connections/items/ 인증/clientSecret'을 추가했습니다.
  • 선택적 속성 'results/items/connections/items/ 인증/clientId, results/items/connections/items/ 인증/httpsCaPem, results/items/connections/items/ 인증/saslOauthbearerExtensions, results/items/connections/items/ 인증/scope, results/items/connections/items/ 인증/tokenEndpointUrl'을 응답에 추가합니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/clientSecret'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/clientId, connections/items/ 인증/httpsCaPem, connections/items/ 인증/saslOauthbearerExtensions, connections/items/ 인증/scope, connections/items/ 인증/tokenEndpointUrl' to the response.
  • 새로운 선택적 요청 속성 'connections/items/ 인증/clientId, connections/items/ 인증/clientSecret, connections/items/ 인증/httpsCaPem, connections/items/ 인증/saslOauthbearerExtensions, connections/items/ 인증/scope, connections/items / 인증/tokenEndpointUrl'
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/clientSecret'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/clientId, connections/items/ 인증/httpsCaPem, connections/items/ 인증/saslOauthbearerExtensions, connections/items/ 인증/scope, connections/items/ 인증/tokenEndpointUrl' to the response.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/clientSecret'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/clientId, connections/items/ 인증/httpsCaPem, connections/items/ 인증/saslOauthbearerExtensions, connections/items/ 인증/scope, connections/items/ 인증/tokenEndpointUrl' to the response.
  • 응답에 선택적 쓰기 전용 속성 'results/items/ 인증/clientSecret'을 추가했습니다.
  • 선택적 속성 'results/items/ 인증/clientId, results/items/ 인증/httpsCaPem, results/items/ 인증/saslOauthbearerExtensions, results/items/ 인증/scope, results/items/ 인증/tokenEndpointUrl' to the response.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/clientSecret'을 추가했습니다.
  • 선택적 속성 '/ 인증/clientId, / 인증/httpsCaPem, / 인증/saslOauthbearerExtensions, / 인증/scope, / 인증/tokenEndpointUrl' to the response.
  • 새로운 선택적 요청 속성 '/ 인증/clientId, / 인증/clientSecret, / 인증/httpsCaPem, / 인증/saslOauthbearerExtensions, / 인증/scope, / 인증/tokenEndpointUrl'
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/clientSecret'을 추가했습니다.
  • 선택적 속성 '/ 인증/clientId, / 인증/httpsCaPem, / 인증/saslOauthbearerExtensions, / 인증/scope, / 인증/tokenEndpointUrl' to the response.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/clientSecret'을 추가했습니다.
  • 선택적 속성 '/ 인증/clientId, / 인증/httpsCaPem, / 인증/saslOauthbearerExtensions, / 인증/scope, / 인증/tokenEndpointUrl' to the response.
  • 새로운 선택적 요청 속성 '/ 인증/clientId, / 인증/clientSecret, / 인증/httpsCaPem, / 인증/saslOauthbearerExtensions, / 인증/scope, / 인증/tokenEndpointUrl'
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/clientSecret'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/clientId, connections/items/ 인증/httpsCaPem, connections/items/ 인증/saslOauthbearerExtensions, connections/items/ 인증/scope, connections/items/ 인증/tokenEndpointUrl' to the response.

2025년 8월 28일 릴리스

  • 요청 속성 에 새로운 'GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRED, GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRING' 열거형 값이 추가되었습니다.15
  • 요청 속성 에 새로운 'GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRED, GROUP_SERVICE_ACCOUNT_SECRETS_EXPIRING' 열거형 값이 추가되었습니다.15
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'ONLINE_ARCHIVE_DELETE_AFTER_DATE_UPDATED' 열거형 값을 추가했습니다.
  • 새로운 'ONLINE_ARCHIVE_DELETE_AFTER_DATE_UPDATED' 열거형 값을 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'atlas. 프로젝트. 배포서버.salesSoldM0s' '/items/' 응답 속성 의 판별자 매핑 키
  • 'atlas. 프로젝트. 배포서버.salesSoldM0s' 응답 상태 '200'에 대한 응답 판별자의 매핑 키
  • 'atlas. 프로젝트. 배포서버.salesSoldM0s' 요청 판별자의 매핑 키
  • 'atlas. 프로젝트. 배포서버.salesSoldM0s' 응답 상태 '200'에 대한 응답 판별자의 매핑 키

2025년 8월 20일 릴리스

  • 새로운 'MONITORING_AGENT_OVERRIDES' 열거형 값을 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'MONITORING_AGENT_OVERRIDES' 열거형 값을 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.

2025년 8월 08일 릴리스

  • 응답에 선택적 속성 'gcpServiceAccounts'를 추가했습니다.

2025년 8월 06일 릴리스

  • 'results/items/oneOf[subschema #8: 호스트 경고 구성]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #3: Host Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 '/oneOf[subschema #6: Stream Processor Alerts]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #8: 호스트 경고 구성]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'ATLAS_maintenance_RESET_BY_ADMIN' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_CONNECTION_GET_AGGREGATED_View_INFOS' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION, HOST_MONGOT_SUFFICIENT_DISK_SPACE' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에서 'AUTO_HEALING_CANNOT_REPAIR_INTERNAL, AUTO_HEALING_CANNOT_RESYNC_INTERNAL' 열거형 값을 제거했습니다.
  • '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'ATLAS_maintenance_RESET_BY_ADMIN' 열거형 값을 추가했습니다.
  • 새로운 'CLUSTER_CONNECTION_GET_AGGREGATED_View_INFOS' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Cluster Connection Audit Types]/' 응답 속성 에 추가했습니다.
  • 새로운 'HOST_MONGOT_APPROACHING_STOP_REPLICATION, HOST_MONGOT_SUFFICIENT_DISK_SPACE' 열거형 값을 '/oneOf[subschema #13: Host Events]/eventTypeName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에서 'AUTO_HEALING_CANNOT_REPAIR_INTERNAL, AUTO_HEALING_CANNOT_RESYNC_INTERNAL, MONGOTUNE_ENABLED' 열거형 값을 제거했습니다.
  • 키 'ACTIVE'의 매핑된 값이 응답 상태 '200'에 대한 응답 판별자에서 '#/components/schemas/OrgActiveUserResponse'에서 '#/components/schemas/GroupActiveUserResponse'로 변경되었습니다.
  • 키 'PENDING'의 매핑된 값이 응답 상태 '200'에 대한 응답 판별자에서 '#/components/schemas/OrgPendingUserResponse'에서 '#/components/schemas/GroupPendingUserResponse'로 변경되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse'를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse'가 제거되었습니다.
  • 키 'ACTIVE'의 매핑된 값이 응답 상태 '200'에 대한 응답 판별자에서 '#/components/schemas/OrgActiveUserResponse'에서 '#/components/schemas/GroupActiveUserResponse'로 변경되었습니다.
  • 키 'PENDING'의 매핑된 값이 응답 상태 '200'에 대한 응답 판별자에서 '#/components/schemas/OrgPendingUserResponse'에서 '#/components/schemas/GroupPendingUserResponse'로 변경되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse'를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse'가 제거되었습니다.
  • 새로운 'VERCEL_USAGE_REPORTED' 열거형 값을 'results/items/oneOf[subschema #6: 청구, 결제 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'VERCEL_USAGE_REPORTED' 열거형 값을 '/oneOf[subschema #6: 청구, 결제 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'userId' 추가

2025년 7월 31일 릴리스

  • 'apiKey/roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/postAuthRoleGrants/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'postAuthRoleGrants/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'postAuthRoleGrants/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'postAuthRoleGrants/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roleMappings/items/roleAssignments/items/ 역할 '에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roleAssignments/items/ 역할 '에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roleAssignments/items/ 역할' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roleAssignments/items/ 역할 '에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값이 'results/items/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가되었습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 'results/items/oneOf[subschema #1: SAML]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 'results/items/oneOf[subschema #1: SAML]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값이 'results/items/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가되었습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 'results/items/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 'results/items/oneOf[subschema #3: OIDC WORKLOAD]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 'results/items/oneOf[subschema #3: OIDC WORKLOAD]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #1: OIDC WORKFORCE]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #1: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #2: OIDC WORKLOAD]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #2: OIDC WORKLOAD]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • ' associatedOrgs/items/postAuthRoleGrants/items/ ' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값이 ' associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가되었습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #1: SAML]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #1: SAML]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #3: OIDC WORKLOAD]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #3: OIDC WORKLOAD]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • ' associatedOrgs/items/postAuthRoleGrants/items/ ' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값이 ' associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가되었습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #1: SAML]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #1: SAML]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #3: OIDC WORKLOAD]/ associatedOrgs/items/postAuthRoleGrants/items/' 응답 속성 에 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 '/oneOf[subschema #3: OIDC WORKLOAD]/ associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가했습니다.
  • ' associatedOrgs/items/postAuthRoleGrants/items/ ' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값이 ' associatedOrgs/items/roleMappings/items/roleAssignments/items/ 역할' 응답 속성 에 추가되었습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'apiKey/roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'serviceAccount/roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'apiKey/roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'serviceAccount/roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/items/roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'results/items/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/orgRoles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/orgRoles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'orgRoles/items/'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'orgRole'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • '/roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/orgRoles/items/' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'orgRole'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/roleName'에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.
  • 'roles/items/roleName' 응답 속성 에 새로운 'ORG_STREAM_PROCESSING_ADMIN' 열거형 값을 추가했습니다.

2025년 7월 29일 릴리스

  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다: 호스트 메트릭 경고 ' 응답 속성
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 'results/items/oneOf[subschema #메트릭 경고9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema #9]/ 메트릭 임계값 경고에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 'results/items/one AlertOf[subschema #9 Configuration]/HostmetricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 'results/items/oneOf[subschema #ThresholdMetrics/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 'results/items/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 'results/items/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 'results/items/RawMetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 'results/items/9Of[sub]에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 'results/items/oneOf[subschema #MetricThresholdView'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 'results/items/RawMetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 'results/items/9Of}]schema에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf}]/metricThresholds/oneOf[subschema에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 'results/items/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 'results/items/oneOf[subschema #9: 메트릭 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 'results/items/oneOf[subschema #9: 메트릭 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 'results/items/oneOf[subschema9 #MetricThreshold]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 'results/items/oneOf[subschema #9]/ 메트릭 임계값 경고에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold Configuration]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 'results/items/oneOf[subschema #MetricThreshold]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 'results/items/one AlertOf[subschema #9 Configuration]/HostmetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'에 대한 매핑된 값이 'results/items/oneOf[subschema #9 Configuration}에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다: 호스트 메트릭 경고 ' 응답 속성
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 'results/items/oneOf[subschema #9: ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 'results/items/AlertThreshold}Config에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 'results/items/MetricThreshold View'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 'results/items/oneOf[subschema Configuration]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf[]subschema에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'에 대한 매핑된 값이 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 'results/items/oneOf[subschema Configuration}에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceAlertDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 'results/items/RawMetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[]schema ConfigurationMetrics에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf[}에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 'results/items/oneOf[subschema #9 Configuration}]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostmetricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 'results/items/oneOf[subschema #MetricThreshold]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 'results/items/one AlertOf[subschema #9 Configuration]/Host MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다: 호스트 메트릭 경고 ' 응답 속성
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 'results/items/oneOf[subschema #9]/ metricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 'results/items/oneOf[subschema Configuration]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 'results/items/oneOf[subschema #9]/HostmetricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/Host MetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 'results/items/oneOf[subschema #9]/HostmetricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 'results/items/one AlertOf[subschema #9]/HostmetricThres Configuration에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 'results/items/oneOf[]submetrics/items/oneOf[에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경됨9 ' 응답 속성
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'의 매핑된 값이 'results/items/{MetricThreshold0]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 'results/items/oneOf[subschema #9]/HostmetricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 'results/items/oneOf[subschema Configuration'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 'results/items/oneOf[subschema #메트릭 경고9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 'results/items/oneOf[subschema #9:Metric Host 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema #{results/items/oneOf]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE' 의 매핑된 값이 'results/items/onealertOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'에 대한 매핑된 값이 'results/items/onetOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #9: HostThreshold 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold 경고 구성]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 임계값 경고 구성]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 'results/items/oneOf[subschema #9 Configuration}]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 /metricThres에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/ 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 속성 대한 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 '/oneOf[subschema Metric 구성 #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다: Host MetricThreshold
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '/oneOf[subschema 구성 #9' 속성 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneholdOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema9 메트릭 속성 요청 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 '에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschemaThres 구성 #9' 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자9 속성 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경 요청 .
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThresholdView' 속성 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성 요청 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] request/메트릭스 임계값 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 '/oneOf[subschema #9 Configuration' 요청 / 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 '/oneholdOf[subschema #9 Configuration] 요청 /metricThres AlertView'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 '/oneOf[subschema #9] 요청 '에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 '/oneOf[subschema #9': 호스트 메트릭 경고 구성]/메트릭 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMassRatioRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'에 대한 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '9 / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자9 속성 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 속성 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다 .9
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자9 속성 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자9 속성 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 속성 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 속성 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다9.
  • 판별자 속성 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다 .9
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 변경 속성.
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 요청 속성]/metric에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경 속성.
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 속성 요청 .
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/ 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '/oneOf[subschema Configuration #9:Metric Host 요청 ] 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/ 요청 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 '/oneholdOf[subschema #9' 요청 속성 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 요청 속성 ]/metric에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값 속성 '/oneOf[subschema #9'에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 ' / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'의 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 속성/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 변경 속성 .
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다.
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/ metricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'에 대한 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '9 / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 속성 ] 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschema #9 Configuration 속성 '에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneholdOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema 구성 #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_JOURNAL'에 대한 매핑된 값이 ' / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration response' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschemaThreshold9 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 '/oneOf[subschema #9 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 '/oneholdOf[subschema #9 속성 response'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 '/oneOf[subschema #9'에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView' 속성 되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 '/oneOf[subschema #9]에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMassRatioRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 '/oneOf[subschema #9] 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 '/oneOf[subschema9: Hostmetric Configuration[subschema00}] 응답에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경됨
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '/components/schemas/MaxDiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema9 속성 '에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'에 대한 매핑된 값이 ' / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 구성]/응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9' 응답 속성 호스트 메트릭 임계 속성 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: metric HostThreshold Configuration] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #]: 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 '/oneOf[subschema #MetricThreshold' 응답9 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'에 대한 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold Configuration' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration response]' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다.
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/ metricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'에 대한 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '9 / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 속성 ] 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschema #9 Configuration 속성 '에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneholdOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema 구성 #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_JOURNAL'에 대한 매핑된 값이 ' / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration response' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschemaThreshold9 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 '/oneOf[subschema #9 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 '/oneholdOf[subschema #9 속성 response'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 '/oneOf[subschema #9'에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView' 속성 되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 '/oneOf[subschema #9]에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMassRatioRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 '/oneOf[subschema #9] 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 '/oneOf[subschema9: Hostmetric Configuration[subschema00}] 응답에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경됨
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '/components/schemas/MaxDiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema9 속성 '에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'에 대한 매핑된 값이 ' / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 구성]/응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9' 응답 속성 호스트 메트릭 임계 속성 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: metric HostThreshold Configuration] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #]: 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 '/oneOf[subschema #MetricThreshold' 응답9 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'에 대한 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold Configuration' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration response]' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다.
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/ metricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'에 대한 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '9 / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 속성 ] 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschema #9 Configuration 속성 '에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneholdOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema 구성 #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_JOURNAL'에 대한 매핑된 값이 ' / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration response' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschemaThreshold9 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 '/oneOf[subschema #9 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 '/oneholdOf[subschema #9 속성 response'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 '/oneOf[subschema #9'에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView' 속성 되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 '/oneOf[subschema #9]에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMassRatioRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 '/oneOf[subschema #9] 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 '/oneOf[subschema9: Hostmetric Configuration[subschema00}] 응답에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경됨
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '/components/schemas/MaxDiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema9 속성 '에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'에 대한 매핑된 값이 ' / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 구성]/응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9' 응답 속성 호스트 메트릭 임계 속성 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: metric HostThreshold Configuration] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #]: 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 '/oneOf[subschema #MetricThreshold' 응답9 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'에 대한 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold Configuration' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration response]' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다.
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 /metricThres에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/ 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 속성 대한 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 '/oneOf[subschema Metric 구성 #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다: Host MetricThreshold
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '/oneOf[subschema 구성 #9' 속성 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneholdOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema9 메트릭 속성 요청 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 '에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschemaThres 구성 #9' 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자9 속성 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경 요청 .
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThresholdView' 속성 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성 요청 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] request/메트릭스 임계값 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 '/oneOf[subschema #9 Configuration' 요청 / 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 '/oneholdOf[subschema #9 Configuration] 요청 /metricThres AlertView'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 '/oneOf[subschema #9] 요청 '에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 '/oneOf[subschema #9': 호스트 메트릭 경고 구성]/메트릭 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMassRatioRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'에 대한 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '9 / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자9 속성 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 속성 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다 .9
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자9 속성 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자9 속성 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 속성 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다 .
  • 판별자 속성 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다9.
  • 판별자 속성 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다 .9
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 변경 속성.
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 요청 속성]/metric에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경 속성.
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 속성 요청 .
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9] 요청 속성 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/ 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '/oneOf[subschema Configuration #9:Metric Host 요청 ] 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/ 요청 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 '/oneholdOf[subschema #9' 요청 속성 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 요청 속성 ]/metric에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값 속성 '/oneOf[subschema #9'에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 ' / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다9.
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'의 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsInIndexRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 '/oneOf[subschema #9] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 요청 속성/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 속성 /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 요청 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 변경 속성 .
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 '/oneOf[subschema #9' 요청 속성 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 요청 / 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다.
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/ metricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'에 대한 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '9 / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 속성 ] 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschema #9 Configuration 속성 '에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경됨
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneholdOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema 구성 #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_JOURNAL'에 대한 매핑된 값이 ' / components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9 Configuration response' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 '/oneOf[subschemaThreshold9 속성 ' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경 속성 .
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 변경 속성 .
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 '/oneOf[subschema #9 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 '/oneholdOf[subschema #9 속성 response'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 '/oneOf[subschema #9'에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeAccessesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView' 속성 되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 '/oneOf[subschema #9]에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMassRatioRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 '/oneOf[subschema #9] 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 '/oneOf[subschema9: Hostmetric Configuration[subschema00}] 응답에 속성 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경됨
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '/components/schemas/MaxDiskPartitionspaceUsedJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 '/oneOf[subschema9 속성 '에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 속성 '/oneOf[subschema #9'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'에 대한 매핑된 값이 ' / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '9 / components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 구성]/응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 ]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 ]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이9 '/ 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 '/oneOf[subschema #9' 응답 속성 호스트 메트릭 임계 속성 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold Configuration' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 '/oneOf[subschema #9': 속성 호스트 메트릭 경고 속성 ]/메트릭스 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다.
  • 판별자 속성 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 '/oneOf[subschema #9' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 '/oneOf[subschema #9: metric HostThreshold Configuration] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값이 '/oneOf[subschema #9]/oneOf[subschema #]: 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 '/oneOf[subschema #MetricThreshold' 응답9 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑된 값이 ' # /components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다.9
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'에 대한 매핑된 값이 '/9 속성 /schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 '/oneOf[subschema #9': 속성 Host MetricThreshold View' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsIndexRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 '/oneOf[subschema #9 Configuration]/property/metricThreshold Configuration' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 '/oneOf[subschema #9] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 '/oneOf[subschema #9 Configuration response]' 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ' 응답에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 속성 ]/metricThreshold'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 '/oneOf[subschema #9: Host MetricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 '/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 '/oneOf[subschema #9: 속성 호스트 임계값 경고 속성 ]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 '/oneOf[subschema #9 Configuration] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다.
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 '/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'ASSERT_MSG'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertMsgRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'ASSERT_REGULAR'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertRegularRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'ASSERT_USER'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'ASSERT_WARNING'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/AssertWarningRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgCommandExecutionTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'AVG_READ_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgReadExecutionTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/AvgWriteExecutionTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CACHE_BYTES_READ_INTO'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesReadIntoDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CACHE_BYTES_WRITTEN_FROM'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheBytesWrittenFromDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CACHE_USAGE_DIRTY'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageDirtyDataMetricThresholdView'로 변경되었습니다: 호스트 메트릭 경고 ' 응답 속성
  • 판별자 키 'CACHE_USAGE_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/CacheUsageUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'COMPUTED_MEMORY'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ComputedMemoryDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CONNECTIONS'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CONNECTIONS_MAX'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsMaxRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CONNECTIONS_PERCENT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ConnectionsPercentRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CURSORS_TOTAL_CLIENT_CURSORS_SIZE'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'CURSORS_TOTAL_OPEN'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalOpenRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'CURSORS_TOTAL_TIMED_OUT'의 매핑된 값이 'results/items/oneOf[subschema #메트릭 경고9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/CursorsTotalTimedOutRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_DATA_SIZE_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema #9]/ 메트릭 임계값 경고에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_DATA_SIZE_TOTAL_WO_SYSTEM'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_INDEX_SIZE_TOTAL'의 매핑된 값이 'results/items/one AlertOf[subschema #9 Configuration]/HostmetricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbIndexSizeTotalDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DB_STORAGE_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/DbStorageTotalDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 'results/items/oneOf[subschema #ThresholdMetrics/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 'results/items/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 'results/items/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 'results/items/RawMetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_READ_LATENCY_JOURNAL'의 매핑된 값이 'results/items/9Of[sub]에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 'results/items/oneOf[subschema #MetricThresholdView'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 'results/items/RawMetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 'results/items/9Of}]schema에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf}]/metricThresholds/oneOf[subschema에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 'results/items/TimeMetricThresholdView'에서 '#/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'DOCUMENT_DELETED'의 매핑된 값이 'results/items/oneOf[subschema #9: 메트릭 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentDeletedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DOCUMENT_INSERTED'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentInsertedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DOCUMENT_RETURNED'의 매핑된 값이 'results/items/oneOf[subschema #9: 메트릭 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentReturnedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'DOCUMENT_UPDATED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DocumentUpdatedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'EXTRA_INFO_PAGE_FAULTS'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_DISK_UTILIZATION'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsDiskUtilizationDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_JVM_CURRENT_MEMORY'의 매핑된 값이 'results/items/oneOf[subschema9 #MetricThreshold]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_JVM_MAX_MEMORY'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_MEMORY_MAPPED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryMappedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_MEMORY_RESIDENT'의 매핑된 값이 'results/items/oneOf[subschema #9]/ 메트릭 임계값 경고에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryResidentDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_MEMORY_VIRTUAL'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold Configuration]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FtsMemoryVirtualDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 'results/items/oneOf[subschema #MetricThreshold]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'FTS_PROCESS_CPU_USER'의 매핑된 값이 'results/items/one AlertOf[subschema #9 Configuration]/HostmetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_ACCESSES_NOT_IN_MEMORY'에 대한 매핑된 값이 'results/items/oneOf[subschema #9 Configuration}에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalAccessesNotInMemoryRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_READERS'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema9에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_CURRENT_QUEUE_WRITERS'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'GLOBAL_LOCK_PERCENTAGE'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalLockPercentageRawMetricThresholdView'로 변경되었습니다: 호스트 메트릭 경고 ' 응답 속성
  • 판별자 키 'GLOBAL_PAGE_FAULT_EXCEPTIONS_THROWN'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/GlobalPageFaultExceptionsThrownRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_ACCESSES'의 매핑된 값이 'results/items/oneOf[subschema #9: ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_HITS'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeHitsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISSES'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissesRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'INDEX_COUNTERS_BTREE_MISS_RATIO'의 매핑된 값이 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'JOURNALING_COMMITS_IN_WRITE_LOCK'의 매핑된 값이 'results/items/AlertThreshold}Config에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'JOURNALING_MB'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingMbDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'JOURNALING_WRITE_DATA_FILES_MB'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'LOGical_SIZE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/LogicalSizeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_DATA'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_INDEX'의 매핑된 값이 'results/items/MetricThreshold View'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_QUEUE_DEPTH_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_DATA'의 매핑된 값이 'results/items/oneOf[subschema Configuration]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_INDEX'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_IOPS_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf[]subschema에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_READ_LATENCY_JOURNAL'에 대한 매핑된 값이 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_DATA'의 매핑된 값이 'results/items/oneOf[subschema Configuration}에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceAlertDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_INDEX'의 매핑된 값이 'results/items/oneOf[sub]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_SPACE_USED_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionSpaceUsedJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_DATA'의 매핑된 값이 'results/items/RawMetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_INDEX'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_IOPS_JOURNAL'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_DATA'의 매핑된 값이 'results/items/oneOf[]schema ConfigurationMetrics에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_INDEX'의 매핑된 값이 'results/items/oneOf[}에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_DISK_PARTITION_WRITE_LATENCY_JOURNAL'의 매핑된 값이 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 'results/items/oneOf[subschema #9 Configuration}]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'MAX_SWAP_USAGE_FREE'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageFreeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SWAP_USAGE_USED'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThresholdView'에서 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSwapUsageUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostmetricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 'results/items/oneOf[subschema #MetricThreshold]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_MEMORY_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_NETWORK_IN'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkInDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MAX_SYSTEM_NETWORK_OUT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MaxSystemNetworkOutDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MEMORY_MAPPED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryMappedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MEMORY_RESIDENT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryResidentDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MEMORY_VIRTUAL'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/MemoryVirtualDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_IOWAIT'의 매핑된 값이 'results/items/one AlertOf[subschema #9 Configuration]/Host MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIowaitRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_IRQ'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuIrqRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_NICE'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuNiceRawMetricThresholdView'로 변경되었습니다: 호스트 메트릭 경고 ' 응답 속성
  • 판별자 키 'MUNIN_CPU_SOFTIRQ'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSoftirqRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_STEAL'의 매핑된 값이 'results/items/oneOf[subschema #9]/ metricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuStealRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_SYSTEM'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuSystemRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'MUNIN_CPU_USER'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/MuninCpuUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NETWORK_BYTES_IN'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesInDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NETWORK_BYTES_OUT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/NetworkBytesOutDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NETWORK_NUM_REQUESTS'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NetworkNumRequestsRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_KERNEL'의 매핑된 값이 'results/items/MetricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'NORMALIZED_FTS_PROCESS_CPU_USER'의 매핑된 값이 'results/items/oneOf[subschema Configuration]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_STEAL'의 매핑된 값이 'results/items/oneOf[subschema #9]/HostmetricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'NORMALIZED_SYSTEM_CPU_USER'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/Host MetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_CMD'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterCmdRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_DELETE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterDeleteRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_INSERT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterInsertRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_QUERY'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterQueryRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_CMD'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplCmdRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_DELETE'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplDeleteRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_INSERT'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplInsertRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_REPL_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #9]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterReplUpdateRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_TTL_DELETED'의 매핑된 값이 'results/items/oneOf[subschema #9]/HostmetricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterTtlDeletedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OpCounterUpdateRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPERATIONS_QUERIES_KILLED'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsQueriesKilledRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPERATIONS_SCAN_AND_ORDER'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationsScanAndOrderRawMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'OPERATION_THROTTLING_REJECTED_OPERATIONS'의 매핑된 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'OPLOG_MASTER_LAG_TIME_DIFF'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPLOG_MASTER_TIME'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPLOG_MASTER_TIME_ESTIMATED_TTL'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView'로 변경되었습니다. '9 응답 속성
  • 판별자 키 'OPLOG_RATE_GB_PER_HOUR'의 매핑된 값이 'results/items/one AlertOf[subschema #9]/HostmetricThres Configuration에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/OplogRateGbPerHourDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'OPLOG_SLAVE_LAG_MASTER_TIME'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/OplogSlaveLagMasterTimeMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'QUERY_EXECUTOR_SCANNED'의 매핑된 값이 'results/items/one AlertOf[subschema #9 구성]/HostMetricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'QUERY_EXECUTOR_SCANNED_OBJECTS'의 매핑된 값이 'results/items/oneOf[subschema #Thresholds/oneOf[subschema]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'QUERY_SPILL_TO_DISK_DURING_SORT'의 매핑된 값이 'results/items/oneOf[]submetrics/items/oneOf[에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView'로 변경됨9 ' 응답 속성
  • 판별자 키 'QUERY_TARGETING_SCANNED_OBJECTS_PER_RETURNED'의 매핑 값이 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'QUERY_TARGETING_SCANNED_PER_RETURNED'의 매핑된 값이 'results/items/{MetricThreshold0]에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'RESTARTS_IN_LAST_HOUR'의 매핑된 값이 'results/items/oneOf[subschema #9]/HostmetricThreshold Configuration에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/RestartsInLastHourRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_INDEX_SIZE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/메트릭에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SearchIndexSizeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_FIELDS_IN_INDEX'의 매핑된 값이 'results/items/oneOf[subschema Configuration'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfFieldsIndexRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_ERROR'의 매핑된 값이 'results/items/oneOf[subschema #메트릭 경고9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_SUCCESS'의 매핑된 값이 'results/items/oneOf[subschema #9:Metric Host 에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_NUMBER_OF_QUERIES_TOTAL'의 매핑된 값이 'results/items/oneOf[subschema #{results/items/oneOf]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView'로 변경되었습니다.9 ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_DELETE' 의 매핑된 값이 'results/items/onealertOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterDeleteRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_INSERT'에 대한 매핑된 값이 'results/items/onetOf[subschema #9 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterInsertRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #9: HostThreshold 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SearchOpCounterUpdateRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SEARCH_REPLICATION_LAG'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 임계값 경고 구성]/에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/SearchReplicationLagTimeMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SWAP_USAGE_FREE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageFreeDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SWAP_USAGE_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: metricThreshold 경고 구성]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SwapUsageUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_MEMORY_AVAILABLE'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 임계값 경고 구성]에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryAvailableDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_MEMORY_PERCENT_USED'의 매핑된 값이 'results/items/one AlertOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_MEMORY_USED'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemMemoryUsedDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_NETWORK_IN'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkInDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'SYSTEM_NETWORK_OUT'의 매핑된 값이 'results/items/oneOf[subschema #9: 호스트 메트릭 경고 구성]/metricThreshold에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/SystemNetworkOutDataMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • 판별자 키 'TICKETS_AVAILABLE_READS'의 매핑된 값이 'results/items/oneOf[subschema #9]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableReadsRawMetricThresholdView'로 변경되었습니다: ' 응답 속성
  • 판별자 키 'TICKETS_AVAILABLE_WRITES'의 매핑된 값이 'results/items/oneOf[subschema #9 Configuration}]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/TicketsAvailableWritesRawMetricThresholdView'로 변경되었습니다. ' 응답 속성
  • '#/components/schemas/AssertRegularRawMetricThresholdView, #/components/schemas/AssertWarningRawMetricThresholdView, #/components/schemas/AssertMsgRawMetricThresholdView, #/components/RawMetricThresholdView #/components/schemas/OpCounterUpdateRawMetricThresholdView, #/components/schemas/OpCounterDeleteRawMetricThresholdView, #/components/schemas/OpCounterTtlDeletedRawMetricThresholdView, #/components/schemas/OpCounterInsertRawMetricThresholdView, #/components/schemas/OpCounterGetMoreRawMetricThresholdView, #/components/schemas/OpCounterReplCmdRawMetricThresholdView, #/ components/schemas/OpCounterReplUpdateRawMetricThresholdView, #/components/schemas/OpCounterReplDeleteRawMetricThresholdView, #/components/schemas/OpCounterReplInsertRawMetricThresholdView, #/components/schemas/FtsMemoryResidentDataMetricThres irtualDataMetricThresholdView, #/components/schemas/FtsMemoryMappedDataMetricThresholdView, #/components/schemas/FtsProcessCpuUserRawMetricThresholdView, #/components/schemas/FtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuUserRawMetricThresholdView, #/components/schemas/NormalizedFtsProcessCpuKernelRawMetricThresholdView, #/components/schemas/SystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MemoryResidentDataMetricThresholdView, #/components/schemas/MemoryVirtualDataMetricThresholdView, #/components/schemas/MemoryMappedDataMetricThresholdView, #/components/ThresholdViews/ComputedMemoryDataMetricThresholdView, #/components/schemas/ components/schemas/IndexCountersBtreeMissesRawMetricThresholdView, #/components/schemas/IndexCountersBtreeMissRatioRawMetricThresholdView, #/components/schemas/GlobalLockPercentageRawMetricTh resholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/ConnectionsRawMetricThresholdView, #/components/schemas/ConnectionsMaxRawMetricThresholdView, #/components/RawMetricThresholdView, #/components/RawMetricThresholdView, #/components/ThresholdRawMetricThresholdView. #/components/schemas/GlobalLockCurrentQueueTotalRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueReadersRawMetricThresholdView, #/components/schemas/GlobalLockCurrentQueueWritersRawMetricThresholdView, #/components/schemas/CursorsTotalOpenRawMetricThresholdView, #/components/schemas/CursorsTotalTimedOutRawMetricThresholdView, #/components/schemas/CursorsTotalClientCursorsSizeRawMetricThresholdView, #/ components/schemas/NetworkBytesInDataMetricThresholdView, #/components/schemas/NetworkBytesOutDataMetricThresholdView, #/components/schemas/NetworkNumRequestsRawMetricThresholdView, #/components/ schemas/OplogMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterTimeEstimatedTtlTimeMetricThresholdView, #/components/schemas/OplogSlaveLagMasterTimeTimeMetricThresholdView, #/components/schemas/OplogMasterLagTimeDiffTimeMetricThresholdView, #/components/schemas/OplogRateGbPerHourDataMetricThresholdView, #/components/schemas/ExtraInfoPageFaultsRawMetricThresholdView, #/components/schemas/ DbStorageTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalDataMetricThresholdView, #/components/schemas/DbDataSizeTotalWoSystemDataMetricThresholdView, #/components/schemas/DbIndexSizeTotalDataMetricThresholdView, #/components/schemas/JournalingCommitsInWriteLockRawMetricThresholdView, #/components/schemas/JournalingMbDataMetricThresholdView, #/components/schemas/JournalingWriteDataFilesMbDataMetricThresholdView, #/components/schemas/TicketsAvailableReadsRawMetricThresholdView, #/components/schemas/TicketsAvailableWritesRawMetricThresholdView, #/components/schemas/Cache UsageDirtyDataMetricThresholdView, #/components/schemas/CacheUsageUsedDataMetricThresholdView, #/components/schemas/CacheBytesReadIntoDataMetricThresholdView, #/components/schemas/CacheBytesWrittenFromDataMetricThresholdView, #/components/schemas/NormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/NormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedDataRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedIndexRawMetricThresholdView, #/components/schemas/DiskPartitionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsDataRawMetricThresholdView, #/ components/schemas/DiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/DiskPartitionWriteIopsJournalRawMetricThre sholdView, #/components/schemas/DiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/DiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthDataRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/DiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/FtsDiskUtilizationDataMetricThresholdView, #/components/schemas/MuninCpuUserRawMetricThresholdView, #/components/schemas/MuninCpuNiceRawMetricThresholdView, #/ components/schemas/MuninCpuSystemRawMetricThresholdView, #/components/schemas/MuninCpuIowaitRawMetricThresholdView, #/components/schem as/MuninCpuIrqRawMetricThresholdView, #/components/schemas/MuninCpuSoftirqRawMetricThresholdView, #/components/schemas/MuninCpuStealRawMetricThresholdView, #/components/schemas/DocumentReturnedRawMetricThresholdView, #/components/schemas/DocumentInsertedRawMetricThresholdView, #/components/schemas/DocumentUpdatedRawMetricThresholdView, #/components/schemas/ DocumentDeletedRawMetricThresholdView, #/components/schemas/OperationsScanAndOrderRawMetricThresholdView, #/components/schemas/QueryExecutorScannedRawMetricThresholdView, #/components/schemas/QueryExecutorScannedObjectsRawMetricThresholdView, #/components/schemas/OperationThrottlingRejectedOperationsRawMetricThresholdView, #/components/schemas/QuerySpillToDiskDuringSortRawMetricThresholdView, #/components/schemas/OperationsQueriesKilledRawMetricThresholdView, #/components/schemas/QueryTargetingScannedPerReturnedRawMetricThresholdView, #/components/schemas/QueryTargetingScannedObjectsPerReturnedRawMetricThresholdView, #/components/sch emas/AvgReadExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgWriteExecutionTimeTimeMetricThresholdView, #/components/schemas/AvgCommandExecutionTimeTimeMetricThresholdView, #/components/schemas/LogicalSizeDataMetricThresholdView, #/components/schemas/RestartsInLastHourRawMetricThresholdView, #/components/schemas/SystemMemoryUsedDataMetricThresholdView, #/components/schemas/ SystemMemoryAvailableDataMetricThresholdView, #/components/schemas/SwapUsageUsedDataMetricThresholdView, #/components/schemas/SwapUsageFreeDataMetricThresholdView, #/components/schemas/SystemNetworkInDataMetricThresholdView, #/components/schemas/SystemNetworkOutDataMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuUserRawMetricThresholdView, #/components/schemas/MaxNormalizedSystemCpuStealRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionspaceUsedIndexRawMetricThresholdView, #/components/schemas/MaxDiskPart itionSpaceUsedJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteIopsJournalRawMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionReadLatencyJournalTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyDataTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyIndexTimeMetricThresholdView, #/components/schemas/MaxDiskPartitionWriteLatencyJournalTimeMetricThresholdView, #/ components/schemas/MaxDiskParti tionQueueDepthDataRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthIndexRawMetricThresholdView, #/components/schemas/MaxDiskPartitionQueueDepthJournalRawMetricThresholdView, #/components/schemas/MaxSystemMemoryPercentUsedRawMetricThresholdView, #/components/schemas/MaxSystemMemoryUsedDataMetricThresholdView, #/components/schemas/MaxSystemMemoryAvailableDataMetricThresholdView, #/components/schemas/MaxSwapUsageUsedDataMetricThresholdView, #/components/schemas/MaxSwapUsageFreeDataMetricThresholdView, #/components/schemas/MaxSystemNetworkInDataMetricThresholdView, #/components/schemas/MaxSystemNetworkOutDataMetricThresholdView, #/components/components/searchIndexSizeDataMetricThresholdView, #/component components/schemas/NumberMetricThresholdView, #/components/schemas/SearchOpCounterInsertRawMetricThresholdView, #/components/schemas/SearchOpCou nterDeleteRawMetricThresholdView, #/components/schemas/SearchOpCounterUpdateRawMetricThresholdView, #/components/schemas/SearchOpCounterGetMoreRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesTotalRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesErrorRawMetricThresholdView, #/components/schemas/SearchNumberOfQueriesSuccessRawMetricThresholdView, #/components/schemas/FtsJvmMaxMemoryDataMetricThresholdView, #/components/schemas/FtsJvmCurrentMemoryDataMetricThresholdView'를 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.

2025년 7월 23일 릴리스

  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 'results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesInDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 'results/items/oneOf[subschema #14]/metricThreshold 구성에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterCMDRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 값이 'results/items/oneOf[subschema #14]/metricThres Alert에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterQueryRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold'에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschemaThreshold'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다. 응답13 속성
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값이 'results/items/oneOf[subschema # Configuration]/13: 서버리스 경고에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값이 'results/items/oneOf[subschema #13 구성]/'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 'results/items/oneOf[subschema # Configuration]/13: Serverless Alert 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 'results/items/oneOf[subschema #13 Configuration]/'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #13 Configuration]/'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 'results/items/oneOf[subschema]Stream Processor #16: 임계값 '응답 속성
  • 판별자 키 'STREAM_PROCESSOR_KAFKA_LAG'의 매핑된 값이 'results/items/oneOf[subschema #16]Stream Processor 메트릭 경고 구성에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다: 임계값 '응답 속성
  • 'results/items/oneOf[16 프로세서 메트릭 경고 구성]/임계값' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 'results/items/oneOf[subschema #14: Flex 경고 구성]/metricT 'hreshold' 응답 속성 'oneOf' 응답에 대한 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14' 요청 Flex 경고 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14: metricThreshold Configuration]/ 요청 속성 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 요청 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 속성 이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 속성 이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 구성] ' 요청 속성 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 Configuration] 요청 속성 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경됨: Serverless Alert
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다: 서버리스 경고 구성]/
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값 속성 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값 속성 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성 요청 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 : 서버리스 임계값 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다: 서버리스 경고 구성]/
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성 요청 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성 요청 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경됨: 서버리스 경고 구성]
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 '/oneOf[subschema #16' 구성 요청/스트림 프로세서 임계값 경고에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DLQRawMetricThresholdView'로 변경 요청 . 속성
  • 판별자 키 'STREAM_PROCESSOR_kafka_LAG'의 매핑된 값이 '/oneOf[subschema #16': Stream Processorthreshold Alert Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다. 속성
  • '/oneOf[subschema #16 경고] 스트림에 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'}를 추가했습니다. 구성]/임계값' 요청 속성 'oneOf' 목록
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 요청 ' 속성 ' 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14' 속성 Flex 경고 구성] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14: FlexThreshold' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterCMDRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterQueryRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 구성] 응답 속성 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 Configuration]/metricThreshold 속성 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #13: ServerlessThreshold Configuration ] /에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 '/oneOf[subschema #13' 응답 속성 에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경됨: Serverless Alert Configuration]
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 '/oneOf[subschema #16' 구성] 응답/스트림 프로세서 임계값 경고에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DLQRawMetricThresholdView'로 변경되었습니다. 속성
  • 판별자 키 'STREAM_PROCESSOR_kafka_LAG'의 매핑된 값이 '/oneOf[subschema #16: 스트림 프로세서 임계값 메트릭 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다. 속성
  • '/oneOf[subschema #16 경고] 스트림에 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'}를 추가했습니다. 구성]/임계값' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답에 대한 ponse 속성 'oneOf' 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14' 속성 Flex 경고 구성] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14: FlexThreshold' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterCMDRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterQueryRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 구성] 응답 속성 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 Configuration]/metricThreshold 속성 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #13: ServerlessThreshold Configuration ] /에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 '/oneOf[subschema #13' 응답 속성 에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경됨: Serverless Alert Configuration]
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 '/oneOf[subschema #16' 구성] 응답/스트림 프로세서 임계값 경고에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DLQRawMetricThresholdView'로 변경되었습니다. 속성
  • 판별자 키 'STREAM_PROCESSOR_kafka_LAG'의 매핑된 값이 '/oneOf[subschema #16: 스트림 프로세서 임계값 메트릭 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다. 속성
  • '/oneOf[subschema #16 경고] 스트림에 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'}를 추가했습니다. 구성]/임계값' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답에 대한 ponse 속성 'oneOf' 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14' 속성 Flex 경고 구성] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14: FlexThreshold' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterCMDRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterQueryRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 구성] 응답 속성 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 Configuration]/metricThreshold 속성 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #13: ServerlessThreshold Configuration ] /에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 '/oneOf[subschema #13' 응답 속성 에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경됨: Serverless Alert Configuration]
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 '/oneOf[subschema #16' 구성] 응답/스트림 프로세서 임계값 경고에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DLQRawMetricThresholdView'로 변경되었습니다. 속성
  • 판별자 키 'STREAM_PROCESSOR_kafka_LAG'의 매핑된 값이 '/oneOf[subschema #16: 스트림 프로세서 임계값 메트릭 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다. 속성
  • '/oneOf[subschema #16 경고] 스트림에 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'}를 추가했습니다. 구성]/임계값' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답에 대한 ponse 속성 'oneOf' 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14' 요청 Flex 경고 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14: metricThreshold Configuration]/ 요청 속성 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 요청 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 속성 이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 속성 이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성 요청 .
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 구성] ' 요청 속성 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 Configuration] 요청 속성 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경됨: Serverless Alert
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다: 서버리스 경고 구성]/
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값 속성 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값 속성 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성]/metricThreshold' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성 요청 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 : 서버리스 임계값 구성]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성]/메트릭에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 속성 요청 .
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다: 서버리스 경고 구성]/
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성 요청 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성 요청 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 '/oneOf[subschema #13' 요청 속성 에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경됨: 서버리스 경고 구성]
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 '/oneOf[subschema #16' 구성 요청/스트림 프로세서 임계값 경고에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DLQRawMetricThresholdView'로 변경 요청 . 속성
  • 판별자 키 'STREAM_PROCESSOR_kafka_LAG'의 매핑된 값이 '/oneOf[subschema #16': Stream Processorthreshold Alert Configuration] 요청 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다. 속성
  • '/oneOf[subschema #16 경고] 스트림에 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'}를 추가했습니다. 구성]/임계값' 요청 속성 'oneOf' 목록
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 요청 ' 속성 ' 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 요청 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14' 속성 Flex 경고 구성] 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #14: FlexThreshold' 속성 에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold' 응답 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterCMDRawMetricThresholdView'로 속성 되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 속성 ]/metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThresholdView'에서 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView' 속성 변경되었습니다.
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterQueryRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView'로 변경되었습니다 .
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 구성] 응답 속성 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 '/oneOf[subschema #13 Configuration]/metricThreshold 속성 응답에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대한 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 '/oneOf[subschema #13: ServerlessThreshold Configuration ] /에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 구성] 속성 에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 '/oneOf[subschema #13: 서버리스 경고 속성 ]/에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 '/oneOf[subschema #13: Serverless Alert Configuration ] /metricThres에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 변경되었습니다.
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 '/oneOf[subschema #13' 응답 속성 에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경됨: Serverless Alert Configuration]
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 '/oneOf[subschema #16' 구성] 응답/스트림 프로세서 임계값 경고에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/DLQRawMetricThresholdView'로 변경되었습니다. 속성
  • 판별자 키 'STREAM_PROCESSOR_kafka_LAG'의 매핑된 값이 '/oneOf[subschema #16: 스트림 프로세서 임계값 메트릭 경고 구성]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다. 속성
  • '/oneOf[subschema #16 경고] 스트림에 '#/components/schemas/KafkaRawMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/components/schemas/DLQRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'}를 추가했습니다. 구성]/임계값' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 '/oneOf[subschema #14: Flex 경고 구성]/metricThreshold' 응답에 대한 ponse 속성 'oneOf' 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 '/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.
  • 판별자 키 'FLEX_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_CONNECTIONS_PERCENT'의 매핑된 값이 'results/items/oneOf[subschema #14: Flex Alert Configuration]/metricThreshold'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexConnectionPercentRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_NETWORK_BYTES_IN'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesInDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_NETWORK_BYTES_OUT'의 매핑된 값이 'results/items/oneOf[subschema #14]/metricThreshold 구성에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/FlexNetworkBytesOutDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_NETWORK_NUM_REQUESTS'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexNetworkNumRequestsRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_CMD'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterCMDRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_DELETE'의 매핑된 값이 'results/items/oneOf[subschema #14]/metricThres Alert에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterDeleteRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_INSERT'의 매핑된 값이 'results/items/oneOf[subschema #14]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterInsertRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_QUERY'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterQueryRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'FLEX_OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #14'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/FlexOpCounterUpdateRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_AVG_COMMAND_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold'에 대한 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_AVG_WRITE_EXECUTION_TIME'의 매핑된 값이 'results/items/oneOf[subschemaThreshold'에 대해 '#/components/schemas/TimeMetricThresholdView'에서 '#/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView'로 변경되었습니다. 응답13 속성
  • 판별자 키 'SERVERLESS_CONNECTIONS_PERCENT'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessConnectionPercentageRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_IN'의 매핑된 값이 'results/items/oneOf[subschema # Configuration]/13: 서버리스 경고에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_NETWORK_BYTES_OUT'의 매핑된 값이 'results/items/oneOf[subschema #13 구성]/'에 대해 '#/components/schemas/DataMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_NETWORK_NUM_REQUESTS'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_CMD'의 매핑된 값이 'results/items/oneOf[subschema # Configuration]/13: Serverless Alert 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_DELETE'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_GETMORE'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_INSERT'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_QUERY'의 매핑된 값이 'results/items/oneOf[subschema #13 Configuration]/'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_OPCOUNTER_UPDATE'의 매핑된 값이 'results/items/oneOf[subschema #13 Configuration]/'에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/ServerlessOpCounterUpdateRawMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'SERVERLESS_TOTAL_WRITE_UNITS'의 매핑된 값이 'results/items/oneOf[subschema #13]에 대해 '#/components/schemas/RPUMetricThresholdView'에서 '#/components/schemas/ServerlessTotalWriteUnitsRPUMetricThresholdView'로 변경되었습니다. 응답 속성
  • 판별자 키 'STREAM_PROCESSOR_DLQ_MESSAGE_COUNT'의 매핑된 값이 'results/items/oneOf[subschema]Stream Processor #16: 임계값 '응답 속성
  • 판별자 키 'STREAM_PROCESSOR_KAFKA_LAG'의 매핑된 값이 'results/items/oneOf[subschema #16]Stream Processor 메트릭 경고 구성에 대해 '#/components/schemas/RawMetricThresholdView'에서 '#/components/schemas/KafkaRawMetricThresholdView'로 변경되었습니다: 임계값 '응답 속성
  • 'results/items/oneOf[16 프로세서 메트릭 경고 구성]/임계값' 응답 속성 'oneOf' 응답에 대한 목록입니다.
  • 추가된 '#/components/schemas/RawMetricThresholdView, #/components/schemas/FlexConnectionPercentRawMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/components/schemas/Schemas/FlexNetworkBytesInDataMetricThresholdView, #/components/FThMetricThresholdView #/components/schemas/FlexOpCounterCMDRawMetricThresholdView, #/components/schemas/FlexOpCounterDeleteRawMetricThresholdView, #/components/schemas/FlexOpCounterInsertRawMetricThresholdView, #/components/schemas/FlexOpCounterQueryRawMetricThresholdView, #/components/schemas/FlexOpCounterUpdateRawMetricThresholdView, #/components/schemas/FlexOpCounterGetMoreRawMetricThresholdView, #/ components/schemas/TimeMetricThresholdView, #/components/schemas/FlexAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/FlexAVGCommandExecutionTimeMetricThresholdView'를 'results/items/oneOf[subschema #14: Flex 경고 구성]/metricT 'hreshold' 응답 속성 'oneOf' 응답에 대한 목록
  • 추가된 '#/components/schemas/ServerlessAVGCommandExecutionTimeMetricThresholdView, #/components/schemas/ServerlessAVGWriteExecutionTimeMetricThresholdView, #/components/schemas/TimeMetricThresholdView, #/componentsRupdates/TimeMetricThresholdView, #/components/schemas/ServerlessTotalWriteUnitsRPUMetricThres #/components/schemas/ServerlessOpCounterQueryRawMetricThresholdView, #/components/schemas/ServerlessOpCounterInsertRawMetricThresholdView, #/components/schemas/ServerlessOpCounterGetMoreRawMetricThresholdView, #/components/schemas/ServerlessOpCounterDeleteRawMetricThresholdView, #/components/schemas/ServerlessOpCounterCDMRawMetricThresholdView, #/components/schemas/ServerlessNetworkNumRequestRawMetricThresholdView, #/ components/schemas/ServerlessNetworkBytesOutDataMetricThresholdView, #/components/schemas/ServerlessNetworkBytesInDataMetricThresholdView, #/components/schemas/DataMetricThresholdView, #/compon ents/schemas/ServerlessConnectionPercentageRawMetricThresholdView, #/components/schemas/RawMetricThresholdView'를 'results/items/oneOf[subschema #13: Serverless Alert Configuration]/metricThreshold' 응답 속성 'oneOf' 목록에 추가합니다.

2025년 7월 16일 릴리스

  • 요청 선택적 속성 'withDefaultAlertsSettings'가 쓰기 전용이 아닙니다.
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value' 응답 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다.
  • 새로운 'MONGOT' 열거형 값을 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value' 응답 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다.
  • 새로운 'MONGOT' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다. '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value'
  • 요청 속성 에 새로운 'MONGOT' 열거형 값이 추가되었습니다. '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value'
  • '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value' 응답 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다.
  • 새로운 'MONGOT' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value' 응답 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다.
  • 새로운 'MONGOT' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value' 응답 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다.
  • 새로운 'MONGOT' 열거형 값을 '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다. '/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value'
  • 요청 속성 에 새로운 'MONGOT' 열거형 값이 추가되었습니다. '/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value'
  • 'results/items/oneOf[subschema #8: Host Alert Configuration]/matchers/items/value' 응답 속성 에 새로운 'MONGOT' 열거형 값을 추가했습니다.
  • 새로운 'MONGOT' 열거형 값을 'results/items/oneOf[subschema #9: Host Metric Alert Configuration]/matchers/items/value' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'MONGOTUNE_DISABLED, MONGOTUNE_ENABLED' 열거형 값을 추가했습니다.
  • 선택적 속성 'results/items/oneOf[subschema #4: API User Events]/targetPublicKey, results/items/oneOf[subschema #4: API User Events]/whitelistEntry'를 응답에 추가했습니다.
  • 새로운 'MONGOTUNE_DISABLED, MONGOTUNE_ENABLED' 열거형 값을 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #4: API User Events]/targetPublicKey, /oneOf[subschema #4: API User Events]/whitelistEntry'를 응답에 추가했습니다.
  • 응답에 선택적 속성 'results/items/connections/items/net워킹'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹'을 추가했습니다.
  • 새로운 선택적 요청 속성 'connections/items/net워킹'이 추가되었습니다.
  • 응답에 선택적 속성 'connections/items/net워킹'을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹'을 추가했습니다.
  • 응답에 선택적 속성 'results/items/net워킹'을 추가했습니다.
  • 응답에 선택적 속성 '/net워킹'을 추가했습니다.
  • 새로운 선택적 요청 속성 '/net워킹'이 추가되었습니다.
  • 응답에 선택적 속성 '/net워킹'을 추가했습니다.
  • 응답에 선택적 속성 '/net워킹'을 추가했습니다.
  • 새로운 선택적 요청 속성 '/net워킹'이 추가되었습니다.
  • 응답에 선택적 속성 'connections/items/net워킹'을 추가했습니다.
  • 응답에 선택적 속성 'serviceAccount'를 추가했습니다.
  • 새로운 선택적 요청 속성 'serviceAccount'가 추가되었습니다.
  • 선택적 속성 'results/items/oneOf[subschema #4: API User Events]/targetPublicKey, results/items/oneOf[subschema #4: API User Events]/whitelistEntry'를 응답에 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #4: API User Events]/targetPublicKey, /oneOf[subschema #4: API User Events]/whitelistEntry'를 응답에 추가했습니다.

2025년 7월 02일 릴리스

  • 새로운 'SAOPAULO_BRA, 서울_KOR' 열거형 값을 '/items/dataProcessRegion/ 리전/' 응답 속성 에 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'SAOPAULO_BRA, 서울_KOR' 열거형 값을 추가했습니다.
  • 요청 속성 'dataProcessRegion/ 리전 /'에 새로운 'SAOPAULO_BRA, 서울_KOR' 열거형 값을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'SAOPAULO_BRA, 서울_KOR' 열거형 값을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'SAOPAULO_BRA, 서울_KOR' 열거형 값을 추가했습니다.
  • 요청 속성 'dataProcessRegion/ 리전 /'에 새로운 'SAOPAULO_BRA, 서울_KOR' 열거형 값을 추가했습니다.

2025년 6월 25일 출시

  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값이 추가되었습니다.16
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값이 추가되었습니다.16
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #6: NDS 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #6: NDS 감사 유형]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #6: NDS Audit types]/' 응답 속성 에 추가했습니다.
  • Amazon Web Services 리전 열거형 사양 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: /oneOf[subschema #2: Azure Regions]/' 응답 속성
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf [ subschemaName 복제/사양2: [subschema #2: Azure Regions]/' 응답 속성
  • 'results/items/replicationSpecs/items/regionConfigs / items/oneOf[subschema3 #regionName/Specification]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. [subschema2 #: Azure Regions]/' 응답 속성
  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema4 #regionName/Specification]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. [subschema2 #: Azure Regions]/' 응답 속성
  • 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf2' 속성 Azure Region에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 열거형 Name Region Replication Specifications/one #2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양 #{oneOf]/에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. 2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]에 새로운 'ISRAEL_CENTRAL, itaLY_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. 2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications][subschema # {열거형} : Tenant Regional ReplicationSpecification2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/regionName/oneOf [ subschema #2] 응답 속성 에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf [Amazon Web Services}/ SpecificationOf[subschema #1/ReplicationNameones]]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. [하위 스키마 #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2]/subregionName 복제 사양 Azure 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. #2: Azure 리전]/'
  • 요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3] /subregion ReplicationName #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4]/subregion 복제 이름에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf [ subschema #2]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 'providerSettings/oneOf[subschema #2: Cloud Service Provider Settings for a Cluster]/regionName' 응답 속성 에 새로운 'ISRAEL_CENTRAL, itaLY_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 요청 속성 'providerSettings/oneOf[subschema #2: Cloud Service Provider Settings for a Cluster]/regionName'에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 열거형 Name Region Replication Specifications/one #2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양 #{oneOf]/에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. 2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]에 새로운 'ISRAEL_CENTRAL, itaLY_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. 2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications][subschema # {열거형} : Tenant Regional ReplicationSpecification2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/regionName/oneOf [ subschema #2] 응답 속성 에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 열거형 Name Region Replication Specifications/one #2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양 #{oneOf]/에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. 2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP Regional Replication Specifications]에 새로운 'ISRAEL_CENTRAL, itaLY_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. 2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: Tenant Regional Replication Specifications][subschema # {열거형} : Tenant Regional ReplicationSpecification2: Azure 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/regionName/oneOf [ subschema #2] 응답 속성 에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf [Amazon Web Services}/ SpecificationOf[subschema #1/ReplicationNameones]]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. [하위 스키마 #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2]/subregionName 복제 사양 Azure 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. #2: Azure 리전]/'
  • 요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3] /subregion ReplicationName #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4]/subregion 복제 이름에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf [ subschema #2]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 응답에 선택적 속성 'googleCloudKms/roleId'를 추가했습니다.
  • 응답에 선택적 속성 'googleCloudKms/roleId'를 추가했습니다.
  • 새로운 선택적 요청 속성 'googleCloudKms/roleId' 추가
  • 'results/items/oneOf[subschema1 #: Azure Key Vault #Of1 ] [}subregionName/Of1 : Azure1 리전]/' 응답 속성
  • 'results/items/oneOf[subschema #: Amazon Web Services KMS EAR 비공개 엔드포인트]/subregionName/oneOf1에 새로운 'ISRAEL_CENTRAL, ITALY_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.21 }: Azure 리전]/' 응답 속성
  • 'results/items/regionName/oneOf[subschema #1: Azure Regions]/' 응답 속성 에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • '/oneOf[subschema1 #: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[sub1 Azure Regions]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. ]/' 응답 속성
  • '/ Azure [subschema #: Amazon Web Services KMS EAR 비공개 열거형 포인트]/regionName/oneOf[subschema #21 Regions]/' 응답 속성
  • 'regionName/oneOf[subschema #1: Azure Regions]/' 응답 속성 에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[subschema]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. Azure11 리전]/'
  • 요청 속성 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/regionName/oneOf[subschema #1: Azure 리전]/'
  • 요청 속성 'regionName/oneOf[subschema #1: Azure Regions]/'에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • '/oneOf[subschema1 #: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[sub1 Azure Regions]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. ]/' 응답 속성
  • '/ Azure [subschema #: Amazon Web Services KMS EAR 비공개 열거형 포인트]/regionName/oneOf[subschema #21 Regions]/' 응답 속성
  • 'regionName/oneOf[subschema #1: Azure Regions]/' 응답 속성 에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE, PROXY_PROTOCOL_FOR_PRIVATE_LINK_mode_UPDATED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_BLOCK_WRITE, CLUSTER_UNBLOCK_WRITE, PROXY_PROTOCOL_FOR_PRIVATE_LINK_mode_UPDATED' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf [Amazon Web Services}/ SpecificationOf[subschema #1/ReplicationNameones]]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. [하위 스키마 #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2]/subregionName 복제 사양 Azure 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. #2: Azure 리전]/'
  • 요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3] /subregion ReplicationName #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4]/subregion 복제 이름에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다. #2: Azure 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf [ subschema #2]에 새로운 'ISRAEL_CENTRAL, italy_NORTH, MEXICO_CENTRAL, NEW_ZEALAND_NORTH, POLAND_CENTRAL, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.
  • 'results/items/connections/items/' 응답 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 'connections/items/' 요청 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 'connections/items/' 요청 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 요청 속성 'connections/items/type'에 새로운 'AWSKinesisDataStreams' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 'results/items/' 응답 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 요청 판별자에 'AWSKinesisDataStreams' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AWSKinesisDataStreams' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 요청 속성 '/type'에 새로운 'AWSKinesisDataStreams' 열거형 값을 추가했습니다.
  • 요청 속성 'type'에 새로운 'AWSKinesisDataStreams' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AWSKinesisDataStreams' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 요청 판별자에 'AWSKinesisDataStreams' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AWSKinesisDataStreams' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 요청 속성 '/type'에 새로운 'AWSKinesisDataStreams' 열거형 값을 추가했습니다.
  • 요청 속성 'type'에 새로운 'AWSKinesisDataStreams' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSKinesisDataStreams' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSKinesisDataStreamsConnection'을 추가했습니다.
  • 엔드포인트 추가됨
  • 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'CUSTOM_SESSION_TIMEOUT_MODIFIED, SANDBox_DISABLED_FOR_ORG, SANDBox_ENABLED_FOR_ORG' 열거형 값을 추가했습니다.
  • Added the new 'VERCEL_INVOICE_CREATED, VERCEL_INVOICE_NOT_PAID, VERCEL_INVOICE_PAID, VERCEL_INVOICE_REFUNDED, VERCEL_SELF_SERVE_ACCOUNT_CANCELLED, VERCEL_SELF_SERVE_ACCOUNT_LINKED, VERCEL_SELF_SERVE_ACCOUNT_LINK_FAILED, VERCEL_SELF_SERVE_ACCOUNT_LINK_PENDING' 열거형 values to the 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: 파트너 이벤트 유형]/' 응답 속성
  • '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'CUSTOM_SESSION_TIMEOUT_MODIFIED, SANDBox_DISABLED_FOR_ORG, SANDBox_ENABLED_FOR_ORG' 열거형 값을 추가했습니다.
  • Added the new 'VERCEL_INVOICE_CREATED, VERCEL_INVOICE_NOT_PAID, VERCEL_INVOICE_PAID, VERCEL_INVOICE_REFUNDED, VERCEL_SELF_SERVE_ACCOUNT_CANCELLED, VERCEL_SELF_SERVE_ACCOUNT_LINKED, VERCEL_SELF_SERVE_ACCOUNT_LINK_FAILED, VERCEL_SELF_SERVE_ACCOUNT_LINK_PENDING' 열거형 values to the '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #4: Partner 이벤트 유형]/' 응답 속성
  • Added the new 'ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP10, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP30, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP50, ATLAS_GCP_STREAM_PROCESSING_PRIVATELINK' 열거형 values to the 'results/items/lineItems/items/sku' response 속성
  • 새로운 'ATLAS_GCP_STREAM_PROCESSING_DATA_TRANSFER, ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP,10 ATLAS_GCP_STREAM_PROCESSING_INSTACE_SP,30 ATLAS_GCP_STREAM_PROCESSING_INSTANCE_SP50 {속성} , ATLAS_GCP_STREAM_PROCESSING_INSTACE_SP, ATLAS_GCP_STREAM_PROCESSING_INSTACE_SP 열거형 추가되었습니다.
  • 상태가 '429 '인 실패 응답을 추가했습니다.

2025년 6월 18일 출시

  • 응답에 선택적 속성 'streamsCrossGroupEnabled'를 추가했습니다.
  • 응답에 선택적 속성 'streamsCrossGroupEnabled'를 추가했습니다.
  • 새로운 선택적 요청 속성 'streamsCrossGroupEnabled'가 추가되었습니다.

2025년 6월 17일 출시

  • 응답에 선택적 속성 'results/items/connections/items/clusterGroupId'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/clusterGroupId'를 추가했습니다.
  • 새로운 선택적 요청 속성 'connections/items/clusterGroupId' 추가
  • 응답에 선택적 속성 'connections/items/clusterGroupId'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/clusterGroupId'를 추가했습니다.
  • 응답에 선택적 속성 'results/items/clusterGroupId'를 추가했습니다.
  • 응답에 선택적 속성 '/clusterGroupId'를 추가했습니다.
  • 새로운 선택적 요청 속성 '/clusterGroupId'가 추가되었습니다.
  • 응답에 선택적 속성 '/clusterGroupId'를 추가했습니다.
  • 응답에 선택적 속성 '/clusterGroupId'를 추가했습니다.
  • 새로운 선택적 요청 속성 '/clusterGroupId'가 추가되었습니다.
  • 응답에 선택적 속성 'connections/items/clusterGroupId'를 추가했습니다.

2025년 6월 04일 출시

  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'ENCRYPTION_AT_REST_CONFIGURATION_VALIDATION_SUCCEEDED, step_SKIPPED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'ENCRYPTION_AT_REST_CONFIGURATION_VALIDATION_SUCCEEDED, STEP_SKIPPED' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'results/items/connections/items/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 새로운 선택적 요청 속성 'connections/items/net워킹/ 액세스/tgwRouteId'가 추가되었습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 응답에 선택적 속성 'results/items/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 응답에 선택적 속성 '/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 새로운 선택적 요청 속성 '/net워킹/ 액세스/tgwRouteId'가 추가되었습니다.
  • 응답에 선택적 속성 '/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 응답에 선택적 속성 '/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 새로운 선택적 요청 속성 '/net워킹/ 액세스/tgwRouteId'가 추가되었습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwRouteId'를 추가했습니다.
  • 'results/items/lineItems/items/sku' 응답 속성 에 새로운 'ATLAS_NDS_GCP_SNAPSHOT_EXPORT_UPLOAD' 열거형 값을 추가했습니다.
  • 'lineItems/items/sku' 응답 속성 에 새로운 'ATLAS_NDS_GCP_SNAPSHOT_EXPORT_UPLOAD' 열거형 값을 추가했습니다.

20 5월 2025 출시

  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/ClusterAlertViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/ClusterAlertView' 제거되었습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/ClusterAlertViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/ClusterAlertView' 제거되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/ClusterAlertViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/ClusterAlertView' 제거되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/ClusterAlertViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/ClusterAlertView' 제거되었습니다.

08 5월 2025 출시

  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 엔드포인트에 Atlas 내부 항목이 포함되는 문제를 수정합니다.
  • 선택적 속성 'results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, results/items/oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, results/items/oneOf[subschema #12: 복제본 임계값 경고 구성 설정]/severityOverride, results/items/oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, results/items/oneOf[subschema #14: Flex 경고 구성]/severityOverride, results/items/oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, 결과/items/oneOf[하위 스키마 #16: 스트림 프로세서 메트릭 경고 구성]/severityOverride, results/items/oneOf[subschema #1: Any Other Alert Configurations]/severityOverride, results/items/oneOf[subschema #2: App Services Alert Configuration]/severityOverride, results/items/oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, results/items/oneOf[subschema #5: 클러스터 경고 구성]/severityOverride, results/items/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/severityOverride, results/items/ oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, results/items/oneOf[subschema #8: 호스트 경고 구성]/severityOverride, results/items/oneOf[subschema #9: 호스트 지표 경고 Configuration]/severityOverride'를 응답에 추가합니다.
  • 선택적 속성 '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, /oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, /oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/severityOverride, /oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, /oneOf[subschema #14: Flex 경고 구성]/severityOverride, /oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, /oneOf[subschema #16: 스트림 프로세서 지표 경고 구성]/severityOverride, /oneOf[subschema #1: 모든 기타 경고 구성]/severityOverride, /oneOf[subschema #2: App Services 경고 구성]/severityOverride, /oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, /oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, /oneOf [subschema #5: Cluster Alert Configuration]/severityOverride, /oneOf[subschema #6: Cps Back 최대 임계값 경고 구성]/severityOverride, /oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, /oneOf[subschema #8: 호스트 경고 구성]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride'를 응답에 추가합니다.
  • 새로운 선택적 요청 속성 '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, /oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, /oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/severityOverride, /oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, /oneOf[subschema #14: Flex 경고 구성]/severityOverride, /oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, /oneOf[subschema #16: 스트림 프로세서 지표 경고 구성]/severityOverride, /oneOf[subschema #1: 모든 기타 경고 구성]/severityOverride, /oneOf[subschema #2: App Services 경고 구성]/severityOverride, /oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, /oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, /oneOf[subschema #5: 클러스터 경고 구성]/severityOverride, /oneOf[subschema #6: Cps 백업 임계값 경고 구성]/severityOverride, /oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, /oneOf[subschema #8: 호스트 경고 구성]/severityOverride, /oneOf[subschema #9: 호스트 지표 경고 구성]/severityOverride'
  • 선택적 속성 '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, /oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, /oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/severityOverride, /oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, /oneOf[subschema #14: Flex 경고 구성]/severityOverride, /oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, /oneOf[subschema #16: 스트림 프로세서 지표 경고 구성]/severityOverride, /oneOf[subschema #1: 모든 기타 경고 구성]/severityOverride, /oneOf[subschema #2: App Services 경고 구성]/severityOverride, /oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, /oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, /oneOf [subschema #5: Cluster Alert Configuration]/severityOverride, /oneOf[subschema #6: Cps Back 최대 임계값 경고 구성]/severityOverride, /oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, /oneOf[subschema #8: 호스트 경고 구성]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride'를 응답에 추가합니다.
  • 선택적 속성 '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, /oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, /oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/severityOverride, /oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, /oneOf[subschema #14: Flex 경고 구성]/severityOverride, /oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, /oneOf[subschema #16: 스트림 프로세서 지표 경고 구성]/severityOverride, /oneOf[subschema #1: 모든 기타 경고 구성]/severityOverride, /oneOf[subschema #2: App Services 경고 구성]/severityOverride, /oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, /oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, /oneOf [subschema #5: Cluster Alert Configuration]/severityOverride, /oneOf[subschema #6: Cps Back 최대 임계값 경고 구성]/severityOverride, /oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, /oneOf[subschema #8: 호스트 경고 구성]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride'를 응답에 추가합니다.
  • 선택적 속성 '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, /oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, /oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/severityOverride, /oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, /oneOf[subschema #14: Flex 경고 구성]/severityOverride, /oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, /oneOf[subschema #16: 스트림 프로세서 지표 경고 구성]/severityOverride, /oneOf[subschema #1: 모든 기타 경고 구성]/severityOverride, /oneOf[subschema #2: App Services 경고 구성]/severityOverride, /oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, /oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, /oneOf [subschema #5: Cluster Alert Configuration]/severityOverride, /oneOf[subschema #6: Cps Back 최대 임계값 경고 구성]/severityOverride, /oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, /oneOf[subschema #8: 호스트 경고 구성]/severityOverride, /oneOf[subschema #9: Host Metric Alert Configuration]/severityOverride'를 응답에 추가합니다.
  • 새로운 선택적 요청 속성 '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, /oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, /oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/severityOverride, /oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, /oneOf[subschema #14: Flex 경고 구성]/severityOverride, /oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, /oneOf[subschema #16: 스트림 프로세서 지표 경고 구성]/severityOverride, /oneOf[subschema #1: 모든 기타 경고 구성]/severityOverride, /oneOf[subschema #2: App Services 경고 구성]/severityOverride, /oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, /oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, /oneOf[subschema #5: 클러스터 경고 구성]/severityOverride, /oneOf[subschema #6: Cps 백업 임계값 경고 구성]/severityOverride, /oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, /oneOf[subschema #8: 호스트 경고 구성]/severityOverride, /oneOf[subschema #9: 호스트 지표 경고 구성]/severityOverride'
  • 선택적 속성 'results/items/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/severityOverride, results/items/oneOf[subschema #11: Replica Set Alert Configuration]/severityOverride, results/items/oneOf[subschema #12: 복제본 임계값 경고 구성 설정]/severityOverride, results/items/oneOf[subschema #13: 서버리스 경고 구성]/severityOverride, results/items/oneOf[subschema #14: Flex 경고 구성]/severityOverride, results/items/oneOf[subschema #15: 스트림 프로세서 경고 구성]/severityOverride, 결과/items/oneOf[하위 스키마 #16: 스트림 프로세서 메트릭 경고 구성]/severityOverride, results/items/oneOf[subschema #1: Any Other Alert Configurations]/severityOverride, results/items/oneOf[subschema #2: App Services Alert Configuration]/severityOverride, results/items/oneOf[subschema #3: App Services 지표 경고 구성]/severityOverride, results/items/oneOf[subschema #4: 청구 임계값 경고 구성]/severityOverride, results/items/oneOf[subschema #5: 클러스터 경고 구성]/severityOverride, results/items/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/severityOverride, results/items/ oneOf[subschema #7: 암호화 키 경고 구성]/severityOverride, results/items/oneOf[subschema #8: 호스트 경고 구성]/severityOverride, results/items/oneOf[subschema #9: 호스트 지표 경고 Configuration]/severityOverride'를 응답에 추가합니다.
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'includeMetrics' 추가
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'includeOpType' 추가
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'includeReplicaState' 추가
  • 선택적 속성 'slowQueries/items/ 지표, slowQueries/items/opType, slowQueries/items/replicaState'를 응답에 추가했습니다.
  • Added the new 'ATLAS_FLEX_AWS_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_500_USAGE_HOURS' 열거형 values to the 'results /items/lineItems/items/sku '응답 속성
  • Added the new 'ATLAS_FLEX_AWS_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AWS_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_AZURE_LEGACY_500_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_100_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_200_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_300_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_400_USAGE_HOURS, ATLAS_FLEX_GCP_LEGACY_500_USAGE_HOURS' enum values to the 'lineItems/items/sku' response property

2025년 4월 23일 출시

  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 'results/items/' 응답 속성 에 ' GCP ' 판별자 매핑 키를 추가했습니다.
  • 'results/items/cloudProvider' 응답 속성 에 새로운 ' GCP' 열거형 값을 추가했습니다.
  • 요청 판별자에 ' GCP ' 매핑 키를 추가했습니다.
  • 응답 상태 '200 '에 대한 응답 판별자에 ' GCP' 매핑 키를 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 'cloudProvider' 응답 속성 에 새로운 ' GCP' 열거형 값을 추가했습니다.
  • 요청 속성 'cloudProvider'에 새로운 ' GCP' 열거형 값을 추가했습니다.
  • 응답 상태 '200 '에 대한 응답 판별자에 ' GCP' 매핑 키를 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 'cloudProvider' 응답 속성 에 새로운 ' GCP' 열거형 값을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • '/items/actions/items/ 조치' 응답 속성 에 새로운 'CLEAR_JUMBO_FLAG, KILL_ANY_CURSOR, REFINE_COLLECTION_SHARD_KEY, RESHARD_COLLECTION, SHARDED_DATA_DISTRIBUTION' 열거형 값을 추가했습니다.
  • 'actions/items/ 조치' 응답 속성 에 새로운 'CLEAR_JUMBO_FLAG, KILL_ANY_CURSOR, REFINE_COLLECTION_SHARD_KEY, RESHARD_COLLECTION, SHARDED_DATA_DISTRIBUTION' 열거형 값이 추가되었습니다.
  • 요청 속성 'actions/items/ 조치 '에 새로운 'CLEAR_JUMBO_FLAG, KILL_ANY_CURSOR, REFINE_COLLECTION_SHARD_KEY, RESHARD_COLLECTION, SHARDED_DATA_DISTRIBUTION' 열거형 값을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 'actions/items/ 조치' 응답 속성 에 새로운 'CLEAR_JUMBO_FLAG, KILL_ANY_CURSOR, REFINE_COLLECTION_SHARD_KEY, RESHARD_COLLECTION, SHARDED_DATA_DISTRIBUTION' 열거형 값이 추가되었습니다.
  • 'actions/items/ 조치' 응답 속성 에 새로운 'CLEAR_JUMBO_FLAG, KILL_ANY_CURSOR, REFINE_COLLECTION_SHARD_KEY, RESHARD_COLLECTION, SHARDED_DATA_DISTRIBUTION' 열거형 값이 추가되었습니다.
  • 요청 속성 'actions/items/ 조치 '에 새로운 'CLEAR_JUMBO_FLAG, KILL_ANY_CURSOR, REFINE_COLLECTION_SHARD_KEY, RESHARD_COLLECTION, SHARDED_DATA_DISTRIBUTION' 열거형 값을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • Added the new 'AUTO_HEALING_CANNOT_REPAIR_INTERNAL, AUTO_HEALING_CANNOT_RESYNC_INTERNAL, AUTO_HEALING_REQUESTED_CRITICAL_INSTANCE_POWER_CYCLE, AUTO_HEALING_REQUESTED_INSTANCE_REPLACEMENT, AUTO_HEALING_REQUESTED_NODE_RESYNC, FTDC_SETTINGS_UPDATED' 열거형 values to the 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' response 속성
  • 상태가 '403'인 실패 응답 추가
  • Added the new 'AUTO_HEALING_CANNOT_REPAIR_INTERNAL, AUTO_HEALING_CANNOT_RESYNC_INTERNAL, AUTO_HEALING_REQUESTED_CRITICAL_INSTANCE_POWER_CYCLE, AUTO_HEALING_REQUESTED_INSTANCE_REPLACEMENT, AUTO_HEALING_REQUESTED_NODE_RESYNC, FTDC_SETTINGS_UPDATED' 열거형 values to the '/oneOf[subschema #15: NDS Audits]/eventTypeName' response 속성
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 제거된 'dataFederation.bytesProcessed. 쿼리, dataFederation.bytesProcessed.weekly, dataFederation.bytesProcessed.daily, dataFederation.bytesProcessed.monthly' '/items/' 응답 속성 의 판별자 매핑 키
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 제거된 'dataFederation.bytesProcessed.monthly, dataFederation.bytesProcessed. 쿼리, dataFederation.bytesProcessed.weekly, dataFederation.bytesProcessed.daily' 응답 상태 '200'에 대한 응답 판별자의 매핑 키
  • 상태가 '403'인 실패 응답 추가
  • 제거된 'dataFederation.bytesProcessed.weekly, dataFederation.bytesProcessed.daily, dataFederation.bytesProcessed.monthly, dataFederation.bytesProcessed. 쿼리' 요청 판별자의 매핑 키
  • 제거된 'dataFederation.bytesProcessed. 쿼리, dataFederation.bytesProcessed.weekly, dataFederation.bytesProcessed.daily, dataFederation.bytesProcessed.monthly' 응답 상태 '200'에 대한 응답 판별자의 매핑 키
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 'results/items/connections/items/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 선택적 속성 'results/items/connections/items/net워킹/ 액세스/tgwId, 결과/items/연결/항목/네트워킹/ 액세스/vpcCIDR'을 응답에 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 'connections/items/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 요청 속성 'connections/items/net워킹/ 액세스 /유형'에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwId, 연결/항목/네트워킹/ 액세스/vpcCIDR'을 추가했습니다.
  • 새로운 선택적 요청 속성 'connections/items/net워킹/ 액세스/tgwId, connections/items/net워킹/ 액세스/vpcCIDR'이 추가되었습니다.
  • 응답 상태 '200'에 대한 응답 판별자 추가
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/AWSAccountDetails, #/components/schemas/AzureAccountDetails'를 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 'results/items/arn' 응답의 속성 패턴 '^arn:aws:kafka'가 추가되었습니다.
  • 응답에 선택적 속성 'results/items/azureResourceIds'를 추가했습니다.
  • 응답 속성 'results/items/ 제공자'가 필수 항목이 되었습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 'arn' 응답의 속성 패턴 '^arn:aws:kafka'가 추가되었습니다.
  • 응답에 선택적 속성 'azureResourceIds'를 추가했습니다.
  • 응답 속성 ' 제공자'이(가) 필수 항목이 되었습니다.
  • 새로운 선택적 요청 속성 'azureResourceIds'가 추가되었습니다.
  • 상태가 '403'인 실패 응답 추가
  • 'arn' 응답의 속성 패턴 '^arn:aws:kafka'가 추가되었습니다.
  • 응답에 선택적 속성 'azureResourceIds'를 추가했습니다.
  • 응답 속성 ' 제공자'이(가) 필수 항목이 되었습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 'connections/items/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwId, 연결/항목/네트워킹/ 액세스/vpcCIDR'을 추가했습니다.
  • 'connections/items/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwId, 연결/항목/네트워킹/ 액세스/vpcCIDR'을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 'results/items/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 선택적 속성 'results/items/net워킹/ 액세스/tgwId, results/items/net워킹/ 액세스/vpcCIDR'을 응답에 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • '/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 요청 속성 '/net워킹/ 액세스 /유형'에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 선택적 속성 '/net워킹/ 액세스/tgwId, /네트워킹/ 액세스/vpcCIDR'을 응답에 추가했습니다.
  • 새로운 선택적 요청 속성 '/net워킹/ 액세스/tgwId, /네트워킹/ 액세스/vpcCIDR'이 추가되었습니다.
  • 상태가 '403'인 실패 응답 추가
  • '/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 선택적 속성 '/net워킹/ 액세스/tgwId, /네트워킹/ 액세스/vpcCIDR'을 응답에 추가했습니다.
  • '/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 요청 속성 '/net워킹/ 액세스 /유형'에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 선택적 속성 '/net워킹/ 액세스/tgwId, /네트워킹/ 액세스/vpcCIDR'을 응답에 추가했습니다.
  • 새로운 선택적 요청 속성 '/net워킹/ 액세스/tgwId, /네트워킹/ 액세스/vpcCIDR'이 추가되었습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 'connections/items/net워킹/ 액세스/유형' 응답 속성 에 새로운 'TRANSIT_GATEWAY' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/net워킹/ 액세스/tgwId, 연결/항목/네트워킹/ 액세스/vpcCIDR'을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '401 '인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가
  • 상태가 '403'인 실패 응답 추가

2025년 4월 02일 출시

  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #10: 리소스 이벤트 유형]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 요청 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값이 추가되었습니다.110
  • 응답에 대한 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 요청 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • 응답에 대한 '/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #10: Resource Event Types]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값이 추가되었습니다.110
  • 응답에 대한 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #17: Atlas 리소스 정책 감사 유형'을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #13: 리소스 이벤트 유형]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #17: Atlas 리소스 정책 감사 유형'을 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #13: 리소스 이벤트 유형]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #17: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #13: 리소스 이벤트 유형]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #7: Any 기타 경고]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #17: Atlas 리소스 정책 감사 유형'이 추가되었습니다.
  • '/oneOf[subschema #7: Any 기타 경고]/eventTypeName/oneOf[subschema #13: 리소스 이벤트 유형]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName' 응답 속성 'oneOf' 목록에 'subschema #13: Atlas 리소스 정책 감사 유형'을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any 기타 경고 구성]/eventTypeName/oneOf[subschema #10: 리소스 이벤트 유형]/' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에서 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse'가 제거되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse'가 제거되었습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에서 '#/components/schemas/DiskBackupSnapshotAWSExportBucketResponse, #/components/schemas/DiskBackupSnapshotAzureExportBucketResponse'가 제거되었습니다.
  • 응답에 선택적 속성 'encryptionAtRestProvider'를 추가했습니다.
  • 응답에 선택적 속성 'encryptionAtRestProvider'를 추가했습니다.
  • 응답에 선택적 속성 'encryptionAtRestProvider'를 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • '/items/actions/items/ 조치' 응답 속성 에 새로운 'ANALYZE_SHARD_KEY, MOVE_CHUNK, SPLIT_CHUNK' 열거형 값을 추가했습니다.
  • 'actions/items/ 조치' 응답 속성 에 새로운 'ANALYZE_SHARD_KEY, MOVE_CHUNK, SPLIT_CHUNK' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/ 조치 '에 새로운 'ANALYZE_SHARD_KEY, MOVE_CHUNK, SPLIT_CHUNK' 열거형 값을 추가했습니다.
  • 'actions/items/ 조치' 응답 속성 에 새로운 'ANALYZE_SHARD_KEY, MOVE_CHUNK, SPLIT_CHUNK' 열거형 값을 추가했습니다.
  • 'actions/items/ 조치' 응답 속성 에 새로운 'ANALYZE_SHARD_KEY, MOVE_CHUNK, SPLIT_CHUNK' 열거형 값을 추가했습니다.
  • 요청 속성 'actions/items/ 조치 '에 새로운 'ANALYZE_SHARD_KEY, MOVE_CHUNK, SPLIT_CHUNK' 열거형 값을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 응답에 선택적 속성 'enabledForSearchNodes'를 추가했습니다.
  • 응답에 선택적 속성 'enabledForSearchNodes'를 추가했습니다.
  • 새로운 선택적 요청 속성 'enabledForSearchNodes' 추가
  • 'results/items/' 응답 속성에 판별자 추가
  • 요청 판별자 추가
  • 응답 상태 '202'에 대한 응답 판별자가 추가되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/AtlasResourcePolicyAuditForNdsGroup'을 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'AZ_BALACING_OVERRIDE_MODIFIED' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #23: Resource Events]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/AtlasResourcePolicyAuditForNdsGroup'을 추가했습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 새로운 'AZ_BALACING_OVERRIDE_MODIFIED' 열거형 값을 '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #23: Resource Events]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 응답에 대한 '/items/source' 응답 속성 'oneOf' 목록에서 '#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource'를 제거했습니다.
  • 응답에 대한 '소스' 응답 속성 'oneOf' 목록에서 '#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource'를 제거했습니다.
  • 상태가 '200 '인 성공 응답을 추가했습니다.
  • 응답에 대한 '소스' 응답 속성 'oneOf' 목록에서 '#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource'를 제거했습니다.
  • 응답에 대한 '소스' 응답 속성 'oneOf' 목록에서 '#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource'를 제거했습니다.
  • 응답에 대한 '소스' 응답 속성 'oneOf' 목록에서 '#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource'를 제거했습니다.
  • 응답에 대한 '소스' 응답 속성 'oneOf' 목록에서 '#/components/schemas/OnDemandCpsSnapshotSource, #/components/schemas/PeriodicCpsSnapshotSource'를 제거했습니다.
  • 응답에 선택적 쓰기 전용 속성 'results/items/connections/items/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'results/items/connections/items/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 'results/items/connections/items/ 인증/sslCertificate'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/sslCertificate'을 추가했습니다.
  • 새로운 선택적 요청 속성 'connections/items/ 인증/sslCertificate, connections/items/ 인증/sslKey, connections/items/ 인증/sslKeyPassword'
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/sslCertificate'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/sslCertificate'을 추가했습니다.
  • 선택적 쓰기 전용 속성 'results/items/ 인증/sslKey'를 응답에 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'results/items/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 'results/items/ 인증/sslCertificate'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 '/ 인증/sslCertificate'을 추가했습니다.
  • 새로운 선택적 요청 속성 '/ 인증/sslCertificate, / 인증/sslKey, / 인증/sslKeyPassword'
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 '/ 인증/sslCertificate'을 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 '/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 '/ 인증/sslCertificate'을 추가했습니다.
  • 새로운 선택적 요청 속성 '/ 인증/sslCertificate, / 인증/sslKey, / 인증/sslKeyPassword'
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKey'를 추가했습니다.
  • 응답에 선택적 쓰기 전용 속성 'connections/items/ 인증/sslKeyPassword'를 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ 인증/sslCertificate'을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 상태가 '404'인 실패 응답을 추가했습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 새로운 'RESOURCE_POLICY_VIOLATED' 열거형 값을 'results/items/oneOf[subschema #12: Atlas Resource Policy Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #11: Resource Events]/eventTypeName' 응답 속성 에 새로운 'TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 'isGlobalAdmin' 응답의 속성 기본값 'false'가 제거되었습니다.
  • 새로운 'RESOURCE_POLICY_VIOLATED' 열거형 값을 '/oneOf[subschema #12: Atlas Resource Policy Audits]/eventTypeName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #11: Resource Events]/eventTypeName' 응답 속성 에 새로운 'TAGS_MODIFIED' 열거형 값을 추가했습니다.
  • API 종료 날짜가 삭제되었지만 deprecated=true 유지

2025년 3월 12일 출시

  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 '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]/' 응답 속성 에 추가했습니다.
  • 'results[/items/onetsubschedule]에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.1 12' 응답 속성
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 '/oneOf[subschema #5: 클러스터 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema] 응답에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE'112 속성 열거형 속성을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName'에 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_Longer_VALID' 열거형 값이 추가되었습니다.15
  • 요청 속성 에 새로운 'OUTSIDE_STREAM_PROCESSOR_METRIC_THRESHOLD' 열거형 값이 추가되었습니다.111
  • 요청1 속성 에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.12
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 '/oneOf[subschema #5: 클러스터 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema] 응답에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE'112 속성 열거형 속성을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 '/oneOf[subschema #5: 클러스터 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema] 응답에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE'112 속성 열거형 속성을 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 '/oneOf[subschema #5: 클러스터 경고 구성]/eventTypeName' 응답 속성 에 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema] 응답에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE'112 속성 열거형 속성을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #5: Cluster Alert Configuration]/eventTypeName'에 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_Longer_VALID' 열거형 값이 추가되었습니다.15
  • 요청 속성 에 새로운 'OUTSIDE_STREAM_PROCESSOR_METRIC_THRESHOLD' 열거형 값이 추가되었습니다.111
  • 요청1 속성 에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.12
  • 'results/items/oneOf[subschema #2: Cluster Alerts]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 'results[/items/oneNameOf}에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.715 응답 속성
  • 'results/items/oneOf[subschema #2: Cluster Alerts]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_NO_LONGER_VALID' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #5: Group Event Types]/' 응답 속성 에 추가했습니다.
  • 'results[/items/oneNameOf}에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.715 응답 속성
  • 새로운 '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]/' 응답 속성 에 추가했습니다.
  • '/oneOf][subschema #Types] 감사 응답에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE'7 열거형 속성 을 추가했습니다.15
  • 새로운 '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]/' 응답 속성 에 추가했습니다.
  • '/oneOf][subschema #Types] 감사 응답에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE'7 열거형 속성 을 추가했습니다.15
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamProcessorMetricAlertConfigViewForNdsGroup'을 추가했습니다.
  • 새로운 '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]/' 응답 속성 에 추가했습니다.
  • 'results[/items/onetsubschedule]에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.1 12' 응답 속성
  • 선택적 속성 'results/items/advancedConfiguration, results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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, 결과/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/predictiveEnabled, 결과/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'를 응답에 추가합니다.
  • 선택적 속성 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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'를 응답에 추가합니다. se
  • 새로운 선택적 요청 속성 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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'
  • 응답에 선택적 속성 'advancedConfiguration, autoScaling/compute/predictiveEnabled'를 추가했습니다.
  • 새로운 선택적 요청 속성 'advancedConfiguration, autoScaling/compute/predictiveEnabled'가 추가되었습니다.
  • 선택적 속성 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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'를 응답에 추가합니다. se
  • 선택적 속성 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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'를 응답에 추가합니다. se
  • 새로운 선택적 요청 속성 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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'
  • 노드가 존재하지 않는 경우 API 반환을 업데이트하고, 엔드포인트는 400 대신 빈 JSON ({})을 사용하여 200 을 반환합니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/ChartsAudit' 추가
  • 'results/items/oneOf[subschema #9: Cluster Events]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 추가했습니다.
  • 새로운 'ENCRYPTION_AT_REST_CONFIG_IS_VALID, ENCRYPTION_AT_REST_CONFIG_NO_Longer_VALID' 열거형 값을 'results/items/oneOf[subschema1 #: Any Other Events]/eventTypeName/oneOf/[subschema12 Group Event Types] {속성} :
  • 'results[/subitems/oneOf} 16 SCALE_SCALE_INITIATED_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 속성 이 'results[/subitems/oneOfScalingNTypesTypes:Seventema]에 새로운 열거형 값을 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/ChartsAudit' 추가
  • 새로운 'CLUSTER_AGENT_IN_CRASH_LOOP' 열거형 값을 '/oneOf[subschema #9: Cluster Events]/eventTypeName' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #1: Any 열거형 이벤트]/eventTypeName/oneOf[subschema #12: 그룹 이벤트 속성 ]/'
  • '/oneOf[subschema] 자동 응답에 '/oneOf[subschema] 자동 응답 감사' 열거 속성 에 새로운 'PREDICTIVE_COMPUT_AUTO_SCALE_INITIATED_BASE, PREDICTIVE_COMPURE_AUTO_SCALE_MAX_INSTANCE_SIZE_FAIL_BASE, PREDICTIVE_COMPUT_AUTO_SCALE_OPLOG_FAIL_BASE' 열거형 값을 추가했습니다.16
  • 새로운 선택적 요청 속성 'advancedConfiguration, replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/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'
  • 'results/items/connections/items/' 응답 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/dataProcessRegion/ 리전' 응답 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'를 추가했습니다.
  • 응답에 대한 'results/items/connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection'을 추가했습니다.
  • 'results/items/dataProcessRegion/ 리전/' 응답 속성 에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'results/items/connections/items/ Amazon Web Services/testBucket'을 추가했습니다.
  • 'connections/items/' 요청 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 'dataProcessRegion/ 리전' 요청 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'가 추가되었습니다.
  • 'connections/items/' 요청 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 'connections/items/' 응답 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'dataProcessRegion/ 리전' 응답 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection'을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 요청 속성 'dataProcessRegion/ 리전 /'에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ Amazon Web Services/testBucket' 추가
  • 새로운 선택적 요청 속성 'connections/items/ Amazon Web Services/testBucket' 추가
  • 'connections/items/' 응답 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'dataProcessRegion/ 리전' 응답 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection'을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ Amazon Web Services/testBucket' 추가
  • ' 리전' 요청 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'가 추가되었습니다.
  • 'connections/items/' 응답 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'dataProcessRegion/ 리전' 응답 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection'을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 요청 속성 ' 리전 /'에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ Amazon Web Services/testBucket' 추가
  • 'results/items/' 응답 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 응답에 선택적 속성 'results/items/ Amazon Web Services/testBucket' 추가
  • 요청 판별자에 'S3' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'S3' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 응답에 선택적 속성 '/ Amazon Web Services/testBucket' 추가
  • 새로운 선택적 요청 속성 '/ Amazon Web Services/testBucket' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'S3' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 응답에 선택적 속성 '/ Amazon Web Services/testBucket' 추가
  • 요청 판별자에 'S3' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'S3' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection' 추가
  • 응답에 선택적 속성 '/ Amazon Web Services/testBucket' 추가
  • 새로운 선택적 요청 속성 '/ Amazon Web Services/testBucket' 추가
  • 'connections/items/' 응답 속성 에 'S3' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'dataProcessRegion/ 리전' 응답 속성 'oneOf' 목록에 '#/components/schemas/ApiStreamsGCPRegionView'를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsS3Connection'을 추가했습니다.
  • 'dataProcessRegion/ 리전/' 응답 속성 에 새로운 'OHIO_USA' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'connections/items/ Amazon Web Services/testBucket' 추가
  • 'results/items/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 새로운 'GROUP_MOVED_FROM_ORG' 열거형 값을 추가했습니다.
  • 새로운 'GROUP_MOVED_FROM_ORG' 열거형 값을 '/oneOf[subschema #8: 조직 이벤트]/eventTypeName' 응답 속성 에 추가했습니다.
  • 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 속성
  • 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일 출시

  • 'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/regionName/oneOf에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다. [subschema #3: GCP Regions]/' 응답 속성
  • 11'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema2 #: Azure 리전3 복제 사양 ] /regionName/oneOf[subschema #: GCP 리전]/' 응답 속성
  • 11'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP 리전3 복제 사양 ] /regionName/oneOf[subschema #: GCP 리전]/' 응답 속성
  • 11'results/items/replicationSpecs/items/regionConfigs/items/oneOf[subschema4 #: 테넌트 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/' 응답 속성
  • 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP 리전]/' 응답 속성 에 새로운 '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]/' 응답 속성
  • 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 'results/items/replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #1: Amazon Web Services 리전에 추가했습니다. ]/' 응답 속성
  • 11'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services3 리전 복제 사양]/regionName/oneOf[subschema #: GCP 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #3에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다. : 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 리전]/' 응답 속성
  • '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 리전 복제 사양]/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 리전 복제 사양]/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 리전 복제 사양]/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]/' 응답 속성
  • '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 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema2 #: Azure 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP 리전 복제 사양]/regionName/ 속성 [subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema4 #: 테넌트 리전 복제 사양]/regionName/ 속성 [subschema3 #: GCP 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/'에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. 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' 열거형 값이 추가되었습니다. '
  • 'providerSettings/oneOf[subschema #3: Cloud Service Provider Settings for the 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' 열거형 값이 추가되었습니다.
  • 11'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services3 리전 복제 사양]/regionName/oneOf[subschema #: GCP 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #3에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다. : 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 리전]/' 응답 속성
  • '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 리전 복제 사양]/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 리전 복제 사양]/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 리전 복제 사양]/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]/' 응답 속성
  • '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[subschema #1: Amazon Web Services3 리전 복제 사양]/regionName/oneOf[subschema #: GCP 리전]/' 응답 속성
  • 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/oneOf[subschema #3에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다. : 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 리전]/' 응답 속성
  • '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 리전 복제 사양]/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 리전 복제 사양]/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 리전 복제 사양]/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]/' 응답 속성
  • '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 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema2 #: Azure 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP 리전 복제 사양]/regionName/ 속성 [subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema4 #: 테넌트 리전 복제 사양]/regionName/ 속성 [subschema3 #: GCP 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/'에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. 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' 열거형 값이 추가되었습니다. '
  • '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' 열거형 값을 추가했습니다.
  • '/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' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #3: Amazon Web Services ]/regionName'에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다.
  • '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' 열거형 값을 추가했습니다.
  • '/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' 응답 속성 에 추가했습니다.
  • 요청 속성 '/oneOf[subschema #2: GCP ]/regions/items/'에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #3: Amazon Web Services ]/regionName'에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다.
  • 'awsKms/ 리전' 응답 속성 에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 추가했습니다.
  • 'awsKms/ 리전' 응답 속성 에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 추가했습니다.
  • 요청 속성 'awsKms/ 리전 '에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 추가했습니다.
  • 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 'results/items/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: Amazon Web Services 리전]/' 응답 속성
  • 571'results/items/oneOf[subschema2 #: Amazon 열거형 Amazon Web Services KMS EAR 비공개 엔드포인트]/regionName/oneOf[subschema2 #: Amazon Web Services 리전]/' 응답 속성
  • 'results/items/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 비공개 엔드포인트]/regionName/oneOf[subschema #2에 추가했습니다. : Amazon Web Services 리전]/' 응답 속성
  • 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 '/oneOf[subschema #2: Amazon Web Services KMS EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: Amazon Web Services 리전]/' 응답 속성
  • 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 'regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 응답 속성 에 추가했습니다.
  • 요청 속성 에 새로운 'AP_SOUTHEAST_,5 AP_SOUTHEAST_,7 MX_CENTRAL_11 ' 열거형 값이 추가되었습니다2.: Amazon Web Services 리전]/'
  • 요청 속성 에 새로운 'AP_SOUTHEAST_,5 AP_SOUTHEAST_,7 MX_CENTRAL_1 ' 열거형 값2 Amazon Web Services 추가 KMS .:2 Amazon Web Services 리전]/'
  • 요청 속성 '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 비공개 엔드포인트]/regionName/oneOf[subschema #2에 추가했습니다. : Amazon Web Services 리전]/' 응답 속성
  • 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 '/oneOf[subschema #2: Amazon Web Services KMS EAR 비공개 엔드포인트]/regionName/oneOf[subschema #2: Amazon Web Services 리전]/' 응답 속성
  • 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값을 'regionName/oneOf[subschema #2: Amazon Web Services Regions]/' 응답 속성 에 추가했습니다.
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf [ subschema1 #: Amazon Web Services 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema2 #: Azure 리전 복제 사양]/regionName/oneOf[subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema3 #: GCP 리전 복제 사양]/regionName/ 속성 [subschema3 #: GCP 리전]/'
  • 11요청 열거형 'replicationSpecs/items/regionConfigs/items/oneOf[subschema4 #: 테넌트 리전 복제 사양]/regionName/ 속성 [subschema3 #: GCP 리전]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/regionName/oneOf[subschema #3: GCP Regions]/'에 새로운 'AFRICA_SOUTH_1, NORTH_AMERICA_SOUTH_1' 열거형 값을 추가했습니다.
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. regionName/oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. oneOf[subschema #1: Amazon Web Services Regions]/'
  • 요청 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #4: 테넌트 리전 복제 사양]/regionName/에 새로운 'AP_SOUTHEAST_5, AP_SOUTHEAST_7, MX_CENTRAL_1' 열거형 값이 추가되었습니다. 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' 열거형 값이 추가되었습니다. '

2025년 2월 20일 출시

  • 요청 속성 'roleMappings/items/roleAssignments/items/ 역할 '에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 요청 속성 'roleAssignments/items/ 역할 '에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 요청 속성 'roleAssignments/items/ 역할 '에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 엔드포인트 사용 중단
  • 요청 속성 'roles/items/'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event types]/' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • '/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' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값이 추가되었습니다.12
  • 요청 속성 에 새로운10 509 3' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다. #: 그룹 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을11 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을12 추가했습니다. : 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.133 알림]/roles/items/'
  • 요청 속성 에 새로운143 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다. 알림]/roles/items/'
  • 요청15 속성 에 새로운3 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다. 그룹 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을1 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운23 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 App Services 을 추가했습니다. 그룹 알림]/roles/items/'
  • 요청 속성 에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER'3 열거형 값 App Services 추가했습니다 .: 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER'4 열거형 값을 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청5 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을6 추가했습니다. : 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을7 추가했습니다 . 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.83 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을9 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이10 509 추가되었습니다. /items/'7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이11 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.127
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이13 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이14 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.157
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.17
  • 요청 속성 알림2 App Services 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.7
  • 요청 속성 알림3 App Services 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이4 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이5 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이6 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.77
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이8 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이9 추가되었습니다.7
  • 요청 열거형 '/oneOf[subschema # {속성}15: Stream Processor
  • 요청 열거형1 '/oneOf[subschema11 #: Any 속성
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • '/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' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • '/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' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • '/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' 열거형 값을 추가했습니다.
  • 요청 속성 에 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값이 추가되었습니다.12
  • 요청 속성 에 새로운10 509 3' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다. #: 그룹 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을11 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을12 추가했습니다. : 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.133 알림]/roles/items/'
  • 요청 속성 에 새로운143 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다. 알림]/roles/items/'
  • 요청15 속성 에 새로운3 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다. 그룹 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을1 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운23 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 App Services 을 추가했습니다. 그룹 알림]/roles/items/'
  • 요청 속성 에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER'3 열거형 값 App Services 추가했습니다 .: 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER'4 열거형 값을 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청5 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을6 추가했습니다. : 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을7 추가했습니다 . 그룹3 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_viewer, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.83 알림]/roles/items/'
  • 요청 속성 에 새로운 ' GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_READ_ONLY, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을9 추가했습니다. 그룹3 알림]/roles/items/'
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이10 509 추가되었습니다. /items/'7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이11 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.127
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이13 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이14 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.157
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.17
  • 요청 속성 알림2 App Services 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.7
  • 요청 속성 알림3 App Services 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이4 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이5 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이6 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이 추가되었습니다.77
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이8 추가되었습니다.7
  • 요청 속성 알림 새로운 'ORG_BILLING_READ_ONLY' 열거형 값이9 추가되었습니다.7
  • 요청 열거형 '/oneOf[subschema # {속성}15: Stream Processor
  • 요청 열거형1 '/oneOf[subschema11 #: Any 속성
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #7: Any Other Alerts]/eventTypeName/oneOf[subschema #14: Stream Processor Event Types]/' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #2: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #15: Stream Processor Alert Configuration]/eventTypeName' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other Alert Configurations]/eventTypeName/oneOf[subschema #11: Stream Processor Event types]/' 응답 속성 에 새로운 'STREAM_PROCESSOR_KAFKA_LAG_BEHIND' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_DATABASE_ACCESS_ADMIN, ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER' 열거형 값을 추가했습니다.
  • 요청 속성 '/items/roles/items/'에 새로운 'GROUP_DATABASE_ACCESS_ADMIN' 열거형 값을 추가했습니다.
  • 요청 선택적 속성 'isCustomShardKeyHashed'가 쓰기 전용이 아닙니다.
  • 요청 선택적 속성 'isShardKeyUnique'가 쓰기 전용이 아닙니다.
  • 요청 선택적 속성 'numInitialChunks'가 쓰기 전용이 아닙니다.
  • 요청 선택적 속성 'presplitHashedZones'가 쓰기 전용이 아닙니다.
  • 요청 필수 속성 'customShardKey'가 읽기 전용이 아닙니다.
  • 응답에 선택적 속성 'results/items/oneOf[subschema #2: Amazon Web Services KMS EAR 비공개 엔드포인트]/privateEndpointConnectionName'을 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName'을 응답에 추가했습니다.
  • 선택적 속성 '/oneOf[subschema #2: Amazon Web Services KMS EAR Private Endpoint]/privateEndpointConnectionName'을 응답에 추가했습니다.
  • 새로운 'ACME_PROVIDER_FIXED, ACME_PROVIDER_UNFIXED' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #34: Version Audit Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_INSTANCE_AGENT_API_KEY_ROTATED, Mongot_LOGS_DOWNLOADED' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event Types]/' 응답 속성 에 추가했습니다.
  • 'results/items/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #30: Stream 응답 속성 프로세서 이벤트 속성 에 새로운 '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' 열거형 값을 추가했습니다.
  • 새로운 'ACME_PROVIDER_FIXED, ACME_PROVIDER_UNFIXED' 열거형 값을 '/oneOf[subschema #1: Any 기타 이벤트]/eventTypeName/oneOf[subschema #34: 버전 감사 유형]/' 응답 속성 에 추가했습니다.
  • '/oneOf[subschema #15: NDS Audits]/eventTypeName' 응답 속성 에 새로운 'CLUSTER_INSTance_AGENT_API_KEY_ROTATED, Mongot_LOGS_DOWNLOADED' 열거형 값을 추가했습니다.
  • 새로운 'CPS_COPY_SNAPSHOT_FAILED_WILL_RETRY' 열거형 값을 '/oneOf[subschema #1: Any Other Events]/eventTypeName/oneOf[subschema #5: Cps Backup Event types]/' 응답 속성 에 추가했습니다.
  • '/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' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_DATABASE_ACCESS_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'GROUP_DATABASE_ACCESS_ADMIN' 열거형 값을 추가했습니다.
  • 요청 속성 '/items/roles/items/'에 새로운 'GROUP_DATABASE_ACCESS_ADMIN' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'isDataExplorerGenAIFeaturesEnabled, isDataExplorerGenAISampleDocumentPassingEnabled'를 추가했습니다.
  • 응답에 선택적 속성 'isDataExplorerGenAIFeaturesEnabled, isDataExplorerGenAISampleDocumentPassingEnabled'를 추가했습니다.
  • 새로운 선택적 요청 속성 'isDataExplorerGenAIFeaturesEnabled, isDataExplorerGenAISampleDocumentPassingEnabled'가 추가되었습니다.
  • 'results/items/connections/items/' 응답 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'results/items/connections/items/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'connections/items/' 요청 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 'connections/items/' 요청 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 속성 'connections/items/type'에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 응답에 선택적 속성 'results/items/interfaceEndpointName'을 추가했습니다.
  • 응답에 선택적 속성 'interfaceEndpointName'을 추가했습니다.
  • 응답에 선택적 속성 'interfaceEndpointName'을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'results/items/' 응답 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'results/items/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 판별자에 'AWSLambda' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'AWSLambda' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 속성 '/type'에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 속성 'type'에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 응답 상태 '200'에 대한 응답 판별자에 'AWSLambda' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 판별자에 'AWSLambda' 매핑 키를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection' 추가
  • 응답 상태 '200'에 대한 응답 판별자에 'AWSLambda' 매핑 키를 추가했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • '/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 속성 '/type'에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 요청 속성 'type'에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 'connections/items/' 응답 속성 에 'AWSLambda' 판별자 매핑 키를 추가했습니다.
  • 응답에 대한 'connections/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/StreamsAWSLambdaConnection'을 추가했습니다.
  • 'connections/items/type' 응답 속성 에 새로운 'AWSLambda' 열거형 값을 추가했습니다.
  • 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'
  • 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'
  • 'results/items/roles/items/' 응답의 속성 유형/형식이 '200' 상태에 대해 ' 객체'/''에서 '문자열'/''로 변경되었습니다.
  • API 태그를 지정하다 ' MongoDB Cloud 사용자' 추가
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'orgMembershipStatus'가 추가되었습니다.
  • 새로운 선택적 ' 쿼리' 요청 매개변수 ' 사용자 이름'이 추가되었습니다.
  • 'results/items/' 응답 속성에 판별자 추가
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/GroupPendingUserResponse, #/components/schemas/GroupActiveUserResponse'를 추가했습니다.
  • 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' 이 필수 항목이 되었습니다.
  • 엔드포인트 추가됨
  • API 태그를 지정하다 ' MongoDB Cloud 사용자' 추가
  • 엔드포인트 추가됨
  • 엔드포인트 사용 중단
  • 요청 속성 'groupRoles/items/'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER' 열거형 값을 추가했습니다.
  • 요청 속성 'apiKey/roles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 엔드포인트 사용 중단
  • 엔드포인트 사용 중단
  • 요청 속성 'groupRoleAssignments/items/roles/items에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 엔드포인트 사용 중단
  • 요청 속성 'groupRoleAssignments/items/roles/items에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 엔드포인트 사용 중단
  • 엔드포인트 사용 중단
  • 엔드포인트 사용 중단
  • 요청 속성 'groupRoleAssignments/items/roles/items에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, GROUP_SEARCH_INDEX_EDITOR, GROUP_STREAM_PROCESSING_OWNER' 열거형 값을 추가했습니다.
  • 요청 속성 'roles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 'results/items/roles' 응답의 속성 유형/형식이 '200' 상태에 대해 ' 배열'/''에서 ' 객체'/''로 변경되었습니다.
  • API 태그를 지정하다 ' MongoDB Cloud 사용자' 추가
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'orgMembershipStatus'가 추가되었습니다.
  • 새로운 선택적 ' 쿼리' 요청 매개변수 ' 사용자 이름'이 추가되었습니다.
  • 'results/items/' 응답 속성에 판별자 추가
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse'를 추가했습니다.
  • 응답에 필수 속성 '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' 이 필수 항목이 되었습니다.
  • 엔드포인트 사용 중단
  • 'results/items/roles' 응답의 속성 유형/형식이 '200' 상태에 대해 ' 배열'/''에서 ' 객체'/''로 변경되었습니다.
  • API 태그를 지정하다 ' MongoDB Cloud 사용자' 추가
  • 새로운 선택적 ' 쿼리' 요청 매개변수 'orgMembershipStatus'가 추가되었습니다.
  • 새로운 선택적 ' 쿼리' 요청 매개변수 ' 사용자 이름'이 추가되었습니다.
  • 'results/items/' 응답 속성에 판별자 추가
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/OrgPendingUserResponse, #/components/schemas/OrgActiveUserResponse'를 추가했습니다.
  • 응답에 필수 속성 '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' 이 필수 항목이 되었습니다.
  • 엔드포인트 추가됨
  • API 태그를 지정하다 ' MongoDB Cloud 사용자' 추가
  • 엔드포인트 추가됨
  • 엔드포인트 추가됨
  • 엔드포인트 사용 중단
  • 요청 속성 'orgRoles/items/'에 새로운 'ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 엔드포인트 사용 중단
  • 요청 속성 'roles/items/roleName'에 새로운 'GROUP_BACKUP_MANAGER, GROUP_DATABASE_ACCESS_ADMIN, GROUP_OBSERVABILITY_ViewER, ORG_BILLING_READ_ONLY' 열거형 값을 추가했습니다.
  • 엔드포인트 사용 중단
  • 엔드포인트 사용 중단

2025년 2월 18일 출시

2025년 2월 06일 출시

  • 'results/items/groupId' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • 'results/items/orgId' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'results/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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/' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'roleAssignments/items/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'roleAssignments/items/orgId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 ' ID'의 경우 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 ' ID'의 경우 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 ' ID'의 경우 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'orgId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'roleAssignments/items/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'roleAssignments/items/orgId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'results/items/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$ '가 제거되었습니다.
  • 'results/items/oneOf[subschema1 #: SAML]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af09{24}-]) $'이(가) 제거되었습니다.
  • 'results/items/oneOf[subschema #2: OIDC WORKFORCE]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이(가) 제거되었습니다.
  • 'results/items/oneOf[subschema3 #: OIDC WORKLOAD]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af09-]{24})$'이(가) 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema1 #: OIDC WORKFORCE]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af -])$'09{24}제거됨
  • '/oneOf[subschema2 #: OIDC WORKLOAD]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af -])$'09{24}제거됨
  • 'relatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema1 #: SAML]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af09{24}-])$' 제거됨
  • '/oneOf[subschema2 #: OIDC WORKFORCE]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af -])$'09{24}제거됨
  • '/oneOf[subschema3 #: OIDC WORKLOAD]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af -])$'09{24}제거됨
  • 'relatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema1 #: SAML]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af09{24}-])$' 제거됨
  • '/oneOf[subschema2 #: OIDC WORKFORCE]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af -])$'09{24}제거됨
  • '/oneOf[subschema3 #: OIDC WORKLOAD]/ associatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af -])$'09{24}제거됨
  • 'relatedOrgs/items/dataAccessIdentityProviderIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'federationSettingsId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'identityProviderId'의 경우 minLength가 '20'에서 '0'으로 감소했습니다.
  • ' 쿼리' 요청 매개변수 'projectOwnerId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 'orgId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'teamIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/items/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #10: NDS X509 사용자 인증 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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: 복제본 세트 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #12: Replica Set 임계값 경고 구성]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #12: 복제본 설정 임계값 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #12: 복제본 임계값 경고 구성 설정]/ 알림/items/oneOf[subschema #11: 팀 알림]/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: 서버리스 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/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 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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 }'11240
  • '/oneOf[subschema #1: Any Other Alert Configurations]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/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 메트릭 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #4: Billing 임계값 경고 구성]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #4: 청구 임계값 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '/oneOf[subschema #4: 청구 임계값 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #5: 클러스터 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #5: 클러스터 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0로 감소되었습니다. '
  • '/oneOf[subschema #6: Cps Backup 임계값 경고 구성]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #6: Cps Backup 임계값 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #7: 암호화 키 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #7: 암호화 키 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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: 호스트 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/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: 호스트 지표 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_EXPOSED, HOST_SECURITY_CHECKUP_NOT_MET, HOST_SSL_CETIFICATE_TALE, HOST_VERSION_BEHIND, VERSION_BEHIND' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/eventTypeName'에 새로운 'TOO_FEW_HEALTHY_MEMBERS, TOO_MANY_UNHEALTHY_MEMBERS' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'alertConfigId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'alertConfigId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'alertConfigId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'alertConfigId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #10: NDS X509 User Authentication Alert Configuration]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #10: NDS X509 사용자 인증 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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: 복제본 세트 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #12: Replica Set 임계값 경고 구성]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #12: 복제본 설정 임계값 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #12: 복제본 임계값 경고 구성 설정]/ 알림/items/oneOf[subschema #11: 팀 알림]/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: 서버리스 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/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 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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 }'11240
  • '/oneOf[subschema #1: Any Other Alert Configurations]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #1: Any 기타 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/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 메트릭 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #4: Billing 임계값 경고 구성]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #4: 청구 임계값 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '/oneOf[subschema #4: 청구 임계값 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #5: Cluster Alert Configuration]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #5: 클러스터 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #5: 클러스터 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0로 감소되었습니다. '
  • '/oneOf[subschema #6: Cps Backup 임계값 경고 구성]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #6: Cps Backup 임계값 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #6: Cps 백업 임계값 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • '/oneOf[subschema #7: Encryption Key Alert Configuration]/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #7: 암호화 키 경고 구성]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '/oneOf[subschema #7: 암호화 키 경고 구성]/ 알림/items/oneOf[subschema #11: 팀 알림]/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: 호스트 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/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: 호스트 지표 경고 구성]/ 알림/items/oneOf[하위 스키마 #11: 팀 알림]/teamId' 요청 속성의 minLength가 '24'에서 '0'
  • 요청 속성 '/oneOf[subschema #8: Host Alert Configuration]/eventTypeName'에 새로운 'HOST_EXPOSED, HOST_SECURITY_CHECKUP_NOT_MET, HOST_SSL_CETIFICATE_TALE, HOST_VERSION_BEHIND, VERSION_BEHIND' 열거형 값을 추가했습니다.
  • 요청 속성 '/oneOf[subschema #12: 복제본 세트 임계값 경고 구성]/eventTypeName'에 새로운 'TOO_FEW_HEALTHY_MEMBERS, TOO_MANY_UNHEALTHY_MEMBERS' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'alertConfigId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'alertId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'alertId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'alertId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'apiUserId'의 경우 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'apiUserId'의 경우 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'apiUserId'의 경우 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/items/userId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/iamRoleId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '/roleId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'exportBucketId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'exportBucketId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'onDemandPolicyItem/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'projectId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'scheduledPolicyItems/items/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/roleId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '/ _id' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'roleId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'roleId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'roleId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/zoneId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 선택적 속성 'providerSettings/EffectiveDiskSizeGBLimit, providerSettings/EffectiveInstanceSizeName, providerSettings/EffectiveProviderName'을 응답에 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/zoneId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'exportBucketId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'snapshotId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'exportId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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'로 감소되었습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'restoreJobId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'restoreJobId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'clusterId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'clusterName' 요청 속성의 minLength가 '1'에서 '0'로 감소했습니다.
  • 'export/exportBucketId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '정책/항목/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'poliencies/items/policyItems/items/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'results/items/snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'results/items/snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'restoreId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'checkpointId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'indexID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'indexId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'indexId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'indexId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'indexID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' _id' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'clusterName' 요청 속성의 minLength가 '1'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'archiveId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'archiveId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'archiveId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' _id' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'clusterName' 요청 속성의 minLength가 '1'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'clusterName' 요청 속성의 minLength가 '1'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'suggestedIndexes/items/ 영향/items/' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' 쿼리' 요청 매개변수 'batchId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'jobId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'indexId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'indexId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'indexId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'clusterId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'clusterId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'parts/items/clusterId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 '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' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 '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' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'containerId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'containerId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #1: Azure]/vnetName' 응답의 속성 패턴 이 '^([-\w._()])+$'에서 '^([-\w._() ])$'
  • '/oneOf[subschema #1: Azure]/ 리전' 응답 속성 에 새로운 'MEXICO_CENTRAL, NEW_ZEALAND_NORTH, SPAIN_CENTRAL' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'containerId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'results/items/groupId' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'scopes/items/name' 요청 속성의 minLength가 '1'에서 '0'로 감소했습니다.
  • 요청 속성 'groupId'에서 '^([af0-9]{24})$' 패턴 제거했습니다.
  • 'groupId' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'scopes/items/name' 요청 속성의 minLength가 '1'에서 '0'로 감소했습니다.
  • 요청 속성 'groupId'에서 '^([af0-9]{24})$' 패턴 제거했습니다.
  • 'groupId' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'accessLogs/items/groupId' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'accessLogs/items/groupId' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 선택적 속성 'awsKms/requirePrivateNetworking'을 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'awsKms/roleId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 응답에 선택적 속성 'awsKms/requirePrivateNetworking'을 추가했습니다.
  • 새로운 선택적 요청 속성 'awsKms/requirePrivateNetworking'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/AWSKMSEARPrivateEndpoint'를 추가했습니다.
  • 응답에 대한 'results/items/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName' 응답 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • 응답에 대한 'results/items/regionName' 응답 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • '경로' 요청 매개변수 'cloudProvider'에 새 열거형 값 ' Amazon Web Services '를 추가했습니다.
  • 요청 본문 'oneOf' 목록에 '#/components/schemas/AWSKMSEARPrivateEndpoint'를 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/ ID' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName' 요청 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • 'regionName' 요청 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/AWSKMSEARPrivateEndpoint'를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName' 응답 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • 응답에 대한 'regionName' 응답 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • '경로' 요청 매개변수 'cloudProvider'에 새 열거형 값 ' Amazon Web Services '를 추가했습니다.
  • 요청 속성 에 새로운 ' Amazon Web Services' 열거형 값을 추가했습니다. '/oneOf[subschema #1: Azure Key Vault EAR Private Endpoint]/cloudProvider'
  • 요청 속성 'cloudProvider'에 새로운 ' Amazon Web Services' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'cloudProvider'에 새 열거형 값 ' Amazon Web Services '를 추가했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/AWSKMSEARPrivateEndpoint'를 추가했습니다.
  • 응답에 대한 '/oneOf[subschema #1: Azure Key Vault EAR 비공개 엔드포인트]/regionName' 응답 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • 응답에 대한 'regionName' 응답 속성 'oneOf' 목록에 'subschema #2: Amazon Web Services Regions' 추가
  • '경로' 요청 매개변수 'cloudProvider'에 새 열거형 값 ' Amazon Web Services '를 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 대한 'results/items/' 응답 속성 'oneOf' 목록에 '#/components/schemas/DataExplorerEvent'를 추가했습니다.
  • '경로' 요청 매개변수 'eventId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 대한 응답 본문 'oneOf' 목록에 '#/components/schemas/DataExplorerEvent'를 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'clusterType' 응답의 속성 기본값 'REPLICASET'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 'clusterType' 응답의 속성 기본값 'REPLICASET'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 'clusterType' 응답의 속성 기본값 'REPLICASET'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 'clusterType' 응답의 속성 기본값 'REPLICASET'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 'snapshotId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 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'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'restoreJobId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #1: Amazon Web Services 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용으로 변경됨
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #2: Azure 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/analyticsAutoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/maxInstanceSize'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'replicationSpecs/items/regionConfigs/items/oneOf[subschema #3: GCP 리전 복제 사양]/autoScaling/compute/minInstanceSize'가 읽기 전용이 되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/ ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'replicationSpecs/items/zoneId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • 'clusterType' 응답의 속성 기본값 'REPLICASET'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'indexIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'indexIds/items/' 응답의 속성 패턴 '^([af0-9]{24})$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'invitationId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'invitationId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'invitationId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' _id' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'destination/groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'source/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' _id' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'destination/groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'source/groupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'validationId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'liveMigrationId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'liveMigrationId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'results/items/oneOf[subschema #2: Azure]/vnetName' 응답의 속성 패턴 이 '^([-\w._()])+$'에서 '^([-\w. _()])$'
  • '경로' 요청 매개변수 '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._() ])$'
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'peerId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'peerId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '/oneOf[subschema #2: Azure]/vnetName' 응답의 속성 패턴 이 '^([-\w._()])+$'에서 '^([-\w._() ])$'
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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._() ])$'
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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: Periodic Cloud Provider Snapshot Source]/policyItemId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '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: Periodic Cloud Provider Snapshot Source]/policyItemId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 'results/items/snapshotType' 응답 속성 에 새로운 'fallback' 열거형 값을 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'pipelineRunId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'pipelineRunId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'path' 요청 매개변수 'pipelineName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 'snapshotId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointServiceId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointServiceId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointServiceId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointServiceId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointServiceId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'endpointId' 요청 속성의 minLength가 '22'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '22'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'endpointId'의 경우 minLength가 '22'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'suggestedIndexes/items/ 영향/items/' 응답의 속성 패턴 '^([af09{24}-])$'이 제거되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'sampleDatasetId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 선택적 속성 'results/items/providerSettings/EffectiveDiskSizeGBLimit, results/items/providerSettings/EffectiveInstanceSizeName, results/items/providerSettings/EffectiveProviderName'을(를) 응답에 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 'name' 요청 속성의 minLength가 '1'에서 '0'(으)로 감소했습니다.
  • 선택적 속성 'providerSettings/EffectiveDiskSizeGBLimit, providerSettings/EffectiveInstanceSizeName, providerSettings/EffectiveProviderName'을 응답에 추가했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' ID' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'snapshotId' 요청 속성의 minLength가 '24'에서 '0'로 감소했습니다.
  • 'targetClusterName' 요청 속성의 minLength가 '1'에서 '0'로 감소되었습니다.
  • 'targetGroupId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'restoreJobId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'snapshotId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'clusterName'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 선택적 속성 'providerSettings/EffectiveDiskSizeGBLimit, providerSettings/EffectiveInstanceSizeName, providerSettings/EffectiveProviderName'을 응답에 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 '이름'의 경우 minLength가 '1'에서 '0'로 감소했습니다.
  • 선택적 속성 'providerSettings/EffectiveDiskSizeGBLimit, providerSettings/EffectiveInstanceSizeName, providerSettings/EffectiveProviderName'을 응답에 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • ' _id' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • 'connections/items/net워킹/ 액세스/connectionId' 요청 속성의 minLength가 '24'에서 '0'로 감소되었습니다.
  • 'groupId' 요청 속성의 minLength가 '24'에서 '0'(으)로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 선택적 속성 'results/items/arn, results/items/errorMessage, results/items/providerAccountId'를 추가했습니다.
  • 요청 선택적 속성 ' _id'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 'interfaceEndpointId'가 읽기 전용이 되었습니다.
  • 요청 선택적 속성 '상태'가 읽기 전용이 되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 선택적 속성 'arn, errorMessage, providerAccountId'를 추가했습니다.
  • 새로운 선택적 요청 속성 'arn'이 추가되었습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • 응답에 선택적 속성 'arn, errorMessage, providerAccountId'를 추가했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.
  • '경로' 요청 매개변수 'groupId'의 경우 minLength가 '24'에서 '0'로 감소했습니다.