kubes 0.6.5 → 0.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a5e335602466257bfe7751577e3544f5fcdf73e221e5791fd142275295eea548
-  data.tar.gz: 9172b806b49193341a4399adfd5c9372b1a02437f6bbd3395632a2c81ddebac0
+  metadata.gz: f5e5ce606ff32f7d8083b1c8d6bdff1745700ec971ce7bc0a13a72b5ab370e2a
+  data.tar.gz: 2ff9e9cee9c77e227157ffd701504baf4831b2ed66678db7a7b5248303bc02cb
 SHA512:
-  metadata.gz: 83a7bc9cc35989a17b2960a7a931295d767f2454006eb696b476fed193a7973066a51a4f0e7309bea99b1fdebca71482ee646ab122820c6ae9e5570edb5cc367
-  data.tar.gz: d7baee331717cdab66b8dbf028c97fbc9c3e973a87a9497fdeccd5f1195a8af06193586b8075f4b29ea94910b7d55c12d35d07234391596c76be83da1081e294
+  metadata.gz: 5af79490b1ce56d61a08fcbd2d4c05d442d0b965a030c9ef3a95b74b8276a368065b9d3d340344920e2b5a38e77161be904b11755c55a17e351ce04b891f7725
+  data.tar.gz: cd83c382860483bbbb9c3a4d462def4e8551dc80a8453d171918190bcd82f9cdd4bef351cbaa1a8222cd1dd3ad6e53d128d279a23cee03636142104b6b923192

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,7 @@
+Please fill out one of the templates on https://github.com/boltops-tools/kubes/issues/new/choose
+
+If you want to ask a question please do so on sites like StackOverflow.
+
+To be sensitive to everyone's time, we may close issues asking questions without comment. Here are some additional options also https://kubes.guru/support/ 👌
+
+Thank you!

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,84 @@
+---
+name: Reproducible Bug Report
+about: Is something not working as expected?
+title: ''
+labels: 'bug'
+assignees: ''
+
+---
+
+<!--
+Hi! Thanks for considering to file a bug with Kubes. Please take the time to
+answer the basic questions. Please try to be as detailed as possible.
+To be sensitive to everyone's time, if not enough details are provided, the
+issue may be closed without comment. If you repeatedly fail to provide enough
+details, you may be blocked from ever submitting issues to Kubes again.
+Please use your best judgment. 👍
+
+If you are unsure this is a bug in Kubes, please consider asking your question at sites like StackOverflow.
+
+Thanks!
+-->
+
+## Checklist
+
+<!--
+Make sure that you've done all of these.  To mark a checkbox done, replace [ ] with [x]. Or after you create the issue you can click the checkbox.
+-->
+
+- [ ] Upgrade Kubes: Are you using the latest version of Kubes? This allows Kubes to fix issues fast.
+- [ ] Reproducibility: Are you reporting a bug others will be able to reproduce and not asking a question. If you're unsure or want to ask a question, do so on StackOverflow.
+- [ ] Code sample: Have you put together a code sample to reproduce the issue and make it available?  Code samples help speed up fixes dramatically. If it's an easily reproducible issue, then code samples are not needed. If you're unsure, please include a code sample.
+
+## My Environment
+
+<!-- Please fill out the table below with debugging info to help: -->
+
+| Software         | Version |
+| ---------------- | ------- |
+| Operating System |         |
+| Kubes            |         |
+| kubectl          |         |
+| Ruby             |         |
+
+---
+
+## Expected Behaviour
+
+<!--
+What is it you expected to happen? This should be a description of how the functionality you tried to use is supposed to work. Try to keep this to one-paragraph.
+-->
+
+## Current Behavior
+
+<!--
+Describe the details of the bug.  Try to keep this to one-paragraph.
+-->
+
+## Step-by-step reproduction instructions
+
+<!--
+Be sure to include any steps you took for the problem to exist. This is likely the longest part of the report.
+
+Please include any logs you think relevant here. If the logs are long (more than 50 lines) please make a gist of the logs and link to it. https://gist.github.com
+
+With long logs, you can also use the <details> tag to keep the report readable. Example:
+
+<details>
+ <summary>Summary Goes Here</summary>
+
+ ...this is hidden, collapsable content. start with a blank line to get terminal output to format right...
+</details>
+-->
+
+## Code Sample
+
+<!--
+Please provide a code repository, gist, code snippet or sample files to reproduce the issue.
+-->
+
+## Solution Suggestion
+
+<!--
+Please provide possible solutions. If you can't think of anything, feel free to omit. Please be kind and add helpful possible solutions.  For example, "Fix it!" is not a helpful solution suggestion. We are mere mortals. Please be constructive.
+-->

data/.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,12 @@
+---
+name: Documentation
+about: Found a typo or something that isn't crystal clear in the docs?
+title: ''
+labels: docs
+assignees: ''
+
+---
+
+The Kubes Docs are in the [kubes repo](https://github.com/boltops-tools/kubes/tree/master/docs). Please submit a PR there. Thanks!
+
+For documentation changes to the kubes code base itself, like code comments. Please submit a PR here. Thanks!

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,64 @@
+---
+name: New Feature Suggestion
+about: Want to add a feature to Kubes?
+title: ''
+labels: feature
+assignees: ''
+
+---
+
+<!--
+Hi! Thanks for considering to file a feature request with Kubes. Please take the time to answer the basic questions. Please try to be as detailed as possible.
+
+Thanks!
+-->
+
+## Summary
+
+<!--
+A one-paragraph explanation of the feature.
+-->
+
+## Motivation
+
+<!--
+Why do you want to see this feature in Kubes? What use cases does it support?
+
+How the feature would be relevant to 80% or more of Kubes users.
+-->
+
+## Guide-level explanation
+
+<!--
+Explain the proposal as if it was already included in the project and you were teaching it to another programmer. That generally means:
+
+- Introducing new named concepts.
+- Explaining the feature largely in terms of examples.
+- If applicable, provide sample error messages, deprecation warnings, or upgrade guidance.
+
+If this is a small feature, you may omit this section.
+-->
+
+## Reference-level explanation
+
+<!--
+This is the technical portion of the feature request. Explain the design in sufficient detail that:
+
+- Its interaction with other features is clear.
+- It is reasonably clear how the feature would be implemented.
+- Corner cases are dissected by example.
+
+If you do not know how to answer this, you can omit it. No worries!
+-->
+
+## Drawbacks
+
+<!--
+Why should we *not* do this?
+-->
+
+## Unresolved Questions
+
+<!--
+What related issues do you consider out of scope for this feature that could be addressed in the future independently of the solution that comes out of this feature?
+-->

data/.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,14 @@
+---
+name: Question
+about: Have any questions about how Kubes works?
+title: ''
+labels: 'question'
+assignees: ''
+
+---
+
+The Kubes issue tracker IS NOT for usage questions! Please post your question at sites like StackOverflow.
+
+To be sensitive to everyone's time, we may close issues asking questions without comment. If you repeatedly post questions in the issues tracker, you may be blocked from ever submitting issues to Kubes again. Please use your best judgment. 👍
+
+Here are some additional options also https://kubes.guru/support/ 😁

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,50 @@
+<!--
+Thanks for creating a Pull Request! Before you submit, please make sure you've done the following:
+
+- I read the contributing document at https://kubes.guru/docs/contributing/
+-->
+
+<!--
+Make our lives easier! Choose one of the following by uncommenting it:
+-->
+
+<!-- This is a 🐞 bug fix. -->
+<!-- This is a 🙋‍♂️ feature or enhancement. -->
+<!-- This is a 🧐 documentation change. -->
+
+<!--
+Before you submit this pull request, make sure to have a look at the following checklist. To mark a checkbox done, replace [ ] with [x]. Or after you create the issue you can click the checkbox.
+
+If you don't know how to do some of these, that's fine!  Submit your pull request and we will help you out on the way.
+-->
+
+- [ ] I've added tests (if it's a bug, feature or enhancement)
+- [ ] I've adjusted the documentation (if it's a feature or enhancement)
+- [ ] The test suite passes (run `bundle exec rspec` to verify this)
+
+## Summary
+
+<!--
+Provide a description of what your pull request changes.
+-->
+
+## Context
+
+<!--
+Is this related to any GitHub issue(s) or another relevant link?
+-->
+
+## How to Test
+
+<!--
+Please provide instructions on how to test the fix. This speeds up reviewing the PR. If testing requires a demo Kubes project, please provide an example repo.
+-->
+
+
+## Version Changes
+
+<!--
+Which semantic version change would you recommend?
+If you don't know, feel free to omit it.
+-->
+

data/CHANGELOG.md

@@ -3,6 +3,22 @@
 All notable changes to this project will be documented in this file.
 This project *loosely tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
 
+## [0.7.1] - 2020-11-16
+- [#42](https://github.com/boltops-tools/kubes/pull/42) load helpers for dsl properly
+- fix merge layer
+
+## [0.7.0] - 2020-11-16
+- [#41](https://github.com/boltops-tools/kubes/pull/41) multiple resources yaml support
+
+## [0.6.8] - 2020-11-14
+- [#40](https://github.com/boltops-tools/kubes/pull/40) fix version check
+
+## [0.6.7] - 2020-11-12
+- dependencies version bump: kubes_google
+
+## [0.6.6] - 2020-11-12
+- dependencies version bump: kubes_aws and kubes_google
+
 ## [0.6.5] - 2020-11-12
 - [#39](https://github.com/boltops-tools/kubes/pull/39) google secrets fetcher option
 

data/docs/_docs/dsl/multiple-resources.md

@@ -1,14 +1,13 @@
 ---
-title: Multiple Resources
+title: DSL Multiple Resources
 ---
 
 Kubes encourages a structure with files that matches the resource kind. Example:
 
-    .kubes
-    └── resources
-        └── web
-            ├── deployment.rb
-            └── service.rb
+    .kubes/resources
+    └── web
+        ├── deployment.rb
+        └── service.rb
 
 This structure is nicely organized and covers 80% of use cases. An astute user may point out that this struture assumes one resource of each kind.
 
@@ -18,13 +17,12 @@ Next, we'll cover different ways to create multiple resource of the same kinds.
 
 You can create multiple resources of same kind by appending a dash followed by anything. Example:
 
-    .kubes
-    └── resources
-        └── web
-            ├── deployment-1.rb
-            ├── deployment-2.rb
-            ├── service-1.rb
-            └── service-2.rb
+    .kubes/resources
+    └── web
+        ├── deployment-1.rb
+        ├── deployment-2.rb
+        ├── service-1.rb
+        └── service-2.rb
 
 Only words before the dash are used to infer the resource kind.
 
@@ -35,7 +33,7 @@ deployment-2.rb | Deployment
 service-1.rb | Service
 service-2.rb | Service
 
-Using multiple files is the general recommended approach.
+Using multiple files is the general recommended approach when using the DSL.
 
 ## Multiple Resources: Block Form
 
@@ -43,9 +41,8 @@ You can also use a block form to create multiple resources.  The multiple resour
 
 You name the resource files with plural names. An example helps explain:
 
-    .kubes
-    └── resources
-        └── deployments.rb
+    .kubes/resources
+    └── deployments.rb
 
 .kubes/resources/web/deployments.rb
 
@@ -86,8 +83,9 @@ You can declare deployment, service, and other resource kinds multiple times.
 
 Layering works for both simple and block form. Just create a folder with the corresponding name.
 
-* The layering definitions with the simple form only merge with other simple form layers.
-* The layering definitions for block forms only merge with other block form layers.
+* The layering definitions for the pre layers are in singular form.
+* The layering definitions for the post layers are in a folder with plural form, but the overrides are defined in singular form still.
+* Resources in the main "middle" layer are the only ones that are allowed multiple resource definitions.
 
 Simple form layering:
 
@@ -105,8 +103,8 @@ Block form layering:
 
     .kubes/resources/
     ├── base
-    │   ├── alls.rb
-    │   └── deployments.rb
+    │   ├── all.rb
+    │   └── deployment.rb
     └── web
         ├── deployments
         │   ├── dev.rb

data/docs/_docs/helpers/google.md

@@ -4,7 +4,7 @@ title: Google Helpers
 
 List of Google helpers:
 
-{% assign docs = site.docs | where: "categories","helpers-aws" %}
+{% assign docs = site.docs | where: "categories","helpers-google" %}
 {% for doc in docs -%}
   * [{{ doc.nav_text }}]({{ doc.url }})
 {% endfor %}

data/docs/_docs/helpers/google/gke.md

@@ -19,14 +19,18 @@ KubesGoogle.configure do |config|
   config.gke.cluster_name = "dev-cluster"
   config.gke.google_region = ENV['GOOGLE_REGION']
   config.gke.google_project = ENV['GOOGLE_PROJECT']
-  config.gke.enable_get_credentials = true # enable hook to call: gcloud container clusters get-credentials
+  config.gke.enable_hooks   = KubesGoogle.cloudbuild?
+  config.gke.enable_get_credentials = KubesGoogle.cloudbuild? # enable hook to call: gcloud container clusters get-credentials
 end
 ```
 
-Note: The use of `KubesGoogle.configure` instead of `Kubes.configure` here.
-
 This enables `kubes apply` before and after hooks to add and remove the current machine IP.
 
+Notes:
+
+* Notice the use of `KubesGoogle.configure` instead of `Kubes.configure` here.
+* The `KubesGoogle.cloudbuild?` checks if kubes is running on a CloudBuild machine.  So hooks don't run locally on your machine.
+
 ## Options
 
 Here are the `config.gke` settings:

data/docs/_docs/helpers/google/secrets.md

@@ -63,7 +63,7 @@ By default, the values are automatically base64 encoded. You can change the defa
 
 ```ruby
 KubesGoogle.configure do |config|
-  config.secrets.base64 = true
+  config.secrets.base64 = false
 end
 ```
 

data/docs/_docs/intro/concepts.md

@@ -6,15 +6,14 @@ title: Kubes Concepts
 
 The `.kubes/resources` where you organized Kubernetes resources. Different subfolders within the resources folder represent your app. Example:
 
-    .kubes
-    └── resources
-        ├── clock
-        │   └── deployment.yaml
-        ├── worker
-        │   └── deployment.yaml
-        └── web
-            ├── deployment.yaml
-            └── service.yaml
+    .kubes/resources
+    ├── clock
+    │   └── deployment.yaml
+    ├── worker
+    │   └── deployment.yaml
+    └── web
+        ├── deployment.yaml
+        └── service.yaml
 
 Each folder contains your Kubernetes deployment definition, either in [YAML]({% link _docs/yaml.md %}) or [DSL]({% link _docs/dsl.md %}) form. Both can be used together.
 

data/docs/_docs/intro/ordering.md

@@ -37,16 +37,15 @@ Kubes will delete in the reverse order.
 
 Resources in the `shared` folder will be applied first.  Example:
 
-    .kubes
-    └── resources
-        ├── clock
-        │   └── deployment.yaml
-        ├── web
-        │   ├── deployment.yaml
-        │   └── service.yaml
-        └── shared
-            ├── config_map.yaml
-            └── secret.yaml
+    .kubes/resources
+    ├── clock
+    │   └── deployment.yaml
+    ├── web
+    │   ├── deployment.yaml
+    │   └── service.yaml
+    └── shared
+        ├── config_map.yaml
+        └── secret.yaml
 
 Results in: