Added support for direct helm variables (#116)

* Added support for direct helm variables
* Upgraded all upgradable dependencies
* Updated action inputs for the direct helm variable prefix
* Updated documentation for direct helm variable usage
* Added support for multi-chart direct helm variables

Author: sudiptosarkar

README.md

@@ -108,6 +108,26 @@ For complex values, you'd want to not use the helm set variable from the command
 { "key": "db.config", "value": "{ \"host\": \"db.example.com\", \"port\": 5432, \"username\": \"postgres\", \"password\": \"mysecretpassword\" }", "useFile": true, "chart": "auth-service" }
 ```
 
+## Direct Variables
+
+There may be situations where you'd want to pass direct helm variables, and set their values. For those, we can use the Github variables with a special prefix. For example, if the prefix is `HELMVAR`, the variable name will need to start with `DEPLOYMENT_<prefix>[_<environment>]_HELMVAR_`. An example value can be:
+
+```json
+{ "key": "ingress.tls[0].hosts[0]", "value": "my-svc.example.com", "chart": "common-config" }
+```
+
+This will be passed as `--set ingress.tls[0].hosts[0]=my-svc.example.com` in the Helm command during deployment.
+
+## Global Direct variables
+
+To support situations where the same direct variable needs to be passed to multiple (all) charts, the chart key is optional. This is only the case for direct helm variables, as opposed to configmaps and secrets, which might create confusion if the keys are the same across multiple configmaps and secrets. For direct variables on the other hand, if the chart key is not provided, the variable will be passed to all Helm charts during deployment.
+
+For example:
+
+```json
+{ "key": "baseSubdomain", "value": "prod-us-east1.example.com" }
+```
+
 ## Example Action
 
 The following example action will deploy the `auth-service` Helm chart.

action.yml

@@ -14,6 +14,9 @@ inputs:
     description: "The Helm Deployment name that is to be deployed. Needed if the chart name and the deployment name need to be different"
   githubSecretVariablePrefix:
     description: "The Github Secret/Variable Prefix to be parsed for deployment"
+  directVariablePrefix:
+    description: "The Github Variable Prefix to be parsed for deployment as a direct helm variable. This will be used to infer direct variables for all the variables that have the key `DEPLOYMENT_<prefix>[_<environment>]_<directVariablePrefix>_<githubKeyName>`. The default value is `HELMVAR`."
+    default: "HELMVAR"
   deploymentEnvironment:
     description: "The name of the Runtime environment. E.g. DEV, TEST, STAGING, UAT, PROD etc. Needs to match the context name in the Kube Config. Will default to the `current-context` in the Kube Config file for deployment. If provided, will be used in conjunction with the Github Secret/Variable Prefix. Only secrets or variables prefixed with `DEPLOYMENT_<prefix>[_<environment>]_<githubKeyName>` will be used"
   namespace:
@@ -83,6 +86,7 @@ runs:
         GITHUB_VARIABLES: ${{ inputs.variables }}
         ENVIRONMENT_VARIABLES: ${{ inputs.environmentVariables }}
         GITHUB_SECRET_VARIABLE_PREFIX: ${{ inputs.githubSecretVariablePrefix }}
+        DIRECT_VARIABLE_PREFIX: ${{ inputs.directVariablePrefix }}
         DEPLOYMENT_ENVIRONMENT: ${{ inputs.deploymentEnvironment }}
         TAG: ${{ inputs.tag }}
         HELM_CONFIG_MAP_VARIABLE_NAME: ${{ inputs.helmConfigMapVariableName }}