profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/iennae/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

berkshelf/berkshelf 1088

A Chef Cookbook manager

cncf/tag-contributor-strategy 50

CNCF Technical Advisory Group on Contributor Strategy -- maintainer relations, building up contributors, governance, graduation, and more.

dapr/community 29

Governance and community material for Dapr and its open source sub-projects

cncf/project-template 11

CNCF Project Template

arschles/advent2020 1

Solutions to Advent of Code 2020, probably in Go

eeyun/crc_chefconf 0

Development repo for building the crc_chefconf workstations

push eventCoffeeOps/coffeeops.github.io

abangser

commit sha 066f043d2a05c7dc1beeeec5d694374e3c2b37b0

Update schedule for London Since Covid we have moved to online and to twice a month.

view details

Jennifer Davis

commit sha 1e3704f39f3546531740d88d5834fc79929cec3e

Merge pull request #47 from abangser/patch-1 Update schedule for London

view details

push time in 3 days

PR merged CoffeeOps/coffeeops.github.io

Update schedule for London

Since Covid we have moved to online and to twice a month.

+5 -2

2 comments

1 changed file

abangser

pr closed time in 3 days

pull request commentGoogleCloudPlatform/nodejs-docs-samples

feat: add functions/esm sample

Hey, thanks everyone. Just adding the flag back so we are clear to not merge currently.

We appreciate the sample Grant. Serverless DPE will do the same due diligence as with all external sample requests. We'll get back to you after we review with the team on next steps.

grant

comment created time in 17 days

Pull request review commentgoogle-github-actions/setup-gcloud

lingering org transition cleanup

 /*- * Copyright 2020 Google LLC+ * Copyright 2019 Google LLC

why this change? seems weird.

tequilarista

comment created time in 22 days

PullRequestReviewEvent

issue closedgoogle-github-actions/setup-gcloud

Why is no official link to Google / GCP?

Question

I ran into Github Actions for one of our Open Source projects and saw this google-github-actions organization in various tutorials. But it took me some minutes to find out if this is an official organisation run by Google, or not. You should provide additional information in the repositories (e.g. "Github action for App Engine, provided by Google") and update this organization's metadata / links. At least some public members could increase the trust, too.

Current State

grafik

Google's Organization

grafik

closed time in 22 days

botic

issue commentgoogle-github-actions/setup-gcloud

Why is no official link to Google / GCP?

Thanks for reaching out! As of today we're verified. Screen Shot 2021-07-14 at 7 41 16 PM

botic

comment created time in 22 days

PullRequestReviewEvent
PullRequestReviewEvent

push eventCoffeeOps/coffeeops_site

rrxtns

commit sha 7c1abaa999d467a0e973e6c2609f61f694268334

updating Seattle and PDX

view details

Jennifer Davis

commit sha 41295b49687466a1f01a02808a70aac9692d80fb

Merge pull request #1 from sntxrr/update-seattle updating Seattle and PDX

view details

push time in 2 months

PR merged CoffeeOps/coffeeops_site

updating Seattle and PDX
  • updating Seattle Organizer
  • updating Meetup URL
  • adding Seattle Twitter
  • correcting PDX Twitter
+6 -3

0 comment

1 changed file

sntxrr

pr closed time in 2 months

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.+Even more powerful, the value of the parameters can come from the following sources:++* hard-coded value+* environment variable+* file+* command output+* secret++Some parameters may be sensitive, for example a database connection string or oauth token.+For improved security, and to limit exposure of sensitive values, it is recommended that you source those parameter values from a secret store such as Hashicorp Vault or Azure Key Vault.++Create a parameter set for the hello-llama with the `porter parameters generate` command. It is an interactive command that walks through setting values for every parameter in the specified bundle.++```console+$ porter parameters generate hello-llama --reference getporter/hello-llama:v0.1.1+Generating new parameter set hello-llama from bundle hello-llama+==> 2 parameters declared for bundle hello-llama++? How would you like to set parameter "name"+   [Use arrows to move, space to select, type to filter]+  secret+> specific value+  environment variable+  file path+  shell command++? Enter the value that will be used to set parameter "name"+  Porter+```+

Cool, wasn't saying that these things need to defined here but wondering if folks have more questions if they were answered somewhere.

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.+Even more powerful, the value of the parameters can come from the following sources:++* hard-coded value+* environment variable+* file+* command output+* secret++Some parameters may be sensitive, for example a database connection string or oauth token.+For improved security, and to limit exposure of sensitive values, it is recommended that you source those parameter values from a secret store such as Hashicorp Vault or Azure Key Vault.

AHHH. just cut the Google Secret Manager out and keep the "sensitive parameter values" (instead of those)

carolynvs

comment created time in 2 months

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.

Ahhhhhh! The output is confusing which is why I'm lost. so I think there is more nuance here and I'll need to chat to you more about it because optional feels like the wrong word

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.+Even more powerful, the value of the parameters can come from the following sources:++* hard-coded value+* environment variable+* file+* command output+* secret++Some parameters may be sensitive, for example a database connection string or oauth token.+For improved security, and to limit exposure of sensitive values, it is recommended that you source those parameter values from a secret store such as Hashicorp Vault or Azure Key Vault.++Create a parameter set for the hello-llama with the `porter parameters generate` command. It is an interactive command that walks through setting values for every parameter in the specified bundle.++```console+$ porter parameters generate hello-llama --reference getporter/hello-llama:v0.1.1+Generating new parameter set hello-llama from bundle hello-llama+==> 2 parameters declared for bundle hello-llama++? How would you like to set parameter "name"+   [Use arrows to move, space to select, type to filter]+  secret+> specific value+  environment variable+  file path+  shell command++? Enter the value that will be used to set parameter "name"+  Porter+```+

Can there only be one parameter set per bundle? What happens if I re-run generate?

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.+Even more powerful, the value of the parameters can come from the following sources:++* hard-coded value+* environment variable+* file+* command output+* secret++Some parameters may be sensitive, for example a database connection string or oauth token.+For improved security, and to limit exposure of sensitive values, it is recommended that you source those parameter values from a secret store such as Hashicorp Vault or Azure Key Vault.++Create a parameter set for the hello-llama with the `porter parameters generate` command. It is an interactive command that walks through setting values for every parameter in the specified bundle.++```console+$ porter parameters generate hello-llama --reference getporter/hello-llama:v0.1.1+Generating new parameter set hello-llama from bundle hello-llama+==> 2 parameters declared for bundle hello-llama++? How would you like to set parameter "name"+   [Use arrows to move, space to select, type to filter]+  secret+> specific value+  environment variable+  file path+  shell command++? Enter the value that will be used to set parameter "name"+  Porter+```+

What if I want to accept a default value for a particular parameter?

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.+Even more powerful, the value of the parameters can come from the following sources:++* hard-coded value+* environment variable+* file+* command output+* secret++Some parameters may be sensitive, for example a database connection string or oauth token.+For improved security, and to limit exposure of sensitive values, it is recommended that you source those parameter values from a secret store such as Hashicorp Vault or Azure Key Vault.

For improved security, and to limit exposure of sensitive values, it is recommended that you source sensitive parameter values from a secret store such as HashiCorp Vault, Azure Key Vault or Google Secret Manager.

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.+Even more powerful, the value of the parameters can come from the following sources:

more powerful than what?

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.+When working with a bundle often though, remembering and typing out every parameter values every time is error prone.+Parameter Sets store a set of parameter values to use with a bundle.

To alleviate errors and the requirement of remembering and manually configuring parameters at the command line, you can store a set of parameter values to use with a bundle with a parameter set.

carolynvs

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentgetporter/porter

QuickStart: Parameters

+---+title: "QuickStart: Parameters"+descriptions: Learn how to use a bundle with parameters+layout: single+---++Now that you know how to install a bundle, let's look at how to specify parameters to customize how that bundle is installed.+Bundles can define parameters to allow the end-user to tweak how the bundle is configured.+A parameter can be a string, integer, boolean or even a json object.+Some examples of how parameters can be used in a bundle are:++* Log Level: Default the log level for an application to info. At any time a user can upgrade the bundle to change that parameter to a different value.+* Deployment Region: Let the user specify which region, such as eastus-1, where the application should be deployed.+* Helm Release Name: A bundle that uses Helm often will define a parameter that allows the user to set the release name for the Helm release.++For optional parameters, bundles set a default value that is used when the user does not specify a value for the parameter.++Let's look at a bundle with parameters:++```console+$ porter explain --reference getporter/hello-llama:v0.1.1+Name: hello-llama+Description: An example Porter bundle with parameters+Version: 0.1.0+Porter Version: v0.38.1-32-gb76f5c1c++No credentials defined++Parameters:+Name   Description                           Type     Default   Required   Applies To+name   Name of to whom we should say hello   string   llama     false      All Actions++No outputs defined++No custom actions defined++No dependencies defined+```++The output tells us that the bundle has one optional string parameter, name, which defaults to "llama".+The name parameter applies to "All Actions" meaning that this parameter can be specified with every action that the bundle defines.+Since it says that no custom actions are defined, the bundle only supports the built-in actions of install, upgrade, and uninstall.++## Use the default parameter values+++First install the bundle and do not specify any parameters so that you can observe how the bundle installs without any customization.++```console+$ porter install hello-llama --reference getporter/hello-llama:v0.1.1+installing hello-llama...+executing install action from hello-llama (installation: hello-llama)+Hello, llama+execution completed successfully!+```++The bundle printed "Hello, llama" using the default value for the name parameter.++## Specify a parameter with a flag+Next upgrade the installation and change the name parameter to another value.+Parameters are specified with the \--param flag: ++```console+$ porter upgrade hello-llama --param name=Porter+upgrading hello-llama...+executing upgrade action from hello-llama (installation: hello-llama)+Porter 2.0+execution completed successfully!+```++## Create a Parameter Set+Setting a parameter value individually on the command line with the \--param flag works well when trying out a bundle.

While trying out a bundle, it might work well when you set individual parameter values on the command line with the --param flag.

carolynvs

comment created time in 2 months