updating docs and release notes for v1.3.0-rc

Praqma · Jun 12, 2018 · a6a2c9f · a6a2c9f
1 parent 302055a
commit a6a2c9f
Show file tree

Hide file tree

Showing 18 changed files with 20 additions and 22 deletions.
diff --git a/README.md b/README.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0
+version: v1.3.0-rc
 ---
 
 ![helmsman-logo](docs/images/helmsman.png)

diff --git a/docs/desired_state_specification.md b/docs/desired_state_specification.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0
+version: v1.3.0-rc
 ---
 
 # Helmsman desired state specification

diff --git a/docs/how_to/define_namespaces.md b/docs/how_to/define_namespaces.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # define namespaces

diff --git a/docs/how_to/manipulate_apps.md b/docs/how_to/manipulate_apps.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # install releases 

diff --git a/docs/how_to/move_charts_across_namespaces.md b/docs/how_to/move_charts_across_namespaces.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # move charts across namespaces

diff --git a/docs/how_to/multiple_value_files.md b/docs/how_to/multiple_value_files.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # multiple value files

diff --git a/docs/how_to/multitenant_clusters_guide.md b/docs/how_to/multitenant_clusters_guide.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # Multitenant Clusters Guide

diff --git a/docs/how_to/override_defined_namespaces.md b/docs/how_to/override_defined_namespaces.md
@@ -1,5 +1,5 @@
 ---
-version: v1.1.0
+version: v1.3.0-rc
 ---
 
 # Override defined namespaces from command line

diff --git a/docs/how_to/pass_secrets_from_env_variables.md b/docs/how_to/pass_secrets_from_env_variables.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # pass secrets from env. variables:

diff --git a/docs/how_to/protect_namespaces_and_releases.md b/docs/how_to/protect_namespaces_and_releases.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # Namespace and Release Protection 

diff --git a/docs/how_to/run_helmsman_in_ci.md b/docs/how_to/run_helmsman_in_ci.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # Run Helmsman in CI

diff --git a/docs/how_to/run_helmsman_with_hosted_cluster.md b/docs/how_to/run_helmsman_with_hosted_cluster.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 You can manage Helm charts deployment on a hosted K8S cluster in the cloud or on-prem. You need to include the required information to connect to the cluster in your state file. 

diff --git a/docs/how_to/run_helmsman_with_minikube.md b/docs/how_to/run_helmsman_with_minikube.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 You can run Helmsman locally as a binary application with Minikube, you just need to skip all the cluster connection settings in your desired state file. Below is the example.toml desired state file adapted to work with Minikube.

diff --git a/docs/how_to/test_charts.md b/docs/how_to/test_charts.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # test charts

diff --git a/docs/how_to/use_local_charts.md b/docs/how_to/use_local_charts.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # use local helm charts

diff --git a/docs/how_to/use_private_helm_charts.md b/docs/how_to/use_private_helm_charts.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # use private helm charts

diff --git a/docs/how_to/use_the_priority_key.md b/docs/how_to/use_the_priority_key.md
@@ -1,5 +1,5 @@
 ---
-version: v1.2.0-rc
+version: v1.3.0-rc
 ---
 
 # Using the priority key for Apps

diff --git a/release-notes.md b/release-notes.md
@@ -1,6 +1,4 @@
-# v1.2.0
+# v1.3.0-rc
 
-- Stable TLS and multitenancy support.
-- Support for multiple values files when deploying charts.
-- Fix environment variables names issue #35
-- Fix #37
+- Support for using YAML for desired state files.
+- Support for passing values directly through the `set` flag in the desired state file.