preparing new release

Praqma · Jan 2, 2020 · ca51a02 · ca51a02
1 parent 90195a2
commit ca51a02
Show file tree

Hide file tree

Showing 19 changed files with 25 additions and 25 deletions.
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-[![GitHub version](https://d25lcipzij17d.cloudfront.net/badge.svg?id=gh&type=6&v=v3.0.0-beta4&x2=0)](https://github.com/Praqma/helmsman/releases) [![CircleCI](https://circleci.com/gh/Praqma/helmsman/tree/master.svg?style=svg)](https://circleci.com/gh/Praqma/helmsman/tree/master)
+[![GitHub version](https://d25lcipzij17d.cloudfront.net/badge.svg?id=gh&type=6&v=v3.0.0-beta5&x2=0)](https://github.com/Praqma/helmsman/releases) [![CircleCI](https://circleci.com/gh/Praqma/helmsman/tree/master.svg?style=svg)](https://circleci.com/gh/Praqma/helmsman/tree/master)
 
 ![helmsman-logo](docs/images/helmsman.png)
 
@@ -61,9 +61,9 @@ If you use private helm repos, you will need either `helm-gcs` or `helm-s3` plug
 Check the [releases page](https://github.com/Praqma/Helmsman/releases) for the different versions.
 ```
 # on Linux
-curl -L https://github.com/Praqma/helmsman/releases/download/v3.0.0-beta4/helmsman_3.0.0-beta4_linux_amd64.tar.gz | tar zx
+curl -L https://github.com/Praqma/helmsman/releases/download/v3.0.0-beta5/helmsman_3.0.0-beta5_linux_amd64.tar.gz | tar zx
 # on MacOS
-curl -L https://github.com/Praqma/helmsman/releases/download/v3.0.0-beta4/helmsman_3.0.0-beta4_darwin_amd64.tar.gz | tar zx
+curl -L https://github.com/Praqma/helmsman/releases/download/v3.0.0-beta5/helmsman_3.0.0-beta5_darwin_amd64.tar.gz | tar zx
 
 mv helmsman /usr/local/bin/helmsman
 ```

diff --git a/docs/best_practice.md b/docs/best_practice.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Best Practice

diff --git a/docs/cmd_reference.md b/docs/cmd_reference.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # CMD reference

diff --git a/docs/deployment_strategies.md b/docs/deployment_strategies.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Deployment Strategies
@@ -135,7 +135,7 @@ If you need supporting applications (charts) for your application (e.g, reverse
 
 ## Notes on using multiple Helmsman desired state files for the same cluster
 
-Helmsman v3.0.0-beta4 introduces the `context` stanza.
+Helmsman v3.0.0-beta5 introduces the `context` stanza.
 When having multiple DSFs operating on different releases, it is essential to use the `context` stanza in each DSF to define what context the DSF covers. The user-provided value for `context` is used by Helmsman to label and distinguish which DSF manages which deployed releases in the cluster. This way, each helmsman operation will only operate on releases within the context defined in the DSF.
 
 When having multiple DSFs be aware of the following:

diff --git a/docs/desired_state_specification.md b/docs/desired_state_specification.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Helmsman desired state specification

diff --git a/docs/how_to/apps/basic.md b/docs/how_to/apps/basic.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Install releases

diff --git a/docs/how_to/apps/destroy.md b/docs/how_to/apps/destroy.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Delete all deployed releases

diff --git a/docs/how_to/apps/helm_tests.md b/docs/how_to/apps/helm_tests.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Test charts

diff --git a/docs/how_to/apps/moving_across_namespaces.md b/docs/how_to/apps/moving_across_namespaces.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Move charts across namespaces

diff --git a/docs/how_to/apps/order.md b/docs/how_to/apps/order.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Using the priority key for Apps

diff --git a/docs/how_to/apps/override_namespaces.md b/docs/how_to/apps/override_namespaces.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Override defined namespaces from command line

diff --git a/docs/how_to/apps/secrets.md b/docs/how_to/apps/secrets.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Passing secrets from env variables:

diff --git a/docs/how_to/deployments/ci.md b/docs/how_to/deployments/ci.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Run Helmsman in CI
@@ -13,7 +13,7 @@ jobs:
 
     deploy-apps:
       docker:
-        - image: praqma/helmsman:v3.0.0-beta4
+        - image: praqma/helmsman:v3.0.0-beta5
       steps:
         - checkout
         - run:

diff --git a/docs/how_to/helm_repos/default.md b/docs/how_to/helm_repos/default.md
@@ -1,10 +1,10 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Default helm repos
 
-Helm v3 no longer adds the `stable` and `incubator` repos by default. However, Helmsman v3.0.0-beta4 still adds these two repos by default. These two DO NOT need to be defined explicitly in your desired state file (DSF). However, if you would like to configure some repo with the name stable for example, you can override the default repo.
+Helm v3 no longer adds the `stable` and `incubator` repos by default. However, Helmsman v3.0.0-beta5 still adds these two repos by default. These two DO NOT need to be defined explicitly in your desired state file (DSF). However, if you would like to configure some repo with the name stable for example, you can override the default repo.
 
 > You can disable the automatic addition of these two repos, use the `--no-default-repos` flag.
 

diff --git a/docs/how_to/misc/merge_desired_state_files.md b/docs/how_to/misc/merge_desired_state_files.md
@@ -1,5 +1,5 @@
 ---
-version: v3.0.0-beta4
+version: v3.0.0-beta5
 ---
 
 # Supply multiple desired state files
@@ -47,7 +47,7 @@ $ helmsman -f common.toml -f nonprod.toml ...
 
 When using multiple DSFs -and since Helmsman doesn't maintain any external state-, it has been possible for operations from one DSF to cause problems to releases deployed by other DSFs. A typical example is that releases deployed by other DSFs are considered `untracked` and get scheduled for deleting. Workarounds existed (e.g. using the `--keep-untracked-releases`, `--target` and `--group` flags).
 
-Starting from Helmsman v3.0.0-beta4, `context` is introduced to define the context in which a DSF is used. This context is used as the ID of that specific DSF and must be unique across the used DSFs. The context is then used to label the different releases to link them to the DSF they were first deployed from. These labels are then checked by Helmsman on each run to make sure operations are limited to releases from a specific context.
+Starting from Helmsman v3.0.0-beta5, `context` is introduced to define the context in which a DSF is used. This context is used as the ID of that specific DSF and must be unique across the used DSFs. The context is then used to label the different releases to link them to the DSF they were first deployed from. These labels are then checked by Helmsman on each run to make sure operations are limited to releases from a specific context.
 
 Here is how it is used:
 

diff --git a/examples/example.toml b/examples/example.toml
@@ -1,4 +1,4 @@
-# version: v3.0.0-beta4
+# version: v3.0.0-beta5
 
 # context defines the context of this Desired State File.
 # It is used to allow Helmsman identify which releases are managed by which DSF.

diff --git a/examples/example.yaml b/examples/example.yaml
@@ -1,4 +1,4 @@
-# version: v3.0.0-beta4
+# version: v3.0.0-beta5
 # metadata -- add as many key/value pairs as you want
 metadata:
   org: "example.com/$ORG_PATH/"

diff --git a/internal/app/main.go b/internal/app/main.go
@@ -6,7 +6,7 @@ import (
 
 const (
 	helmBin            = "helm"
-	appVersion         = "v3.0.0-beta4"
+	appVersion         = "v3.0.0-beta5"
 	tempFilesDir       = ".helmsman-tmp"
 	stableHelmRepo     = "https://kubernetes-charts.storage.googleapis.com"
 	incubatorHelmRepo  = "http://storage.googleapis.com/kubernetes-charts-incubator"

diff --git a/release-notes.md b/release-notes.md
@@ -1,4 +1,4 @@
-# v3.0.0-beta4
+# v3.0.0-beta5
 
 This is a major release to support Helm v3.
 It is recommended you read the [Helm 3 migration guide](https://helm.sh/docs/topics/v2_v3_migration/) before using this release.