From dc05855aa5c79fd530b1c064210ee9fc6b14fcb0 Mon Sep 17 00:00:00 2001 From: Erin Call Date: Thu, 26 Dec 2019 09:41:10 -0800 Subject: [PATCH] Mention the `settings`/`environment` equivalency [#8] It seems like this needs more information, like why you'd want to put something in one stanza or the other, but I don't really know enough about drone to give useful advice. --- docs/parameter_reference.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/parameter_reference.md b/docs/parameter_reference.md index 288bd53..ba492ed 100644 --- a/docs/parameter_reference.md +++ b/docs/parameter_reference.md @@ -1,13 +1,5 @@ # Parameter reference -## Something here about how to specify non-string types - -* boolean -* list\ -* duration - -## Mention that everything can be settings or environment - ## Global | Param name | Type | Purpose | |---------------------|-----------------|---------| @@ -67,6 +59,10 @@ Uninstallations are triggered when the `helm_command` setting is "uninstall" or | timeout | duration | | Timeout for any *individual* Kubernetes operation. The uninstallation's full runtime may exceed this duration. | | skip_tls_verify | boolean | | Connect to the Kubernetes cluster without checking for a valid TLS certificate. Not recommended in production. | +### Where to put settings + +Any setting (with the exception of `prefix`; [see below](#user-content-using-the-prefix-setting)), can go in either the `settings` or `environment` section. + ### Formatting non-string values * Booleans can be yaml's `true` and `false` literals or the strings `"true"` and `"false"`.