Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes​

What types of changes does your code introduce to ? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist​

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments​

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes​

What types of changes does your code introduce to ? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist​

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments​

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Types of changes​

What types of changes does your code introduce to ? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist​

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments​

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

This pull request completes the work for enabling VPC link REST APIs, as well as making it possible to support proxy paths so that the path can be passed through to the underlying APIs. Adding support for the root resource allows using an API gateway per API, instead of a single instance with paths.

Types of changes​

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist​

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments​

Sample usage of the module for a REST API that's using proxy for VPC link (including proxy paths):

module "api_gateway" {
  source     = "git::https://github.com/mydeal-com-au/terraform-aws-api-gateway.git"
  depends_on = [module.eb_windows]

  for_each           = { for api in try(local.workspace.api_gateway.apis, []) : api.name => api }
  environment_name   = local.workspace.environment_name
  name               = each.value.name
  api_type           = try(each.value.api_type, "rest")
  create_vpc_link    = try(each.value.create_vpc_link, true)
  vpc_link_target_id = try(each.value.create_vpc_link, true) ? module.eb_windows[each.value.application_environment].eb_load_balancers[0] : null
  create_api_key     = try(each.value.create_api_key, false)
  domains = [
    for env_app in
    flatten([
      for environment in try(local.workspace.eb_app.environments, []) : [
        for app in environment.apps : {
          environment = environment
          app         = app
        } if try(app.use_api_gateway, false) && app.name == each.value.application_name
      ] if environment.name == each.value.application_environment
      ]) : {
      domain            = "${try(env_app.app.hostname, env_app.app.name)}.${try(local.workspace.eb_app.use_master_hosted_zone, false) ? local.workspace.master_hosted_zone : local.workspace.hosted_zone}"
      api_route_mapping = null
      zone_name         = try(local.workspace.eb_app.use_master_hosted_zone, false) ? local.workspace.master_hosted_zone : local.workspace.hosted_zone
    }
  ]
  routes = flatten([
    for env_app in
    flatten([
      for environment in try(local.workspace.eb_app.environments, []) : [
        for app in environment.apps : {
          environment = environment
          app         = app
        } if try(app.use_api_gateway, false) && app.name == each.value.application_name
      ] if environment.name == each.value.application_environment
      ]) : [
      {
        name             = "root"
        method           = try(each.value.method, "ANY")
        integration_type = try(each.value.integration_type, "HTTP_PROXY")
        integration_uri  = "https://${try(env_app.app.hostname, env_app.app.name)}.${try(local.workspace.eb_app.use_master_hosted_zone, false) ? local.workspace.master_hosted_zone : local.workspace.hosted_zone}/"
        route_mapping    = null
        path_parameters  = []
        connection_type  = try(each.value.connection_type, "VPC_LINK")
      },
      {
        name             = "${env_app.app.name}-load-balancer"
        method           = try(each.value.method, "ANY")
        integration_type = try(each.value.integration_type, "HTTP_PROXY")
        integration_uri  = "https://${try(env_app.app.hostname, env_app.app.name)}.${try(local.workspace.eb_app.use_master_hosted_zone, false) ? local.workspace.master_hosted_zone : local.workspace.hosted_zone}/{proxy}"
        route_mapping    = "{proxy+}"
        path_parameters  = ["proxy"]
        connection_type  = try(each.value.connection_type, "VPC_LINK")
      }
  ]])
}

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes​

What types of changes does your code introduce to ? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist​

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING.md doc.
• I have added necessary documentation (if appropriate).
• Any dependent changes have been merged and published in downstream modules.

Further comments​

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Add VPC Link configuration for rest api