docker-api
captn3m0/docker-api/ignition
terraform-ignition-docker-api  Terraform Configuration using the Ignition Provider to setup a Docker API endpoint. This generates the certs, and returns them as output. This is based on the official [CoreOS documentation][docs]. You can see the inputs and outputs at the Terraform Registry or MODULE.md. Usage ``hcl module "ignition" { source = "captn3m0/docker-api/ignition" version = "1.0.4" ca_subject = { common_name = "ca.docker" } client_subject = { common_name = "client.docker" } server_subject = { common_name = "docker-server" } } // The return value from this is a userdata blob, so you can either // upload it to S3 and then append the S3 URL to your userdata, like: resource "aws_s3_bucket_object" "s3" { key = "docker.json" bucket =
| Name | Type | Description | Default |
|---|---|---|---|
| server_subject | map | The subject block for the server certificate. This should be the hostname of the | |
| client_subject | map | The subject block for the Client certificate. See https://www.terraform.io/docs/ | |
| ca_subject | map | The subject block for the CA certificate. See https://www.terraform.io/docs/prov | |
| cert_path | string | path to write the client config to | "" |
| validity | string | certificate validity in days, defaults to 365 | 365 |
config — Rendered ignition configuration. Can be used in a append block, or passed as userdataca-cert — PEM encoded CA Certificate, used for signing both the server and the client certsclient-cert — PEM encoded client certificate, used to authenticate to the serverclient-key — PEM encoded client key, used to authenticate to the serversource — Ready data-uri based source to inser into a append or replace blockverification — Verification hash for the userdata