From cf60fb282443178c682c34a88a90387ab53277fe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E2=80=9Cadnan=E2=80=9D?= Date: Thu, 7 Oct 2021 18:43:58 -0400 Subject: [PATCH] to squash: address wording issues MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: “adnan” --- docs/content/parameters.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/content/parameters.md b/docs/content/parameters.md index fb1b32b9a..c909f29cf 100644 --- a/docs/content/parameters.md +++ b/docs/content/parameters.md @@ -5,19 +5,19 @@ aliases: - /how-parameters-work/ --- -When you are authoring a bundle, you can define what parameters your bundle -requires such as username and password values for a backing database, or the -region that a certain resource should be deployed in, etc. Then in your -action's steps you can reference the parameters using porter's template -language `{{ bundle.parameters.db_name }}`. +When you are authoring a bundle, you can define parameters that are required by +your bundle. These parameters are restricted to a list of [allowable data +types](/author-bundles/#parameters) and are used to define parameters such as +username and password values for a backing database, or the region that a +certain resource should be deployed in, etc. Then in your action's steps you can +reference the parameters using porter's template language `{{ +bundle.parameters.db_name }}`. Parameter values are resolved from a combination of supplied parameter set files, user-specified overrides and defaults defined by the bundle itself. The resolved values are added to a claim receipt, which is passed in to the bundle execution environment, e.g. the docker container, when the bundle -action is executed (install/upgrade/uninstall/invoke). Parameters are restricted -to a list of [allowable data -types](https://porter.sh/author-bundles/#parameters). +action is executed (install/upgrade/uninstall/invoke). ## Parameter Sets