rops 1.0.1 → 1.0.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: edce405e87d5a4199f1bf81eb2b308ffd59e980bfd8cca9e5af65d2766fe765d
-  data.tar.gz: 28579f4f236865908f1a0fdbac465225285c9961a2aaf13aa1513bd477a7481f
+  metadata.gz: 251592c08814310a14cc0530cb79be6d18510b28393211810690495c559c4632
+  data.tar.gz: 0a4aee08e4858051f0f555b1ca322a661673231ccd0da4c6258f604ed87eb5d7
 SHA512:
-  metadata.gz: 70d5f614103f56e270c43014c81bc4801223a0fbae5977f4f658367b590c96ba0308c631c88f75c8f18c88882dfb350fee85b620f477afa1db524775f406d1c7
-  data.tar.gz: ed7bb0203a5dbe569019bef605e9a8ab805de1d8a0914f8d9162b4157c64b7a78489000ef13fbb1e112feced24a5a9a7f71244a1582e48ea4d18aa8a909703e4
+  metadata.gz: ff89c2f68f4a214da8d451f95719c512f816913a5bc40cc5c8e04e1440d99a0f9d53f7dc70228637dc61ebbc311eb7f8987b4e0f86deb4abc10954d1a7c5de79
+  data.tar.gz: de710e909b10d21e70a6f7386ee79d94311cd84a7cfe0f0d67b966cb92251463911890dd1ae0ea2ac7cc2b4d57c62e9ddd92badc29e9e0571a6acbe356a822ab

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    rops (1.0.1)
+    rops (1.0.5)
       activesupport (~> 6.1.4)
       dry-cli (~> 0.7.0)
       git (~> 1.9.1)

data/README.md

@@ -2,26 +2,23 @@
 
 The Record360 Operations tool - checkout, build, deploy
 
-## Usage
+## Description
 
 This tool implements the Record360 Best Practices for building and deploying projects.  It interfaces with Git (for source control), Docker/Podman (for container images), and Kubernetes (cluster deployments).
 
-### Installation
+## Installation
 
-Add `rops` to your Gemfile and then run `bundle install`.
+Download and install with:
 
-```ruby
-# Gemfile
-group :development do
-  gem 'rops', github: 'Record360/rops'
-end
+```shell
+gem install rops
 ```
 
-### Configuration
+## Configuration
 
 `rops` has several opinionated defaults, which can be overridden by command line options or a configuration file.
 
-#### Project Root Directory
+### Project Root Directory
   By default, the current working directory when `rops` runs.  It can be overridden with the `--root=<DIR>` option.
 
   The project root directory must contain:
@@ -34,7 +31,7 @@ end
   * `./platform/rops.yaml`
   * `./config/rops.yaml`
 
-#### Docker Container Images
+### Docker Container Images
   By default, a single image named from the the Project root directory and built from `./Dockerfile`.  May be overridden by setting the `images` array in the configuration file, e.g.:
 
 ```yaml
@@ -45,23 +42,22 @@ images:
   dockerfile: dockerfiles/second.Dockerfile
 ```
 
-#### Git Default Branch
+### Git Default Branch
   The Git branch to build, by default `master`.  Overridden with the `default_branch` field in the configuration file.
 
-#### Docker Registry
-  The Docker registry to push container images.  By default, `docker.io/r360`, which is probably not what you want and should be overridden by setting the `registry` field in the configuration file.
+### Docker Registry
+  The Docker registry to push container images.  By default, `r360`, which is probably not what you want and should be overridden by setting the `registry` field in the configuration file.
 
-#### Kubernetes Context
+### Kubernetes Context
   The name of the Kubernetes context to deploy to (as listed in `~/.kube/config`).  Defaults to `staging` and overridden with the `default_context` field in the configuration file.
 
   There are extra safety features when deploying to the production context, which defaults to `production` and may be overridden with the `production_context` field in the configuration file.
 
   Kubernetes configuration is organized by Kubernetes context name, under the `./platform` directory.  For example, the Kubernetes configuration for the default contexts (`staging` and `production`) is stored under `./platform/staging` and `./platform/production` respectively.
 
-### Operations
+## Operations
 
 ### Status
-
 Arguments: 
 * `context`: Kubernetes context (default `staging`, or the value of `staging_context`)
 
@@ -80,7 +76,6 @@ Currently running (staging):
 ```
 
 ### Build
-
 Arguments: 
 * `branch`: Git branch/commit (default `master`, or the value of `default_branch`)
 
@@ -105,7 +100,6 @@ Successfully tagged localhost/web:gfc50028b-feature
 ```
 
 ### Push
-
 Arguments: 
 * `branch`: Git branch/commit (default `master`, or the value of `default_branch`)
 
@@ -120,7 +114,6 @@ Storing signatures
 ```
 
 ### Deploy
-
 Arguments: 
 * `branch`: Git branch/commit (default `master`, or the value of `default_branch`)
 * `context`: Kubernetes context (default `staging`, or the value of `default_context`)

data/bin/rops

@@ -1,7 +1,6 @@
 #!/usr/bin/env ruby
 $: << __dir__+'/../lib'
 
-require 'bundler/setup'
 require 'dry/cli'
 require 'active_support'
 require 'active_support/core_ext'

data/lib/deployer.rb

@@ -9,7 +9,7 @@ class Deployer
   CONFIG_DEFAULTS = {
     'repository' => nil,
     'default_branch' => 'master',
-    'registry' => 'docker.io/r360',
+    'registry' => 'r360',
     'default_context' => 'staging',
     'production_context' => 'production',
     'images' => []
@@ -135,7 +135,7 @@ class Deployer
     cmd = "kubectl --context #{context} #{cmd}"
 
     if ssh_host.blank?
-      stdout, stderr, cmd_status = Open3.capture3(cmd)
+      stdout, stderr, cmd_status = Open3.capture3(cmd, stdin_data: data)
       [ stdout, stderr, cmd_status.success? ]
     else
       require 'net/ssh'

data/lib/image.rb

@@ -68,7 +68,7 @@ class Image
       if status.success? || stderr.include?('error parsing manifest blob')
         @remote_exists = true
       else
-        puts stderr  if stderr.present? && !stderr.include?('manifest unknown')
+        puts stderr  if stderr.present? && !stderr.include?('manifest unknown') && !stderr.include?('no such manifest')
         @remote_exists = false
       end
     end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rops
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.5
 platform: ruby
 authors:
 - Steve Sloan