Feature Request: HTTP Request Headers

[mikeroll]

I would love to be able to configure the provider to send specific headers with each API request. Theoretically something along these lines:

provider "rabbitmq" {
  endpoint = ...
  username = ...
  password = ...

  request_header {
    name = "X-Client-Id"
    value = "id"
  }

  request_header {
    name = "X-Client-Secret"
    value = "secret"
  }
}

My use case is a RabbitMQ instance secured with Cloudflare Access. The short story is that it adds an extra authentication layer in front of a web endpoint; completing the auth flow for non-interactive access (such as by a Terraform provider) results in obtaining a session token; the token value is then to be sent along with each request to the protected service.
Many other "ZTA" or "Delegated SSO" solutions employ the same approach so I believe supporting arbitrary headers would enable or simplify the usage of the provider in such environments.

Would you be up for including this functionality? If so I could take a stab at implementing it - from what I understand this is mostly about extending the configuration interface + probably adjusting the RoundTripper to plug the headers everywhere.

[rfavreau]

@mikeroll @thomasLeclaire

This feature is available into rfd59/rabbitmq provider.

terraform {
  required_providers {
    rabbitmq = {
      source = "rfd59/rabbitmq"
      version = "2.3.0"
    }
  }
}

provider "rabbitmq" {
  endpoint = "http://127.0.0.1:15672"
  username = "guest"
  password = "guest"

  headers = {
    "X-Client-Id" = "id",
    "X-Client-Secret" = "secret"
  }
}

Thanks to @Dbzman