Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Ingress Gateway config entries #199

Closed
woz5999 opened this issue Jun 22, 2020 · 1 comment · Fixed by #202
Closed

Add support for Ingress Gateway config entries #199

woz5999 opened this issue Jun 22, 2020 · 1 comment · Fixed by #202

Comments

@woz5999
Copy link

woz5999 commented Jun 22, 2020

Terraform Version

All versions

Affected Resource(s)

  • consul_config_entry

Terraform Configuration Files

resource "consul_config_entry" "default" {
  kind = "ingress-gateway"
  name = var.ingress_gateway_service_name

  config_json = jsonencode({
     Listeners = [
      {
        Port     = var.por
        Protocol = var.protocol
        Services = var.services
      }
    ]
  })
}

Expected Behavior

No errors

Actual Behavior

Error: Failed to decode config entry: invalid config entry kind: ingress-gateway

Important Factoids

The specific error messages seems to be coming from the vendored hashicorp/consul api package. The current package has support for this config entry type, so I believe the provider just needs an update/build/release to resolve this issue.

config_entry.go

@remilapeyre
Copy link
Collaborator

Hi @woz5999, Ingress Gateway are a new feature of Consul 1.8 that just got released. I'm still working on the integration of those features in the Terraform provider but I hope to be able to make a new release shortly :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants