Sign in
Transit Gateways

Create Transit Gateway

Creates a new transit gateway attachment for a given network. The attachment type is determined by the transit_gateway_attachment_config.kind field. Supported types: aws-transit-gateway-attachment, aws-vpc-peering-attachment, aws-resource-endpoint-attachment, azure-vnet-peering-attachment, azure-vhub-peering-attachment, and gcp-vpc-peering-attachment. Creation is asynchronous — the transit gateway starts in initializing state and transitions to ready once provisioned.

post/v2/cloud-gateways/networks/{networkId}/transit-gateways

Path parameters

networkIdstring uuid required

The network ID to operate on. For serverless.v1 kind of cloud gateways, this field should be omitted.

Example:36ae63d3-efd1-4bec-b246-62aa5d3f5695

The network to operate on.

Request body

OR
OR
OR
OR
OR

Example request

{
  "name": "us-east-2 transit gateway",
  "dns_config": [
    {
      "remote_dns_server_ip_addresses": [
        "10.0.0.2"
      ],
      "domain_proxy_list": [
        "foobar.com"
      ]
    }
  ],
  "cidr_blocks": [
    "10.0.0.0/8",
    "100.64.0.0/10",
    "172.16.0.0/12"
  ]
}

Response

Response format for creating a transit gateway.

OR
OR
OR
OR
OR

Example response

{
  "name": "us-east-2 transit gateway",
  "dns_config": [
    {
      "remote_dns_server_ip_addresses": [
        "10.0.0.2"
      ],
      "domain_proxy_list": [
        "foobar.com"
      ]
    }
  ],
  "cidr_blocks": [
    "10.0.0.0/8",
    "100.64.0.0/10",
    "172.16.0.0/12"
  ],
  "id": "0850820b-d153-4a2a-b9be-7d2204779139",
  "state_metadata": {
    "reported_status": "ERROR",
    "reason": "Transit Gateway Attachment configuration could not find a resource with the provided ram share arn.\n"
  },
  "entity_version": 1,
  "created_at": "2022-11-04T20:10:06.927Z",
  "updated_at": "2022-11-04T20:10:06.927Z"
}

Changes

Changed in 9 of the 75 revisions of this API.712346

  • 377981ac9f1411See 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

  • c5d7b6bc7ab12See 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

  • 7bc7400170e011See 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

  • 41f50b46b4425See 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

  • 8ab3ec3ed3011See the full diff
    • ●

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

      response-property-enum-value-added

  • 3c0154b2053a19See the full diff
    • ▲

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

      response-property-became-nullable

    • ▲

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

      response-property-became-nullable

    • ▲

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

      response-property-became-nullable

    • ▲

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

      response-property-became-nullable

    • ▲

      the response property allOf[subschema #2]/invalid_parameters/items/oneOf[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

  • 6333a0d3b09515336See the full diff
    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      new-required-request-property

    • ▲

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

      request-property-type-changed

    • ▲

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

      request-property-type-changed

    • ▲

      the oneOf[CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway]/ request property type/format changed from / 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[AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/ response's property type/format changed from / to object/ for status 201

      response-property-type-changed

    • ▲

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

      response-property-type-changed

    • ▲

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

      response-property-type-changed

    • ●

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

      request-property-all-of-removed

    • ●

      removed AwsVpcPeeringGateway subschema #2 subschema #3 from the oneOf[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[CreateAzureTransitGateway -> subschema #4: Azure Transit Gateway]/ request property allOf list

      request-property-all-of-removed

    • ○

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

      new-optional-request-property

    • ○

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

      new-optional-request-property

    • ○

      added the new optional request property oneOf[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[AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/state_metadata to the response with the 201 status

      response-optional-property-added

    • ○

      added the optional property oneOf[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[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[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[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[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[AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/cidr_blocks to the response with the 201 status

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

      added the required property oneOf[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[AwsTransitGatewayResponse -> subschema #1: AWS Transit Gateway]/updated_at to the response with the 201 status

      response-required-property-added

    • ○

      added the required property oneOf[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[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[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[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[AwsVpcPeeringGatewayResponse -> subschema #2: AWS VPC Peering Gateway]/id to the response with the 201 status

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

      added the required property oneOf[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[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[AzureTransitGatewayResponse -> subschema #3: Azure Transit Gateway]/created_at to the response with the 201 status

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

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

      response-required-property-added

    • ○

      added the required property oneOf[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[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

  • 76b0fefddb0d35143See the full diff
    • ▲

      added AwsTransitGateway subschema #2 subschema #3 to the oneOf[subschema #1: AWS Transit Gateway -> 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 -> CreateAwsVpcPeeringGateway]/ request property allOf list

      request-property-all-of-added

    • ▲

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

      request-property-all-of-added

    • ▲

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

      request-property-type-changed

    • ▲

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

      request-property-type-changed

    • ▲

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

      request-property-type-changed

    • ▲

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

      response-property-type-changed

    • ▲

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

      response-property-type-changed

    • ▲

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

      response-property-type-changed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

      removed the required property oneOf[subschema #1: AWS Transit Gateway -> 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 -> 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 -> 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 -> 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 -> 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 -> 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 -> AwsVpcPeeringGatewayResponse]/id from the response with the 201 status

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

      removed the required property oneOf[subschema #2: AWS VPC Peering Gateway -> 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 -> AwsVpcPeeringGatewayResponse]/updated_at from the response with the 201 status

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

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

      response-required-property-removed

    • ▲

      removed the required property oneOf[subschema #3: Azure Transit Gateway -> 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 -> AzureTransitGatewayResponse]/updated_at from the response with the 201 status

      response-required-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

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

      request-property-removed

    • ●

      removed the optional property oneOf[subschema #1: AWS Transit Gateway -> 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 -> AwsVpcPeeringGatewayResponse]/state_metadata from the response with the 201 status

      response-optional-property-removed

    • ●

      removed the optional property oneOf[subschema #3: Azure Transit Gateway -> 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 -> 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 -> 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 -> AzureTransitGatewayResponse]/ response property allOf list for the response status 201

      response-property-all-of-added

  • 87c135153b843See 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