vtk 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 548575ce6bef53e2e3e617e8151e056879c569821d24cdcb0c9ab1ded7cde684
+  data.tar.gz: 1a087c94d0c2f30076cbd312c020a59dcc995185a4cf5a658a9fe3fd35adde45
+SHA512:
+  metadata.gz: 9772f4461e30d1fb40da791790c851aada39362d18dff6d9b903ad45a2b35017201066c724397a99175d923f2aa4940563b6af65c360f86920e826fdcd51944d
+  data.tar.gz: 63a40c81a3f42214db2a46cc9ccd68a562ce570c5b1557a5d9937f156ad850ea7ec98774c481ed18f759e05b71d29da9396ac9b581e9267437405537096a6674

data/.editorconfig

@@ -0,0 +1,11 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

data/.github/workflows/main.yml

@@ -0,0 +1,13 @@
+name: Ruby
+
+on: [push,pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-20.04
+    steps:
+    - uses: actions/checkout@v2
+    - uses: ruby/setup-ruby@v1
+      with:
+        bundler-cache: true
+    - run: bundle exec rake

data/.gitignore

@@ -0,0 +1,19 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log
+
+# rspec failure tracking
+.rspec_status
+
+# Don't check in lock file for this app (gem)
+Gemfile.lock

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,5 @@
+AllCops:
+  NewCops: enable
+
+Layout/LineLength:
+  Max: 120

data/.tool-versions

@@ -0,0 +1 @@
+ruby 2.7.2

data/CHANGELOG.md

@@ -0,0 +1,35 @@
+commit 27fe3ef674a283686b7cff164386ec9d913208ef (HEAD -> start-afresh-with-tty, origin/start-afresh-with-tty)
+Author: Lindsey Hattamer <lindsey.hattamer@oddball.io>
+Date:   Mon Jan 4 11:13:11 2021 -0500
+
+    add docs
+
+commit 3a7d97c35ca9f084a0f27d1a2ff522dd8e9b2abc
+Author: Eric Boehs <eric@boehs.com>
+Date:   Mon Jan 4 10:11:38 2021 -0600
+
+    Looks like rake runs rubocop already
+
+commit 9f7df0e213edaa57420a1bd14501aea6fc4ffd5a
+Author: Eric Boehs <eric@boehs.com>
+Date:   Mon Jan 4 10:10:33 2021 -0600
+
+    GH Actions: Pin Ubuntu to 20.04 (avoids warning)
+
+commit 3343941e76b506ed00d3fbd1a7ecd163873597fc
+Author: Eric Boehs <eric@boehs.com>
+Date:   Mon Jan 4 10:06:42 2021 -0600
+
+    Add tool-versions and rubocop to GitHub Actions
+
+commit 99560d5ad44c9889bdd4884104c993aa86749a40
+Author: Lindsey Hattamer <lindsey.hattamer@oddball.io>
+Date:   Mon Jan 4 11:03:58 2021 -0500
+
+    Remove adding to gemfile
+
+commit b6394523b7eafbde3276a9f990dd7e4179e124e4
+Author: Lindsey Hattamer <lindsey.hattamer@oddball.io>
+Date:   Mon Jan 4 11:02:55 2021 -0500
+
+    Update .github/workflows/main.yml

data/Gemfile

@@ -0,0 +1,6 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in vtk.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,20 @@
+The MIT License (MIT)
+
+Copyright (c) 2020 Eric Boehs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
+the Software, and to permit persons to whom the Software is furnished to do so,
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,19 @@
+# VSP Toolkit (`vtk`)
+
+The purpose of this gem is to allow VFS engineers to quickly begin developing on the platform. It does this by providing a command line interface that allows the use of simple commands and parameters to do everything from setting up a development environment to building out a directory structure and creating necessary files for separating code into its own module.
+
+*The following assumes you have Ruby 2.6.6 or higher installed.*
+
+## Installation
+
+Install it yourself as:
+
+    $ gem install vtk
+
+## Usage
+
+### Modules
+
+Teams developing for vets-api should create their code as a module. This allows for the separation and easy identification of different projects. To scaffold a directory structure for your module, first cd into the vets-api directory, then enter the command below, substituting the name of your module for *<module name>*. This will build out a directory structure and create necessary files in the `modules/` directory.
+
+    $ vtk module add <module name>

data/Rakefile

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+
+require 'rubocop/rake_task'
+
+RuboCop::RakeTask.new
+
+task default: %i[spec rubocop]

data/bin/console

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'bundler/setup'
+require 'vtk'
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require 'irb'
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+gem install bundler --conservative
+bundle config set --local path '.bundle/bundle'
+bundle install
+bundle binstubs --all
+gem install tty --conservative
+
+# Do any other automated setup that you need to do here

data/docs/design-doc.md

@@ -0,0 +1,143 @@
+# VSP Toolkit/Command-Line Interface (CLI) Design Doc
+
+> This document is in draft status and subject to change or removal.
+
+- **Author(s):** Keifer Furzland
+- **Last Updated:** June 25, 2020
+- **Status:** **Draft** | In Review | Approved
+- **Approvers:** John Paul Ashenfelter [ ], Michael Fleet \[ \], Andrew Gunsch \[ \], Alex Pappas \[ \],
+
+## Overview
+### Objective
+
+We want to answer the following questions:
+
+    Why do we want a command-line interface (CLI)?
+    How do we build & deploy features into a CLI?
+    What infrastructure resources do we use?
+    How is the CLI installed & configured?
+    How could VFS users use the CLI to make development easier?
+
+Only VSP engineers should be releasing "officially supported" code, though it can be an open source tool, of course
+
+The intended audience is VSP software engineers, particularly those on the Operations, FE Tools, and BE Tools teams.
+
+- Build a cohesive set of command line tools used by VFS teams to make development easier.
+- Solving and preventing problems with self-service,
+- Primary product user is VFS engineer, though VSP team(s) will dogfood while building
+
+
+### Background
+
+VSP engineers utilize a wide variety of tools, processes, concepts, and utilities that are scattered about various documents, brains, and
+machines.
+
+For as much as we can, we should aim to build a single source of truth. This will be best for managing/updating code,
+reducing "works on my machine" problems, and provide automatic configuration/support.
+
+### High Level Design - WIP
+
+These are mostly ideas until the first research spike is complete.
+
+- VSP can use to do internal tasks (to dogfood) but goal is to improve VFS teams productivity
+- Configuration file to manage local user configuration
+- Configuration management (write to ~/.vsp/config.yml) for portability and extensibility
+- Single binary install, package management, install from source (make it *easy* and *fool-proof* to install & update &
+    use)
+- Built-in tools for portability (`pkg`, `nodejs`) can reduce headache for cross-platform users, and "just work," though
+- Adds value by allowing us to codify important business practices (running reports, updating config, etc).
+- Integrates w/ other tools across the VSP world
+- Provides a modular design (VFS teams can modify it)
+- Future-proof and scale-friendly - the shell isn't going away, React might, SOCKS config may change (instead of
+    everyone updating `/etc/*` or equiv, they can run `vsp upgrade` and `vsp socks` and be done w/ it)
+- Could provide a webservice for the VFS team to use to query status/outages (is this just /v0/backend_status?)
+- Test user data may be accessible here too, like `vsp service mvi --users --out=mvi-test-users.json`
+- `vsp product:config forms --all --hide-sensitive` would show global VSP and api/site (product) specific configuration
+- `vsp config` - should this be showing config for a specific thing? like "aws configuration" or "vets-api settings.yml"
+- `vsp toolkit:plugin {init, config, install} PLUGIN_NAME` - for building, configuring, installing a new toolkit plugin (with oclif)
+- Indicate somehow that a command is a native plugin or an "extension" i.e. not supported directly by VSP?
+- We can build a process around adding/publishing modules for inclusion in the supported code, maybe
+- We envision this can be leveraged into a web UI by wrapping a common API pattern
+- The RPCs between commands should be consistent schema so we can do standard extensions
+
+
+## Specifics
+
+### Detailed Design - WIP
+
+#### Prototype Plan
+
+- Use [`oclif`](https://oclif.io/docs) to rapidly generate CLI framework
+- One pattern would be to to map the CLI commands to the command pattern in code architecture
+- Prototyping first 'thin layer' proving out the tooling:
+  - `vsp doctor:socks`                   # manage VA SOCKS state/connection - wraps `devops/utils/va.sh`
+  - `vsp services:status`                # see backend service status, planned outages, etc. by hitting the `vets-api` endpoint
+  - `vsp products:site --build-version`  # show the `build.txt` info
+
+After the spike we'll have a prototype usable in further user testing.
+
+### Code Location
+
+- We could either host the `vsp-toolkit` as the core/main library and host git submodules for plugins
+- Plugins *should* contain any dependencies, and this may "inspire rewrites" - which would add tech debt to squeeze a
+- - We could reference dependencies and explicit check for them at runtime/command runtime/vsp doctor, like "does
+    `$VSP_DEVOPS_REPO` exist? good, use` $VSP_DEVOPS_REPO_PATH/scripts/script.sh` or is `va.sh` in `$PATH`, then redirect VSP
+    utils `$CMD` to `va.sh $_`
+
+### Testing Plan
+
+- `oclif` generates tests but we should ensure we're writing unit & integration tests across platforms
+
+### Logging
+
+- N/a
+
+### Debugging
+
+- Include a utility command `--debug` for debug output include system architecture, dependencies versions, etc.
+
+### Caveats
+
+- TBD
+
+### Security Concerns
+
+- Ensure we are properly handling files, permissions, data, memory, performance details
+
+### Privacy Concerns
+
+- This tool shouldn't allow anyone to do anything they inherently wouldn't be able to otherwise. In order to maintain
+    this state, we should consider how platform-wide privacy concerns are addressed. I.e. authorization, authentication,
+    audit-trail. Does the user have least privilege?
+
+### Open Questions and Risks
+
+- Will the majority of our audience be comfortable with this tool?
+- Should we use OCLIF? Or Thor?
+- How can we build a web UI on top of it? SDK-style
+- Allow for multiple languages driving the CLI? Is this possible?
+- Can we wrap application generators/wizards/form builders?
+- We have basically millions of NPM scripts, can we improve discoverability w/o rewriting them all?
+- Wrapping over porting - investigate how we can leverage existing scripts
+- Shelling out (safely) is a not-necessarily bad idea
+- Structure a script folder with endpoints as folders/script filenames?
+
+### Work Estimates
+- June 25 2020: Product Outline & Design Document drafted and out for review
+- June 26 2020: Spike on prototype to explore potential painpoints and flesh out outline/doc
+- July ? : Plan & start work pending stakeholder approval
+- July- Aug: Dogfood and build out uses for internal, existing tools (doctor, utils, metadata, logs, aws connections,
+    etc). (Wrap existing scripts, update where necesessary)
+- August : Have 3-5 useful tools prototyped and ready for a design sprint w/ VFS & VSP engineers
+
+### Alternatives - WIP
+_This section contains alternative solutions to the stated objective, as well as explanations for why they weren't used. In the planning stage, this section is useful for understanding the value added by the proposed solution and why particular solutions were discarded. Once the system has been implemented, this section will inform readers of alternative solutions so they can find the best system to address their needs._
+
+### Future Work - WIP
+_Features you'd like to (or will need to) add but aren't required for the current release. This is a great place to speculate on potential features and performance improvements._
+
+### Revision History
+
+Date | Revisions Made | Author
+-----|----------------|--------
+June 25, 2020 | Added initial draft of design document. | Keifer Furzland

data/exe/vtk

@@ -0,0 +1,18 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+lib_path = File.expand_path('../lib', __dir__)
+$LOAD_PATH.unshift(lib_path) unless $LOAD_PATH.include?(lib_path)
+require 'vtk/cli'
+
+Signal.trap('INT') do
+  warn("\n#{caller.join("\n")}: interrupted")
+  exit(1)
+end
+
+begin
+  Vtk::CLI.start
+rescue Vtk::CLI::Error => e
+  puts "ERROR: #{e.message}"
+  exit 1
+end

data/lib/vtk.rb

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require_relative 'vtk/version'
+
+module Vtk
+  class Error < StandardError; end
+  # Your code goes here...
+end

data/lib/vtk/cli.rb

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+require 'thor'
+
+module Vtk
+  # Handle the application command line parsing
+  # and the dispatch to various command objects
+  #
+  # @api public
+  class CLI < Thor
+    # Error raised by this runner
+    Error = Class.new(StandardError)
+
+    desc 'version', 'vtk version'
+    def version
+      require_relative 'version'
+      puts "v#{Vtk::VERSION}"
+    end
+    map %w[--version -v] => :version
+
+    require_relative 'commands/module'
+    register Vtk::Commands::Module, 'module', 'module [SUBCOMMAND]', 'Command description...'
+  end
+end

data/lib/vtk/command.rb

@@ -0,0 +1,122 @@
+# frozen_string_literal: true
+
+require 'forwardable'
+
+module Vtk
+  # Command class that all command inherit from
+  class Command
+    extend Forwardable
+
+    def_delegators :command, :run
+
+    # Execute this command
+    #
+    # @api public
+    def execute(*)
+      raise(
+        NotImplementedError,
+        "#{self.class}##{__method__} must be implemented"
+      )
+    end
+
+    # The external commands runner
+    #
+    # @see http://www.rubydoc.info/gems/tty-command
+    #
+    # @api public
+    def command(**options)
+      require 'tty-command'
+      TTY::Command.new(options)
+    end
+
+    # The cursor movement
+    #
+    # @see http://www.rubydoc.info/gems/tty-cursor
+    #
+    # @api public
+    def cursor
+      require 'tty-cursor'
+      TTY::Cursor
+    end
+
+    # Open a file or text in the user's preferred editor
+    #
+    # @see http://www.rubydoc.info/gems/tty-editor
+    #
+    # @api public
+    def editor
+      require 'tty-editor'
+      TTY::Editor
+    end
+
+    # File manipulation utility methods
+    #
+    # @see http://www.rubydoc.info/gems/tty-file
+    #
+    # @api public
+    def generator
+      require 'tty-file'
+      TTY::File
+    end
+
+    # Terminal output paging
+    #
+    # @see http://www.rubydoc.info/gems/tty-pager
+    #
+    # @api public
+    def pager(**options)
+      require 'tty-pager'
+      TTY::Pager.new(options)
+    end
+
+    # Terminal platform and OS properties
+    #
+    # @see http://www.rubydoc.info/gems/tty-pager
+    #
+    # @api public
+    def platform
+      require 'tty-platform'
+      TTY::Platform.new
+    end
+
+    # The interactive prompt
+    #
+    # @see http://www.rubydoc.info/gems/tty-prompt
+    #
+    # @api public
+    def prompt(**options)
+      require 'tty-prompt'
+      TTY::Prompt.new(options)
+    end
+
+    # Get terminal screen properties
+    #
+    # @see http://www.rubydoc.info/gems/tty-screen
+    #
+    # @api public
+    def screen
+      require 'tty-screen'
+      TTY::Screen
+    end
+
+    # The unix which utility
+    #
+    # @see http://www.rubydoc.info/gems/tty-which
+    #
+    # @api public
+    def which(*args)
+      require 'tty-which'
+      TTY::Which.which(*args)
+    end
+
+    # Check if executable exists
+    #
+    # @see http://www.rubydoc.info/gems/tty-which
+    #
+    # @api public
+    def exec_exist?(*args)
+      require 'tty-which'
+      TTY::Which.exist?(*args)
+    end
+  end
+end

data/lib/vtk/commands/.gitkeep

@@ -0,0 +1 @@
+#

data/lib/vtk/commands/module.rb

@@ -0,0 +1,24 @@
+# frozen_string_literal: true
+
+require 'thor'
+
+module Vtk
+  module Commands
+    # Interfaces with vets-api modules
+    class Module < Thor
+      namespace :module
+
+      desc 'add <module name>', 'Add a new module to vets-api'
+      method_option :help, aliases: '-h', type: :boolean,
+                           desc: 'Display usage information'
+      def add(name)
+        if options[:help]
+          invoke :help, ['add']
+        else
+          require_relative 'module/add'
+          Vtk::Commands::Module::Add.new(name, options).execute
+        end
+      end
+    end
+  end
+end

data/lib/vtk/commands/module/add.rb

@@ -0,0 +1,31 @@
+# frozen_string_literal: true
+
+require_relative '../../command'
+
+module Vtk
+  module Commands
+    class Module
+      # Adds a new module to vets-api
+      class Add < Vtk::Command
+        attr_accessor :name, :options
+
+        def initialize(name, options)
+          @name = name
+          @options = options
+
+          super()
+        end
+
+        def execute(_input: $stdin, _output: $stdout)
+          create_module name
+        end
+
+        private
+
+        def create_module(name)
+          `rails g module #{name}`
+        end
+      end
+    end
+  end
+end

data/lib/vtk/templates/.gitkeep

@@ -0,0 +1 @@
+#

data/lib/vtk/templates/module/add/.gitkeep

@@ -0,0 +1 @@
+#

data/lib/vtk/version.rb

@@ -0,0 +1,5 @@
+# frozen_string_literal: true
+
+module Vtk
+  VERSION = '0.1.0'
+end

data/vtk.gemspec

@@ -0,0 +1,40 @@
+# frozen_string_literal: true
+
+require_relative 'lib/vtk/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = 'vtk'
+  spec.license       = 'MIT'
+  spec.version       = Vtk::VERSION
+  spec.authors       = ['Eric Boehs', 'Lindsey Hattamer', 'Travis Hilton']
+  spec.email         = ['eric.boehs@oddball.io', 'lindsey.hattamer@oddball.io', 'travis.hilton@oddball.io']
+
+  spec.summary       = 'A CLI for the VSP platform'
+  spec.description   = 'This is a CLI tool for the VSP platform for developer usage'
+  spec.homepage      = 'https://github.com/department-of-veterans-affairs/vsp-toolkit'
+  spec.required_ruby_version = Gem::Requirement.new('>= 2.4.0')
+
+  spec.metadata['homepage_uri'] = spec.homepage
+  spec.metadata['source_code_uri'] = spec.homepage
+  spec.metadata['changelog_uri'] = 'https://github.com/department-of-veterans-affairs/vsp-toolkit/blob/master/CHANGELOG.md'
+
+  # Specify which files should be added to the gem when it is released.
+  # The `git ls-files -z` loads the files in the RubyGem that have been added into git.
+  spec.files = Dir.chdir(File.expand_path(__dir__)) do
+    `git ls-files -z`.split("\x0").reject { |f| f.match(%r{\A(?:test|spec|features)/}) }
+  end
+  spec.bindir        = 'exe'
+  spec.executables   = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ['lib']
+
+  spec.add_dependency 'thor', '> 0.20.3'
+
+  spec.add_development_dependency 'rake', '~> 13.0.0'
+  spec.add_development_dependency 'rspec', '~> 3.10.0'
+  spec.add_development_dependency 'rubocop', '~> 1.6.0'
+  spec.add_development_dependency 'rubocop-rake', '~> 0.5.0'
+  spec.add_development_dependency 'rubocop-rspec', '~> 2.0.0'
+
+  # For more information and examples about making a new gem, checkout our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

metadata

@@ -0,0 +1,160 @@
+--- !ruby/object:Gem::Specification
+name: vtk
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Eric Boehs
+- Lindsey Hattamer
+- Travis Hilton
+autorequire:
+bindir: exe
+cert_chain: []
+date: 2021-01-05 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: thor
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">"
+      - !ruby/object:Gem::Version
+        version: 0.20.3
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">"
+      - !ruby/object:Gem::Version
+        version: 0.20.3
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 13.0.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 13.0.0
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 3.10.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 3.10.0
+- !ruby/object:Gem::Dependency
+  name: rubocop
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 1.6.0
+- !ruby/object:Gem::Dependency
+  name: rubocop-rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.5.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.5.0
+- !ruby/object:Gem::Dependency
+  name: rubocop-rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.0.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 2.0.0
+description: This is a CLI tool for the VSP platform for developer usage
+email:
+- eric.boehs@oddball.io
+- lindsey.hattamer@oddball.io
+- travis.hilton@oddball.io
+executables:
+- vtk
+extensions: []
+extra_rdoc_files: []
+files:
+- ".editorconfig"
+- ".github/workflows/main.yml"
+- ".gitignore"
+- ".rspec"
+- ".rubocop.yml"
+- ".tool-versions"
+- CHANGELOG.md
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- docs/design-doc.md
+- exe/vtk
+- lib/vtk.rb
+- lib/vtk/cli.rb
+- lib/vtk/command.rb
+- lib/vtk/commands/.gitkeep
+- lib/vtk/commands/module.rb
+- lib/vtk/commands/module/add.rb
+- lib/vtk/templates/.gitkeep
+- lib/vtk/templates/module/add/.gitkeep
+- lib/vtk/version.rb
+- vtk.gemspec
+homepage: https://github.com/department-of-veterans-affairs/vsp-toolkit
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://github.com/department-of-veterans-affairs/vsp-toolkit
+  source_code_uri: https://github.com/department-of-veterans-affairs/vsp-toolkit
+  changelog_uri: https://github.com/department-of-veterans-affairs/vsp-toolkit/blob/master/CHANGELOG.md
+post_install_message:
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.4.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.0.8
+signing_key:
+specification_version: 4
+summary: A CLI for the VSP platform
+test_files: []