A (maintained) fork of https://github.com/humio/terraform-provider-humio which was deleted.
The provider is published in the official Hashicorp Terraform registry, so it can used like any other published provider:
terraform {
required_providers {
humio = {
source = "clearhaus/humio"
version = "0.5.0"
}
}
}
Alternatively, the provider be built locally for development. To do so:
-
Clone the git repository of the provider
git clone https://github.com/clearhaus/terraform-provider-humio cd terraform-provider-humio
-
Build the provider plugin
go build -o terraform-provider-humio
-
Create
~/.terraformrc
with the following content:provider_installation { dev_overrides { "clearhaus/humio" = "<path-to-repo>" } # For all other providers, install them directly from their origin provider # registries as normal. If you omit this, Terraform will _only_ use # the dev_overrides block, and so no other providers will be available. direct {} }
Make sure to update the path in the above to the recently cloned
terraform-provider-humio
repository.
When running a Terraform command with the publisher defined in ~/.terraformrc
, the following warning will be shown:
╷
│ Warning: Provider development overrides are in effect
│
│ The following provider development overrides are set in the CLI configuration:
│ - clearhaus/humio in <path-to-repo>
│
│ The behavior may therefore not match any released version of the provider and applying changes may cause the state to become incompatible with published releases.
╵
The provider is configured through the environment variables HUMIO_ADDR
and HUMIO_API_TOKEN
.
Alternatively, the configurations can be hardcoded in the Terraform provider definition:
provider "humio" {
addr = "https://humio.example.com/"
api_token = "XXXXXXXXXXXXXXXXXXXXXXXXX"
}
If no addr
is defined, https://cloud.humio.com/
will be used.
It's recommended to configure the address directly in the Terraform provider and the API key using the environment variable.
See examples directory.