refactor: remove canary deployment support

Canary deployments are not being used, so removing all related logic
to simplify the codebase.

Changes:
- Remove removeCanary input parameter and logic from index.js
- Remove special handling for track === 'canary'
- Remove canary test scenarios (canary.sh, canary.sh.snap)
- Update test snapshots to remove removeCanary debug output
- Remove canary deployment documentation from README
- Update description to remove canary deployment mention

Author: genisd

README.md

@@ -6,9 +6,8 @@ Releasing: The `v1` tag gets updated on **master merge**!
 
 # Helm Action
 
-Deploys a helm chart using GitHub actions. Supports canary deployments and
-provides a built in helm chart for apps that listen over http to get your ramped
-up quickly.
+Deploys a helm chart using GitHub actions. Provides a built in helm chart for
+apps that listen over http to get you ramped up quickly.
 
 View an example repository using this action at
 [github.com/deliverybot/example-helm](https://github.com/deliverybot/example-helm).
@@ -33,8 +32,7 @@ payload if the action was triggered by a deployment.
   chart found in this repository. (required)
 - `chart_version`: The version of the helm chart you want to deploy (distinct from app version)
 - `values`: Helm chart values, expected to be a YAML or JSON string.
-- `track`: Track for the deployment. If the track is not "stable" it activates
-  the canary workflow described below.
+- `track`: Track for the deployment (e.g., stable, staging).
 - `task`: Task name. If the task is "remove" it will remove the configured helm
   release.
 - `dry-run`: Helm dry-run option.
@@ -102,43 +100,6 @@ jobs:
         KUBECONFIG_FILE: '${{ secrets.KUBECONFIG }}'
 ```
 
-## Example canary
-
-If a track is chosen that is equal to canary, this updates the helm chart
-in a few ways:
-
-1. Release name is changed to `{release}-{track}` (eg. myapp-canary).
-2. The service is disabled on the helm chart `service.enabled=false`
-3. The ingress is disabled on the helm chart `ingress.enabled=false`
-
-Not enabling the service or ingress allows the stable ingress and service
-resources to pick up the canary pods and route traffic to them.
-
-```yaml
-# .github/workflows/deploy.yml
-name: Deploy
-on: ['deployment']
-
-jobs:
-  deployment:
-    runs-on: 'ubuntu-latest'
-    steps:
-    - uses: actions/checkout@v1
-
-    - name: 'Deploy'
-      uses: 'deliverybot/helm@v1'
-      with:
-        release: 'nginx'
-        track: canary
-        namespace: 'default'
-        chart: 'app'
-        token: '${{ github.token }}'
-        values: |
-          name: foobar
-      env:
-        KUBECONFIG_FILE: '${{ secrets.KUBECONFIG }}'
-```
-
 ## Example pr cleanup
 
 If you are creating an environment per pull request with Helm you may have the

index.js

@@ -206,7 +206,6 @@ async function run() {
     const task = getInput("task");
     const version = getInput("version");
     const valueFiles = getValueFiles(getInput("value_files"));
-    const removeCanary = getInput("remove_canary");
     const helm = getInput("helm") || "helm";
     const timeout = getInput("timeout");
     const repository = getInput("repository");
@@ -235,7 +234,6 @@ async function run() {
     core.debug(`param: version = "${version}"`);
     core.debug(`param: secrets = "${JSON.stringify(secrets)}"`);
     core.debug(`param: valueFiles = "${JSON.stringify(valueFiles)}"`);
-    core.debug(`param: removeCanary = ${removeCanary}`);
     core.debug(`param: timeout = "${timeout}"`);
     core.debug(`param: repository = "${repository}"`);
     core.debug(`param: atomic = "${atomic}"`);
@@ -288,13 +286,6 @@ async function run() {
     valueFiles.forEach((f) => args.push(`--values=${f}`));
     args.push("--values=./values.yml");
 
-    // Special behaviour is triggered if the track is labelled 'canary'. The
-    // service and ingress resources are disabled. Access to the canary
-    // deployments can be routed via the main stable service resource.
-    if (track === "canary") {
-      args.push("--set=service.enabled=false", "--set=ingress.enabled=false");
-    }
-
     // If true upgrade process rolls back changes made in case of failed upgrade.
     if (atomic === true) {
       args.push("--atomic");
@@ -322,14 +313,6 @@ async function run() {
       await exec.exec(helm, ["dependency", "build", chart]);
     }
 
-    // Remove the canary deployment before continuing.
-    if (removeCanary) {
-      core.debug(`removing canary ${appName}-canary`);
-      await exec.exec(helm, deleteCmd(namespace, `${appName}-canary`), {
-        ignoreReturnCode: true,
-      });
-    }
-
     // Actually execute the deployment here.
     if (task === "remove") {
       // delete ttl cronjob in case it was set (it is not required).

tests/scenarios/canary.sh

@@ -15,7 +15,6 @@
 ::debug::param: version = "1234"
 ::debug::param: secrets = "{"secret":"val"}"
 ::debug::param: valueFiles = "[]"
-::debug::param: removeCanary = 
 ::debug::param: timeout = ""
 ::debug::param: repository = ""
 ::debug::param: atomic = "true"

tests/scenarios/canary.sh.snap

@@ -15,7 +15,6 @@
 ::debug::param: version = "1234"
 ::debug::param: secrets = "{"secret":"val"}"
 ::debug::param: valueFiles = "[]"
-::debug::param: removeCanary = 
 ::debug::param: timeout = "30"
 ::debug::param: repository = ""
 ::debug::param: atomic = "true"

tests/scenarios/helm3.sh.snap

@@ -15,7 +15,6 @@
 ::debug::param: version = "1234"
 ::debug::param: secrets = "{"secret":"val"}"
 ::debug::param: valueFiles = "[]"
-::debug::param: removeCanary = 
 ::debug::param: timeout = ""
 ::debug::param: repository = ""
 ::debug::param: atomic = "true"