dentaku/woodpecker-helm3
1
0
Fork 0
Code Pull requests Releases Activity

Mention the settings/environment equivalency [#8]

Browse source 
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.
This commit is contained in:
Erin Call 2019-12-26 09:41:10 -08:00
parent d4506608d7
commit dc05855aa5
No known key found for this signature in database
GPG key ID: 4071FF6C15B8DAD1
1 changed files with 4 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/parameter_reference.md
View file

@ -1,13 +1,5 @@
# Parameter reference # Parameter reference
## Something here about how to specify non-string types
* boolean
* list\<string\>
* duration
## Mention that everything can be settings or environment
## Global ## Global
| Param name | Type | Purpose | | 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. | | 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. | | 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 ### Formatting non-string values
* Booleans can be yaml's `true` and `false` literals or the strings `"true"` and `"false"`. * Booleans can be yaml's `true` and `false` literals or the strings `"true"` and `"false"`.