cknife 1.2.0 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 42b1aec5549d2d6e08113f9d867e4faad1cf3954
-  data.tar.gz: b30a5ad505f0c656eaf4fb800704a5d4824492b1
+  metadata.gz: 8e24f7e41e3ed98f6d61a0d360b26f096862b121
+  data.tar.gz: fa9e6591fa5c4ac455e161f8a0766c254fb3aa56
 SHA512:
-  metadata.gz: 9e023ec2bb2a311ea6afabe95b7325de60e94de53f2854b018160aa99f4fa30d301b48c5266bfa07e60107a21f5575538187e7a6b464167be188fd8638bcc92c
-  data.tar.gz: ddc7b4e2541e650e1b3df6d28e110c63972aff17baf38ac4d4e48735519a62a8c4a13893c58ae6342ebd120f2a563a01f8fa59d4b0806422f4302897dfd135ee
+  metadata.gz: 8678596a96eeff55e41a21af3c1b6ac27ed1c5749451c839e33d9051041c507bd17668c548049fce8588126a26d3f9ad2789ebb2755cf267156fcc807481a255
+  data.tar.gz: 1510e3040a671d69d988f3cbfa7c0631f9ab68601b40d3aa1593bd1024995b70e4e39c677fea89ceaa172a35d5a8ada9124bb681606a0a5aaa802f6fb8635996

data/.ruby-version

@@ -1 +1 @@
-2.0.0-p643
+2.4

data/README.md

@@ -1,361 +1,147 @@
 
-# Overview
+# Quickstart
 
-cknife has command line tools written in Ruby. They're supposed
-to help with some system administration tasks.
-
-# Requirements
-
-Ruby >= 2.1.
-
-# Installation
-
-Install ruby and possibly bundler:
+cknife is a set of command line tools. They...do different things.
 
     > \curl -sSL https://get.rvm.io | bash -s stable --ruby
-    > gem install bundler
-
-Create a Gemfile with cknife and its git repository.
-
-
-    source "http://rubygems.org"
-    git_source(:github) { |repo| "https://github.com/#{repo}.git" }
-
-    gem "cknife", '~> 1.1.0'
-
-Run bundle.
-
-    > bundle
-
-# Monitor
-
-This sends out a PUT request every fifteen minutes to a server
-you configure.
-
-    > bundle exec cknifemon 
-    Tasks:
-      cknifemon help [TASK]  # Describe available tasks or one specific task
-      cknifemon restart      # Restart monitor.
-      cknifemon start        # Start monitor.
-      cknifemon status       # Show status of monitor.
-      cknifemon stop         # Stop monitor.
-
-It is designed to work with M. Rivera CRM, but you can configure the
-url to be any endpoint for your own monitoring purposes. You can
-configure alerts on the server that you create as the target endpoint
-of the monitor.
-
-The configuration is as follows:
-
-    mon:
-      url: http://some.server.com/monitored_computers/heartbeat
-      api_key: someapikey
-
-# Amazon Web Services (AWS) Command Line Interface
-
-    > bundle exec cknifeaws help 
-    Tasks:
-      cknifeaws afew [BUCKET_NAME]                  # Show first 5 files in bucket
-      cknifeaws create [BUCKET_NAME]                # Create a bucket
-      cknifeaws create_cloudfront [BUCKET_NAME]     # Create a cloudfront distribution (a CDN)
-      cknifeaws delete [BUCKET_NAME]                # Destroy a bucket
-      cknifeaws download [BUCKET_NAME]              # Download all files in a bucket to CWD. Or one file.
-      cknifeaws fdelete [BUCKET_NAME] [FILE_NAME]   # Delete a file in a bucket.
-      cknifeaws fupload [BUCKET_NAME] [LOCAL_FILE]  # Upload a file to a bucket. Path to file is ignored.
-      cknifeaws help [TASK]                         # Describe available tasks or one specific task
-      cknifeaws list                                # Show all buckets
-      cknifeaws list_cloudfront                     # List cloudfront distributions (CDNs)
-      cknifeaws list_servers                        # Show all servers
-      cknifeaws show [BUCKET_NAME]                  # Show info about bucket
-      cknifeaws start_server [SERVER_ID]            # Start a given EC2 server
-      cknifeaws stop_server [SERVER_ID]             # Stop a given EC2 server (does not terminate it)
-      cknifeaws upsync [BUCKET_NAME] [DIRECTORY]    # Push local files matching glob PATTERN into bucket. Ignore unchanged files.
-
-### AWS Key and Secret Configuration
-
-Setup your AWS key and secret in any of these methods, in order of priority:
-
-  - $CWD/cknife.yml
-  - $CWD/tmp/cknife.yml
-  - environment variables: `KEY`, `SECRET`
-  - environment variables: `AMAZON_ACCESS_KEY_ID`, `AMAZON_SECRET_ACCESS_KEY` 
+    > gem install cknife
 
-If using one of the above cknife.yml files to define your keys, the format
-is as follows:
+Create `$CWD/tmp/cknife.yml` and put in a AWS key-secret pair:
 
     ---
     key: AKIAblahblahb...
     secret: 8xILhOsecretsecretsecretsecret...
 
-### Upload a local directory into an S3 Bucket
-
-    Usage:
-      cknifeaws upsync [BUCKET_NAME] [DIRECTORY]
-
-    Options:
-      [--public]             
-      [--region=REGION]      
-                             # Default: us-east-1
-      [--noprompt=NOPROMPT]  
-      [--glob=GLOB]          
-                             # Default: **/*
-      [--backups-retain]     
-      [--days-retain=N]      
-                             # Default: 30
-      [--months-retain=N]    
-                             # Default: 3
-      [--weeks-retain=N]     
-                             # Default: 5
-      [--dry-run]            
-
-Some examples:
-
-Upload and sync `/tmp/*.sql` into `my-frog-app-backups`
-bucket. Treat the files as backup files, and keep one backup
-file for each of the last 5 months, 10 weeks, and 30 days.    
-
-    > cknifeaws upsync my-frog-app-backups ./tmp --glob "*.sql" --noprompt --backups-retain true --months-retain 5 --weeks-retain 10 --days-retain 30
-
-As above, but now do redis backup files (`./tmp/*.rdb`). these will
-not produce namespace collisions with the sql files, and thus the same
-bucket can be used to store backups for both .sql and .rdb files.
-
-    > cknifeaws upsync my-frog-app-backups ./tmp --glob "*.rdb" --noprompt --backups-retain true --months-retain 5 --weeks-retain 10 --days-retain 30
-
-**DO NOT DO THIS INSTEAD OF THE ABOVE 2 COMMANDS, THINKING IT WILL
-TREAT .SQL AND .RDB FILES SEPARATELY. INSTEAD, YOU WILL LOSE
-SOME OF YOUR BACKUP FILES.**
-
-    > cknifeaws upsync my-frog-app-backups ./tmp --glob "*" --noprompt --backups-retain true --months-retain 5 --weeks-retain 10 --days-retain 30
-
-Dry run mode. Try one of the prior backups retain commands, but
-let's see what will happen, first.
-
-    > cknifeaws upsync my-frog-app-backups ./tmp --glob "*.sql" --noprompt --backups-retain true --months-retain 5 --weeks-retain 10 --days-retain 30 --dry-run
-
-This is the premier feature of the gem.
-
-Uses multipart uploads with a chunksize of 10 megabytes to keep RAM
-usage down.
-
-It can be used to run a backups schedule with multiple classes of
-files (partitioned by a glob pattern). **It is your responsibility to
-generate one uniquely-named backup file per day**, as this tool does
-not do that part for you.
-
-If you *don't* use the `backups-retain` option, then its like a very
-weak **rsync** that can upload from a local filesystem into a bucket.
-Which is also pretty useful.
-
-The glob allows you to determine whether you want to recursively
-upload an entire directory, or just a set of *.dat or *.sql files,
-ignoring whatever else may be in the specified directory. This glob
-pattern is appended to the directory you specify.
-
-For determining whether to upload a file, it uses the file's local
-filesystem modification time, and if there is a mismatch then it does
-an md5 checksum comparison, and if there is a mismatch there, then the
-local file will replace the remote one in S3. The file's local
-filesystem modification time is stored on S3 in the S3 object's
-metadata when the file is uploaded.
-
-### Download an S3 bucket to a local directory
-
-Sometimes you want to download an entire S3 bucket to your local
-directory - a set of photos, for example.
-
-    > cknifeaws help download 
-    Usage:
-      cknifeaws download [BUCKET_NAME]
+Then invoke the `cknifeaws` tool.
 
-    Options:
-      [--region=REGION]  
-                         # Default: us-east-1
-      [--one=ONE]        
+    > cknifeaws afew your-bucket-name
 
-    Download all files in a bucket to CWD. Or one file.
+That will show you a few files in that Amazon S3 bucket of yours
+named `your-bucket-name`.
 
-Download entire my-photos bucket to CWD
-
-    > cknifeaws download my-photos 
-
-# SMTP Email Command Line Interface
-
-    > cknifemail help
-    Tasks:
-      cknifemail help [TASK]                             # Describe available tasks or one specific task
-      cknifemail mail [RECIPIENT] [SUBJECT] [TEXT_FILE]  # Send an email to recipient.
-
-Only simple email sending is available here, for now.
-
-### Send an email
-
-    > bundle exec ./bin/cknifemail help mail 
-    Usage:
-      cknifemail mail [RECIPIENT] [SUBJECT] [TEXT_FILE]
-
-    Options:
-      [--from=FROM]      
-      [--simple-format]  
-                         # Default: true
-
-The `simple_format` option is available to help format plaintext
-emails whose bodies you don't want messed up when newlines are ignored
-with html formatting. This is helpful for when log files are included
-in email bodies, which is the primary expectation for how this will
-be used.
-
-Has been successfully tested with the SMTP interface to Amazon SES and
-Sendgrid. Should work with Postmark just fine.
-
-This **requires** the cknife YAML config, with the following field structure.
-
-    mail:
-      from: "Rick Santana <rick.santana@example.com>"
-      authentication: login
-      address: smtp-server
-      port: smtp-port (defaults to 587)
-      username: yoursmtpusername
-      password: yoursmtppassword
-      domain: domain-if-you-like.com
-
-
-
-# Zerigo Command Line Interface
-
-The These tasks can be used to manage your DNS via Zerigo.  They changed
-their rates drastically with little notice in January of 2014, so I
-switched to DNS Simple and don't use this much anymore.
-
-    > cknifezerigo help
-    Tasks:
-      cknifezerigo create [HOST_NAME]  # Create a host
-      cknifezerigo delete [ID]         # Delete an entry by id
-      cknifezerigo help [TASK]         # Describe available tasks or one specific task
-      cknifezerigo list                # List available host names.
-
-# PostgreSQL Backups
-
-This is a wrapper around the PostgreSQL backup and restore command
-line utilities.
-
-It requires the following Rails-style configuration in the
-configuration file:
-
-    pg:
-      host: localhost
-      database: dbname
-      username: dbuser
-      password: dbpassword
-
-**Warning:** do not use a colon in your password, or the password
-configuration will not work. This is a shortcoming of this project and
-a consequence of the `.pgpass` file format used by PostgreSQL.
-
-Then you can capture a snapshot of your database. You can also restore
-it using this tool.
-
-    > bundle exec cknifepg help 
-    Tasks:
-      cknifepg capture      # Capture a dump of the database to db(current timestamp).dump.
-      cknifepg disconnect   # Disconnect all sessions from the database. You must have a superuser configured for this to work.
-      cknifepg help [TASK]  # Describe available tasks or one specific task
-      cknifepg restore      # Restore a file. Use the one with the most recent mtime by default. Searches for db*.dump files in the CWD.
-      cknifepg sessions     # List active sessions in this database and provide a string suitable for giving to kill for stopping those sessions.
-
-This generates and deletes a `.pgpass` file before and after the
-command line session. Be aware that if this process is interrupted,
-the `.pgpass` file may be left on disk in the CWD.
-
-# MySQL Backups
-
-Like pg, this requires a similar setup in the configuration:
-
-    mysql:
-      host: localhost
-      database: dbname
-      username: dbuser
-      password: dbpassword
-
-Then you can capture a snapshot of your database.
+    > cknifeaws afew my-bucket --count=50
+    
+That will show you 50 of them.
+
+# Why bother?
+
+What do you do when you don't want to write
+[bash](https://www.tldp.org/LDP/Bash-Beginners-Guide/html/Bash-Beginners-Guide.html),
+your `.bash_profile` already has more aliases than you can manage, and
+yet you still find it silly to be going to the same [old documentation
+websites](https://www.postgresql.org/docs/9.5/static/backup-dump.html)
+for things you are certain you once knew how to do?
+
+Well, you can write a script in something other than
+bash to automate the precise command line invocation
+that you used to accomplish a task. But when you
+move to a different project, how can you take your
+scripts with you? Why not design your scripts
+to be robust enough so that they are conventional?
+
+Why can't a [Stackoverflow](https://stackoverflow.com) question's
+answer be captured in a form that can be configured and called by you
+(or someone who was in your position before), so that you don't have
+to enter the same question into
+[google.com](https://www.google.com/?q=LOL%20HALP%20ME%20CODE) again
+later down the road?
+
+Why make a browser bookmark if you can skip the browser entirely?
+It's not like the browser bookmark can compile the answer into machine
+code for you, anyway.
+
+If someone turns the answer into a programmed tool, what if your IDE
+is no better than the command line when it comes to invoking it?
+
+I created cknife to have a set of scripts to fall back on when
+confronted with the above encounter I've been having for years. cknife
+is a toolset that encapsulates common command line expressions that
+developers use when at work.
+
+I've never used [chef](https://www.chef.io), but were I to grow
+cknife, I wouldn't be surprised to see it overlap with it.
+
+cknife currently has some wrappers around Amazon's EC2 and S3
+services. It has others around MySQL and PostgreSQL. It has a trivial
+one around [du](http://man7.org/linux/man-pages/man1/du.1.html).  The
+`cknifemon` tool, meanwhile, is a daemon that can launch PUT HTTP
+requests to an endpoint you configure, on a schedule.
+
+It can be used for system administration, but it can be also be used
+to aid developers as they acclimate themselves to a piece of
+technology with which they may not be familiar, and for which
+documentation may be a little scattered. It can be used
+to bang on a piece of technology for the sake of your own
+learning, too.
+
+To be precise, cknife consists of command line executables. These
+tools often require more information from the user, which can be put
+into a configuration file, `cknife.yml`, in YAML format, and found by
+cknife in the current working directory ($CWD) when it is invoked.
+
+See the [Wiki](https://github.com/mikedll/cknife/wiki) for
+details on the tools cknife has.
 
-    > bundle exec cknifemysql help 
-    Tasks:
-      cknifemysql capture      # Capture a dump of the database to db(current timestamp).sql.
-      cknifemysql help [TASK]  # Describe available tasks or one specific task
-      cknifemysql restore      # Restore a file. Use the one with the most recent mtime by default. Searches for db*.sql files in the CWD.
+# Requirements
 
-Sample output:
+  - Ruby >= 2.4. Older versions work to some extent with older rubies.
 
-    > bundle exec cknifemysql capture 
-    mysqldump --defaults-file=my.cnf -h localhost -P 3306 -u dbuser dbname --add-drop-database --result-file=db20150617125335.sql
-    Captured db20150617125335.sql.
+The cknife executables are implemented with the Ruby
+[Thor](https://github.com/erikhuda/thor) gem.
 
-And the accompanying restore, were you to run it immediately afterwards:
+# Installation
 
-    > bundle exec cknifemysql restore 
-    Restore db20150617125335.sql? y
-    Doing restore...
-    mysql --defaults-file=my.cnf -h localhost -P 3306 -u dbuser dbname
-    source db20150617125335.sql;
-    Restored db20150617125335.sql
+Install Ruby and possibly bundler:
 
-**Important:** As you can see, a my.cnf is generated and your password
-stored in there. That file is removed when the command is done
-executing.  This keeps your password off of the command line and
-hidden from certain `top` or `ps` invocations by other users who may
-be on the same machine. This rational is taken from the PostgreSQL
-PGPASSFILE documentation. If this command error's-out, you'll be
-warned to remove this file yourself for security purposes.
+    > \curl -sSL https://get.rvm.io | bash -s stable --ruby
+    > gem install bundler
 
-# Dub
+Add cknife to a Gemfile.
 
-Like du, but sorts your output by size.  This helps you determine
-which directories are taking up the most space:
+    source "http://rubygems.org"
+    git_source(:github) { |repo| "https://github.com/#{repo}.git" }
 
-    > cknifedub
-          37.0G .
-          23.0G ./Personal
-          14.0G ./Library
-         673.0M ./Work
-           0.0B ./Colloquy Transcripts
+    gem "cknife", '~> 1.1.0'
 
-Options:
+Run bundle.
 
-    -c Enable colorized output. 
+    > bundle
 
-# A typical cron script for capturing PostgreSQL backups and uploading them to S3
+# Usage
 
-    #!/bin/bash
-    
-    source "$HOME/.rvm/scripts/rvm";
+The cknife tools make use of a common configuration file. It uses a
+YAML format. It is named `cknife.yml` and the tools look for it in
+these two places, in order:
 
-    rvm use 2.0.0;
+  - $CWD/cknife.yml
+  - $CWD/tmp/cknife.yml
 
-    cd path/to/backups/dir/with/cknife/config;
+Here are the command line executables:
 
-    cknifepg capture;
+  - cknifeaws
+  - cknifedub
+  - cknifemail  
+  - cknifemon
+  - cknifemysql
+  - cknifenowtimestamp
+  - cknifepg
+  - cknifewcdir
 
-    cknifeaws upsync backups-bucket . --noprompt --backups-retain --glob="db*.dump";
+You can invoke any of them like this:
 
-    find -mtime +7 -iname "*.dump" -delete
-    
-Which can be used with the following sample [crontab](http://en.wikipedia.org/wiki/Cron#Examples),
-executing once a day at 2am:
+    bundle exec cknifeaws
 
-    # * * * * *  command to execute
-    # │ │ │ │ │
-    # │ │ │ │ │
-    # │ │ │ │ └───── day of week (0 - 6) (0 to 6 are Sunday to Saturday, or use names; 7 is Sunday, the same as 0)
-    # │ │ │ └────────── month (1 - 12)
-    # │ │ └─────────────── day of month (1 - 31)
-    # │ └──────────────────── hour (0 - 23)
-    # └───────────────────────── min (0 - 59)
+# Security Awareness
 
-    0 2 * * *  path/to/script > /dev/null
+Since the `cknife.yml` holds sensitive information in the name of
+convenience, you may choose to erase it after you're done with what
+you're doing with it. It depends on your use, of course. You probably
+want to add it to your `.gitignore` file if you're using it on a
+per-project basis.
 
+# Development
 
-### Making a release
+## Making a release
 
 One of the following, like patch. This will create a git commit.
 
@@ -366,7 +152,7 @@ One of the following, like patch. This will create a git commit.
 Do a git flow release. Create the gem spec and commit it:
 
     bundle exec rake gemspec:generate
-    git commit -am "Generated gemspec for version 0.1.4"
+    git commit -am "Generated gemspec for version 1.3.0"
 
 Do a git flow finish release. Push to github. You can
 then do a release to Rubygems. This command will
@@ -375,7 +161,7 @@ since the gemspec is already valid.
 
     rake release
 
-### Building Locally (Optional)
+## Building Locally (Optional)
 
 You may build a local gem:
 
@@ -385,7 +171,7 @@ And remove it:
 
     rm pkg/cknife-0.1.6.gem
 
-### Invoking commands without clobbering the gemspec
+## Invoking commands without clobbering the gemspec
 
 You can uncommente the 'gem cknife' line in the Gemfile.
 

data/VERSION

@@ -1 +1 @@
-1.2.0
+1.3.0

data/bin/cknifewcdir

@@ -1,28 +1,67 @@
 #!/usr/bin/env ruby
 
-def run
-  wccmd = `find . -ipath #{ARGV[0]} -exec wc -l {} \\;`
-
-  comps = []
-
-  total = 0
-  wccmd.split(/\n/).each do |l|
-    l =~ /\s*(\d+(\.\d+)?)\s+(.*)$/
-    size = $1
-    path = $3
-    comps << [size.to_i, path]
-    total += size.to_i
-  end
+require 'thor'
 
-  comps.sort! do |a, b|
-    b[0] <=> a[0]
-  end
+class CKnifeWcdir < Thor
+
+  default_task :count
+
+  class_option :verbose, :default => false, :type => :boolean, :desc => "Show which commands are invoked, any input given to them, and any output they give back."
+
+  desc "count [PATTERNS] or simply [PATTERNS] without count will work", "Count lines of code in files matching the [PATTERNS] in the $CWD. Use patterns like this: *.rb, *.php."
+  long_desc <<-LONGDESC
+      Counts lines of code in the $CWD. Prints the files found, and
+      their line counts, in descending order of line count.
+
+      Requires patterns such as *.rb, or *.php, so that it knows what
+      files to count (it doesn't use a default file type).
+
+      You can supply directory names to exclude from consideration,
+      such as 'vendor' or 'node_modules'.
+
+      --skip=vendor node_modules
+
+      > cknifewcdir *.rb *.js --skip=vendor node_modules
+      \x5(...results...)
 
-  comps.each do |(size,path)|
-    printf( "%d %s\n", size, path)
+      This is a wrapper around the find and wc posix commands.
+  LONGDESC
+  method_option :start, :type => :string, :default => "", :desc => "location to begin your search"
+  method_option :skip, :type => :array, :default => [], :desc => "names of directories to skip"
+  def count(*patterns)
+    start_point = options[:start].empty? ? "." : options[:start].chomp('/')
+
+    pattern_s = "\\( " + patterns.map { |p| "-name #{p}" }.join(' -o ') + " \\) "
+    skip_s = options[:skip].empty? ? "" : "-type d \\( " + options[:skip].map { |dir| "-path #{start_point}/#{dir.chomp('/')}" }.join(' -o ') +  " \\) -prune -o "
+
+    # note patterns must go after the skips (after the -prune -o)
+    cmd = "find #{start_point} #{skip_s}#{pattern_s} -exec wc -l {} \\;"
+
+    puts cmd if options[:verbose]
+    wccmd = `#{cmd}`
+
+    comps = []
+
+    total = 0
+    wccmd.split(/\n/).each do |l|
+      l =~ /\s*(\d+(\.\d+)?)\s+(.*)$/
+      size = $1
+      path = $3
+      comps << [size.to_i, path]
+      total += size.to_i
+    end
+
+    comps.sort! do |a, b|
+      b[0] <=> a[0]
+    end
+
+    print_table([["LOC", "File"]] + comps)
+
+    puts "Total: #{total}"
   end
 
-  puts "Total: #{total}"
 end
 
-run
+ARGV.unshift(CKnifeWcdir.default_task) unless CKnifeWcdir.all_tasks.has_key?(ARGV[0])
+CKnifeWcdir.start(ARGV)
+

data/cknife.gemspec

@@ -2,11 +2,11 @@
 # DO NOT EDIT THIS FILE DIRECTLY
 # Instead, edit Jeweler::Tasks in Rakefile, and run 'rake gemspec'
 # -*- encoding: utf-8 -*-
-# stub: cknife 1.2.0 ruby lib
+# stub: cknife 1.3.0 ruby lib
 
 Gem::Specification.new do |s|
   s.name = "cknife".freeze
-  s.version = "1.2.0"
+  s.version = "1.3.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0".freeze) if s.respond_to? :required_rubygems_version=
   s.require_paths = ["lib".freeze]
@@ -14,7 +14,7 @@ Gem::Specification.new do |s|
   s.date = "2018-10-10"
   s.description = "A collection of command line tools, especially for popular API services.".freeze
   s.email = "soymrmike@gmail.com".freeze
-  s.executables = ["cknifeaws".freeze, "cknifedub".freeze, "cknifemail".freeze, "cknifemon".freeze, "cknifemysql".freeze, "cknifenowtimestamp".freeze, "cknifepg".freeze, "cknifewcdir".freeze, "cknifezerigo".freeze]
+  s.executables = ["cknifeaws".freeze, "cknifedub".freeze, "cknifemail".freeze, "cknifemon".freeze, "cknifemysql".freeze, "cknifenowtimestamp".freeze, "cknifepg".freeze, "cknifewcdir".freeze]
   s.extra_rdoc_files = [
     "LICENSE",
     "README.md"
@@ -36,7 +36,6 @@ Gem::Specification.new do |s|
     "bin/cknifenowtimestamp",
     "bin/cknifepg",
     "bin/cknifewcdir",
-    "bin/cknifezerigo",
     "cknife.gemspec",
     "cknife.yml.sample",
     "doc/remote_ubuntu_machine.md",

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cknife
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.3.0
 platform: ruby
 authors:
 - Michael Rivera
@@ -227,7 +227,6 @@ executables:
 - cknifenowtimestamp
 - cknifepg
 - cknifewcdir
-- cknifezerigo
 extensions: []
 extra_rdoc_files:
 - LICENSE
@@ -249,7 +248,6 @@ files:
 - bin/cknifenowtimestamp
 - bin/cknifepg
 - bin/cknifewcdir
-- bin/cknifezerigo
 - cknife.gemspec
 - cknife.yml.sample
 - doc/remote_ubuntu_machine.md

data/bin/cknifezerigo

@@ -1,97 +0,0 @@
-#!/usr/bin/env ruby
-
-require 'rest-client'
-require 'thor'
-require 'active_support/all'
-
-class Zerigo < Thor
-
-  ENDPOINT = "https://ns.zerigo.com/api/1.1"
-  USERNAME = ENV['ZERIGO_USERNAME']
-  PASSWORD = ENV['ZERIGO_PASSWORD']
-  DOMAIN = ENV['ZERIGO_DEFAULT_DOMAIN']
-
-
-  no_tasks do
-    def zerigo
-      @zerigo ||= RestClient::Resource.new ENDPOINT, USERNAME, PASSWORD
-    end
-
-    def show_hosts(response)
-      fmt = "%6.5s %30.29s %40.39s %12.11s"
-
-      puts sprintf(fmt, 
-                   "Type",
-                   "Hostname",
-                   "Data",
-                   "ID")
-
-      Nokogiri::XML( response.body ).css('host').each do |host|
-        puts sprintf(fmt,
-                     host.at_css('host-type').text,
-                     host.at_css('hostname').text,
-                     host.at_css('data').text,
-                     host.at_css('id').text)
-      end
-    end
-
-    def zone
-      if @zone.nil?
-        zones = []
-        response = zerigo['/zones.xml'].get 
-        unless response.code.to_s !~ /2\d{2}/
-          Nokogiri::XML( response.body ).css('zone').each do |zone|
-            zones << {
-              :id => zone.css('id').first.text,
-              :domain => zone.css('domain').first.text,
-            }
-          end
-        end
-        found = zones.select { |z| z[:domain] == DOMAIN }.first
-        raise "Unable to find zone matching domain #{DOMAIN}" unless found
-
-        @zone = found[:id]
-      end
-      @zone
-    end
-  end
-
-  module HostTypes
-    CNAME = "CNAME"
-    ARECORD = "A"
-    MX = "MX"
-  end
-
-  desc "list", "List available host names."
-  def list
-    response = zerigo["/zones/#{zone}/hosts.xml"].get
-    unless response.code.to_s !~ /2\d{2}/
-      show_hosts( response )
-    end
-  end
-
-  desc "create [HOST_NAME]", "Create a host"
-  method_options :data => "proxy.heroku.com"
-  method_options :host_type => HostTypes::CNAME
-  def create(hostname = "")
-    new_host = { :data => options[:data], :host_type => options[:host_type], :hostname => hostname }
-
-    response = zerigo["/zones/#{zone}/hosts.xml"].post new_host.to_xml(:root => "host"), :content_type => "application/xml"
-    if response.code.to_s =~ /201/
-      puts "Created a host."
-      show_hosts( response )
-    end    
-  end
-
-
-  desc "delete [ID]", "Delete an entry by id"
-  def delete(id)
-    response = zerigo["/hosts/#{id}.xml"].delete
-    if response.code.to_s =~ /200/
-      puts "Delete a host with id #{id}"
-    end    
-  end
-
-end
-
-Zerigo.start