Archived
Require provider api_key and remove env var fallback
This commit is contained in:
1 parent
2b0c058664
commit
a317b5f0ce
13 files changed
+22
-30
No files matched your search
@@ -18,7 +18,7 @@ Using a single suffix (`test_suffix`), this example creates five DNS record scen
|
||||
## Prerequisites
|
||||
|
||||
- Local provider binary + Terraform `dev_overrides` for `dynu/dynu`
|
||||
- `DYNU_API_KEY` exported, or `dynu_api_key` set in `terraform.tfvars`
|
||||
- `dynu_api_key` set in `terraform.tfvars`
|
||||
- A Dynu-managed root domain you control
|
||||
|
||||
## Configure
|
||||
|
||||
@@ -1,5 +1,4 @@
|
||||
# Optional if DYNU_API_KEY is exported in your shell.
|
||||
# dynu_api_key = "REPLACE_ME"
|
||||
dynu_api_key = "REPLACE_ME"
|
||||
|
||||
# Required: a Dynu-managed root domain/zone that you control.
|
||||
# Do NOT put an existing production hostname here.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
variable "dynu_api_key" {
|
||||
description = "Dynu API key. Leave null to use DYNU_API_KEY from environment."
|
||||
description = "Dynu API key used by the provider. Set in terraform.tfvars."
|
||||
type = string
|
||||
default = null
|
||||
sensitive = true
|
||||
|
||||
Reference in new issue
Block a user