ky 0.5.2.pre1 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 79b89255c18ce526eae627c708a5bc265777ff53
-  data.tar.gz: 90ec88c86756ae65599f3005b4480e4312bce855
+  metadata.gz: 97fe31308fd5965cb4e060be68510e5d362d2d20
+  data.tar.gz: 10c53d5166e32068af33cb3eff65a9578d03a167
 SHA512:
-  metadata.gz: 7a059e29f0cfc7b31c5873bf662e427abd8f676a697c5a15f3332efc2c9cf01c487b39b5f9eeb3063475975589b8eda2da69464d69b0558345e0335cecacdea5
-  data.tar.gz: 83d2f6d350fec0028d7d3a8804ef316621bb2939eb968a50fc63f9abc607696ca9254d69233dcbbdec19592a51babf811ee7f64f5331a1d41cb4f59ccb17eec6
+  metadata.gz: 7dfce97e1633ec1af9baef516e2fd937c0caf294b1816f792d0eb40d4af5b012f5384d8c77f126d5edf16f51e11db655a1e9b9bdd306fae81ab071f5d2344627
+  data.tar.gz: 85c24fa3ca01a9fba7af99297666cdfe147731ef15ecd8fd141e035df2259138ce9f999dd28ba889ef4ed73e17200b2e7cad9b94458fe556197adbdc4146feb3

data/README.md

@@ -4,10 +4,12 @@
 
 The primary purpose is to automate/DRY up duplication and agreement between multiple deployment YAML files and config/secret yaml files that we saw emerging as we built our kubernetes configuration.
 
-The full/hopeful use of the tool may be enabled with the new `compile` command which is very much a rough draft at present, but which takes a crack at generating a complete deployment yaml file for every line of a Procfile such as used for Heroku, and a pair of config and secrets files.  The secret file can be non-base64 encoded, and compile will generate deployments and a base64 encoded secrets file to a target directory specified.  This command uses all the below commands in combination, one other command not exposed via CLI independently.
+There is a companion gem which relies on/integrates with ky called [kubert](https://github.com/stellaservice/kubert), which share configuration.  KY manages compiling a Procfile, configmaps, secrets and a template into valid kubernetes yaml for various environments and deployment targets, and operates only locally with no network activity.  Kubert adds convenience wrappers for actions interacting with your kubernetes cluster such as opening a console, running a task, deploying and rolling back.
+
+The primary usage of ky at present is the `compile` command which generates a complete deployment yml file for every line of a Procfile such as used for Heroku, and a pair of config and secrets files.  The secret file can be non-base64 encoded, and compile will generate deployments and a base64 encoded secrets file to a target directory specified.  This command uses all the below commands in combination, one other command not exposed via CLI independently.
 
 The command is invoked as:
-`ky compile Procfile.file config.yml secrets.yml output_dir` and the output directory will be created if necessary.  You may pass a namespace to compile which will be reflected in the deployments (and should agree with the config and secrets, though it's not checking they agree at present).  The arguments are all configurable via the configuration file as well, so it can in practice be invoked as `ky compile` or `ky compile --envioronment stg` if you have a configuration file correctly present as described below.
+`ky compile -e {{env}}` assuming you have a .ky file specifying path to Procfile.file, configmap.yml, secrets.yml and output_dir.  You may pass a namespace to compile which will be reflected in the deployments (and should agree with the config and secrets if specified).
 
 Configuration begins with a config file in the project working directory, or in your home directory if you wish to share across several projects.  Unfortunately there are several competing conventions for configuration files, the traditional dot-file configuration convention and newer, more visible Capitalfile configuration.  KY is a lubricant, and has no opinion, and therefore currently supports naming your configuration file `.ky.yml`, `.ky.yaml`, or `Lubefile`.  The default configuration, if this file is not found, is as follows:
 ```

data/examples/.ky.yml

@@ -8,11 +8,18 @@ image_tag: "latest"
 api_version: "extensions/v1beta1"
 inline_config: true
 inline_secret: false
-project_name: "connect"
+project_name: "my-project"
 config_path: "spec/support/config.yml"
 secret_path: "spec/support/decoded.yml"
 output_dir: "namespaces"
 procfile_path: "spec/support/Procfile"
+kubert:
+  contexts:
+    staging: staging.example.com
+    prod: production.example.com
+  excluded_deployments: [sanitize, migration]
+  default_environment: stg
+  task_pod: console
 merge:
   web:
     spec:

data/lib/ky/version.rb

@@ -1,3 +1,3 @@
 module KY
-  VERSION = "0.5.2.pre1"
+  VERSION = "0.6.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: ky
 version: !ruby/object:Gem::Version
-  version: 0.5.2.pre1
+  version: 0.6.0
 platform: ruby
 authors:
 - Brian Glusman
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2017-03-27 00:00:00.000000000 Z
+date: 2017-03-28 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -167,9 +167,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: ky
 rubygems_version: 2.6.8