Changes to Create Transit Gateway

Changed in 9 of the 75 revisions of this API.▲71●23○46

1. Mar 16, 2026377981ac9f14▲1○1
2. Mar 11, 2026c5d7b6bc7ab1○2
3. Jan 20, 20267bc7400170e0▲1○1
4. Jan 7, 202641f50b46b442●5
5. Oct 23, 20258ab3ec3ed301●1
6. Aug 22, 20253c0154b2053a▲19
7. Aug 14, 20256333a0d3b095▲15●3○36
8. Jul 22, 202576b0fefddb0d▲35●14○3
9. May 14, 202587c135153b84○3

What changed

• Mar 16, 2026377981ac9f14▲1○1See the full diff
  • ▲

    added the new required request property oneOf[subschema #5: Azure Virtual Hub Peering Gateway]/transit_gateway_attachment_config

    new-required-request-property

  • ○

    added the required property oneOf[subschema #4: Azure Virtual Hub Peering Gateway]/transit_gateway_attachment_config to the response with the 201 status

    response-required-property-added

• Mar 11, 2026c5d7b6bc7ab1○2See the full diff
  • ○

    added the optional property oneOf[subschema #1: AWS Transit Gateway]/transit_gateway_attachment_config/attachment_id to the response with the 201 status

    response-optional-property-added

  • ○

    added the optional property oneOf[subschema #2: AWS VPC Peering Gateway]/transit_gateway_attachment_config/peering_connection_id to the response with the 201 status

    response-optional-property-added

• Jan 20, 20267bc7400170e0▲1○1See the full diff
  • ▲

    added AzureVHubPeeringGatewayResponse to the response body oneOf list for the response status 201

    response-body-one-of-added

  • ○

    added CreateAzureVHubPeeringGateway to the request body oneOf list

    request-body-one-of-added

• Jan 7, 202641f50b46b442●5See the full diff
  • ●

    added the new error enum value to the oneOf[subschema #1: AWS Transit Gateway]/state response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new error enum value to the oneOf[subschema #2: AWS VPC Peering Gateway]/state response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new error enum value to the oneOf[subschema #3: Azure Transit Gateway]/state response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new error enum value to the oneOf[subschema #4: GCP VPC Peering Transit Gateway]/state response property for the response status 201

    response-property-enum-value-added

  • ●

    added the new error enum value to the oneOf[subschema #5: AWS Resource Endpoint Gateway]/state response property for the response status 201

    response-property-enum-value-added

• Oct 23, 20258ab3ec3ed301●1See the full diff
  • ●

    added the new type enum value to the allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterStandard]/rule response property for the response status 400

    response-property-enum-value-added

• Aug 22, 20253c0154b2053a▲19See the full diff
  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterChoiceItem]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterDependentItem]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterMaximumLength]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterMinimumLength]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property allOf[subschema #2]/invalid_parameters/items/oneOf[#/components/schemas/InvalidParameterStandard]/source became nullable for the status 400

    response-property-became-nullable

  • ▲

    the response property detail became nullable for the status 401

    response-property-became-nullable

  • ▲

    the response property instance became nullable for the status 401

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #1: AWS Transit Gateway]/state_metadata/reason became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #1: AWS Transit Gateway]/state_metadata/reported_status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #2: AWS VPC Peering Gateway]/state_metadata/reason became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #2: AWS VPC Peering Gateway]/state_metadata/reported_status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #3: Azure Transit Gateway]/state_metadata/reason became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #3: Azure Transit Gateway]/state_metadata/reported_status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #4: GCP VPC Peering Transit Gateway]/state_metadata/reason became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #4: GCP VPC Peering Transit Gateway]/state_metadata/reported_status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #5: AWS Resource Endpoint Gateway]/state_metadata/reason became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property oneOf[subschema #5: AWS Resource Endpoint Gateway]/state_metadata/reported_status became nullable for the status 201

    response-property-became-nullable

  • ▲

    the response property status became nullable for the status 401

    response-property-became-nullable

  • ▲

    the response property title became nullable for the status 401

    response-property-became-nullable

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 14, 20256333a0d3b095▲15●3○36See the full diff
  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAwsTransitGateway -> subschema #1: AWS Transit Gateway]/cidr_blocks

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAwsTransitGateway -> subschema #1: AWS Transit Gateway]/name

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAwsTransitGateway -> subschema #1: AWS Transit Gateway]/transit_gateway_attachment_config

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAwsVpcPeeringGateway -> subschema #2: AWS VPC Peering Gateway]/cidr_blocks

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAwsVpcPeeringGateway -> subschema #2: AWS VPC Peering Gateway]/name

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAwsVpcPeeringGateway -> subschema #2: AWS VPC Peering Gateway]/transit_gateway_attachment_config

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway]/name

    new-required-request-property

  • ▲

    added the new required request property oneOf[#/components/schemas/CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway]/transit_gateway_attachment_config

    new-required-request-property

  • ▲

    the oneOf[#/components/schemas/CreateAwsTransitGateway -> subschema #1: AWS Transit Gateway] request property type changed from no type to object

    request-property-type-changed

  • ▲

    the oneOf[#/components/schemas/CreateAwsVpcPeeringGateway -> subschema #2: AWS VPC Peering Gateway] request property type changed from no type to object

    request-property-type-changed

  • ▲

    the oneOf[#/components/schemas/CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway] request property type changed from no type to object

    request-property-type-changed

  • ▲

    added GCPVPCPeeringGatewayResponse AwsResourceEndpointGatewayResponse to the response body oneOf list for the response status 201

    response-body-one-of-added

  • ▲

    the oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway] response's property type changed from no type to object for status 201

    response-property-type-changed

  • ▲

    the oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway] response's property type changed from no type to object for status 201

    response-property-type-changed

  • ▲

    the oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway] response's property type changed from no type to object for status 201

    response-property-type-changed

  • ●

    removed AwsTransitGateway subschema #2 subschema #3 from the oneOf[#/components/schemas/CreateAwsTransitGateway -> subschema #1: AWS Transit Gateway] request property allOf list

    request-property-all-of-removed

  • ●

    removed AwsVpcPeeringGateway subschema #2 subschema #3 from the oneOf[#/components/schemas/CreateAwsVpcPeeringGateway -> subschema #2: AWS VPC Peering Gateway] request property allOf list

    request-property-all-of-removed

  • ●

    removed AzureTransitGateway subschema #2 subschema #3 from the oneOf[#/components/schemas/CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway] request property allOf list

    request-property-all-of-removed

  • ○

    added the new optional request property oneOf[#/components/schemas/CreateAwsTransitGateway -> subschema #1: AWS Transit Gateway]/dns_config

    new-optional-request-property

  • ○

    added the new optional request property oneOf[#/components/schemas/CreateAwsVpcPeeringGateway -> subschema #2: AWS VPC Peering Gateway]/dns_config

    new-optional-request-property

  • ○

    added the new optional request property oneOf[#/components/schemas/CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway]/dns_config

    new-optional-request-property

  • ○

    added CreateAwsResourceEndpointGateway CreateGCPVPCPeeringTransitGateway to the request body oneOf list

    request-body-one-of-added

  • ○

    added the optional property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/state_metadata to the response with the 201 status

    response-optional-property-added

  • ○

    added the optional property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/state_metadata to the response with the 201 status

    response-optional-property-added

  • ○

    added the optional property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/state_metadata to the response with the 201 status

    response-optional-property-added

  • ○

    removed AwsTransitGateway BaseTransitGatewayResponse subschema #2 from the oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway] response property allOf list for the response status 201

    response-property-all-of-removed

  • ○

    removed AwsVpcPeeringGateway BaseTransitGatewayResponse subschema #2 from the oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway] response property allOf list for the response status 201

    response-property-all-of-removed

  • ○

    removed AzureTransitGateway BaseTransitGatewayResponse from the oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway] response property allOf list for the response status 201

    response-property-all-of-removed

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/cidr_blocks to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/created_at to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/dns_config to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/entity_version to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/id to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/name to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/state to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/transit_gateway_attachment_config to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/updated_at to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/cidr_blocks to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/created_at to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/dns_config to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/entity_version to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/id to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/name to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/state to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/transit_gateway_attachment_config to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/updated_at to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/created_at to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/dns_config to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/entity_version to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/id to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/name to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/state to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/transit_gateway_attachment_config to the response with the 201 status

    response-required-property-added

  • ○

    added the required property oneOf[#/components/schemas/AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/updated_at to the response with the 201 status

    response-required-property-added

  This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 22, 202576b0fefddb0d▲35●14○3See the full diff
  • ▲

    added AwsTransitGateway subschema #2 subschema #3 to the oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/CreateAwsTransitGateway] request property allOf list

    request-property-all-of-added

  • ▲

    added AwsVpcPeeringGateway subschema #2 subschema #3 to the oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/CreateAwsVpcPeeringGateway] request property allOf list

    request-property-all-of-added

  • ▲

    added AzureTransitGateway subschema #2 subschema #3 to the oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/CreateAzureTransitGateway] request property allOf list

    request-property-all-of-added

  • ▲

    the oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/CreateAwsTransitGateway] request property type changed from object to no type

    request-property-type-changed

  • ▲

    the oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/CreateAwsVpcPeeringGateway] request property type changed from object to no type

    request-property-type-changed

  • ▲

    the oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/CreateAzureTransitGateway] request property type changed from object to no type

    request-property-type-changed

  • ▲

    the oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse] response's property type changed from object to no type for status 201

    response-property-type-changed

  • ▲

    the oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse] response's property type changed from object to no type for status 201

    response-property-type-changed

  • ▲

    the oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse] response's property type changed from object to no type for status 201

    response-property-type-changed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/cidr_blocks from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/created_at from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/dns_config from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/entity_version from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/id from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/name from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/state from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/transit_gateway_attachment_config from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/updated_at from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/cidr_blocks from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/created_at from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/dns_config from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/entity_version from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/id from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/name from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/state from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/transit_gateway_attachment_config from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/updated_at from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/created_at from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/dns_config from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/entity_version from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/id from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/name from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/state from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/transit_gateway_attachment_config from the response with the 201 status

    response-required-property-removed

  • ▲

    removed the required property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/updated_at from the response with the 201 status

    response-required-property-removed

  • ●

    removed the request property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/CreateAwsTransitGateway]/cidr_blocks

    request-property-removed

  • ●

    removed the request property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/CreateAwsTransitGateway]/dns_config

    request-property-removed

  • ●

    removed the request property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/CreateAwsTransitGateway]/name

    request-property-removed

  • ●

    removed the request property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/CreateAwsTransitGateway]/transit_gateway_attachment_config

    request-property-removed

  • ●

    removed the request property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/CreateAwsVpcPeeringGateway]/cidr_blocks

    request-property-removed

  • ●

    removed the request property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/CreateAwsVpcPeeringGateway]/dns_config

    request-property-removed

  • ●

    removed the request property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/CreateAwsVpcPeeringGateway]/name

    request-property-removed

  • ●

    removed the request property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/CreateAwsVpcPeeringGateway]/transit_gateway_attachment_config

    request-property-removed

  • ●

    removed the request property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/CreateAzureTransitGateway]/dns_config

    request-property-removed

  • ●

    removed the request property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/CreateAzureTransitGateway]/name

    request-property-removed

  • ●

    removed the request property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/CreateAzureTransitGateway]/transit_gateway_attachment_config

    request-property-removed

  • ●

    removed the optional property oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse]/state_metadata from the response with the 201 status

    response-optional-property-removed

  • ●

    removed the optional property oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse]/state_metadata from the response with the 201 status

    response-optional-property-removed

  • ●

    removed the optional property oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse]/state_metadata from the response with the 201 status

    response-optional-property-removed

  • ○

    added AwsTransitGateway BaseTransitGatewayResponse subschema #2 to the oneOf[subschema #1: AWS Transit Gateway -> #/components/schemas/AwsTransitGatewayResponse] response property allOf list for the response status 201

    response-property-all-of-added

  • ○

    added AwsVpcPeeringGateway BaseTransitGatewayResponse subschema #2 to the oneOf[subschema #2: AWS VPC Peering Gateway -> #/components/schemas/AwsVpcPeeringGatewayResponse] response property allOf list for the response status 201

    response-property-all-of-added

  • ○

    added AzureTransitGateway BaseTransitGatewayResponse to the oneOf[subschema #3: Azure Transit Gateway -> #/components/schemas/AzureTransitGatewayResponse] response property allOf list for the response status 201

    response-property-all-of-added

• May 14, 202587c135153b84○3See the full diff
  • ○

    added the optional property oneOf[subschema #1: AWS Transit Gateway]/state_metadata to the response with the 201 status

    response-optional-property-added

  • ○

    added the optional property oneOf[subschema #2: AWS VPC Peering Gateway]/state_metadata to the response with the 201 status

    response-optional-property-added

  • ○

    added the optional property oneOf[subschema #3: Azure Transit Gateway]/state_metadata to the response with the 201 status

    response-optional-property-added

  This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog