norad_cli 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: f67e3b7d29e50815d288e17ba88cf0791e5cc808
+  data.tar.gz: b1b7675b3bab7237fc7cfa9b094181d9918cbb29
+SHA512:
+  metadata.gz: 24c52f33dd524c6057465193569229968f3eb90e48963a530919191450e91b504d6112bfaacbad903e95259d61590eb72ed6e35e4911884a9d6b692948c0c2ec
+  data.tar.gz: bf5fb027e9df8357164c6c9971b24a5db7077ed822fcb5d7eff24220199028f061811e247923fc82b35e9ece3121bd06f246225aecb659c9dd2beee27472d2e6

data/.gitignore

@@ -0,0 +1,9 @@
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/

data/.gitlab-ci.yml

@@ -0,0 +1,43 @@
+stages:
+  - static_analysis
+  - security_test
+#  - behavior_test
+  - release
+
+image: ruby:2.3.3
+
+cache:
+  key: "$CI_BUILD_NAME"
+  paths:
+    - vendor/bundle
+
+before_script:
+  - bundle install --jobs=4 --with development
+
+rubocop:
+  stage: static_analysis
+  script: bundle exec rubocop
+
+bundle_audit:
+  stage: security_test
+  script: bundle exec bundle-audit check --update
+
+#rspec:
+#  stage: behavior_test
+#  script: bundle exec rspec
+
+publish:
+  stage: release
+  script:
+    - echo "---" > ~/.gem/credentials
+    - COLON=':' && echo "${COLON}rubygems_api_key${COLON} ${RUBYGEMS_API_KEY}" >> ~/.gem/credentials
+    - git config --global user.email "norad.dev@gmail.com"
+    - git config --global user.name "Norad Release"
+    - git config --global push.default simple
+    - chmod 0600 ~/.gem/credentials
+    - bundle exec rake build
+    - bundle exec rake release:guard_clean
+    - gem push `ls ./pkg/norad_cli-*.gem`
+    - rm -fr ~/.gem
+  only:
+    - master

data/.rspec

@@ -0,0 +1,2 @@
+--format documentation
+--color

data/.rubocop.yml

@@ -0,0 +1,34 @@
+AllCops:
+  TargetRubyVersion: 2.3
+  DisplayCopNames: true
+  Exclude:
+    - 'lib/norad_cli/templates/spec/**/*'
+Documentation:
+  Enabled: false
+Metrics/LineLength:
+  Max: 120
+  Exclude:
+    - 'lib/norad_cli/support/api_security_container_seed_script.rb'
+    - 'lib/norad_cli/cli/sectest.rb'
+Metrics/MethodLength:
+  Exclude:
+    - 'lib/norad_cli/support/api_security_container_seed_script.rb'
+    - 'lib/norad_cli/cli/sectest.rb'
+Metrics/AbcSize:
+  Exclude:
+    - 'lib/norad_cli/support/api_security_container_seed_script.rb'
+    - 'lib/norad_cli/cli/sectest.rb'
+Metrics/BlockLength:
+  Exclude:
+    - 'spec/**/*'
+    - 'lib/norad_cli/cli/sectest.rb'
+Metrics/ClassLength:
+  Exclude:
+    - 'lib/norad_cli/cli/sectest.rb'
+Style/NegatedIf:
+  Exclude:
+    - 'lib/norad_cli/cli/sectest.rb'
+Security/YAMLLoad:
+  Exclude:
+    - 'lib/norad_cli/support/manifest.rb' 
+    - 'lib/norad_cli/support/api_security_container_seed_script.rb'

data/.ruby-gemset

@@ -0,0 +1 @@
+norad-gem

data/.ruby-version

@@ -0,0 +1 @@
+2.3.3

data/.travis.yml

@@ -0,0 +1,5 @@
+sudo: false
+language: ruby
+rvm:
+  - 2.3.0
+before_install: gem install bundler -v 1.12.5

data/CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# How to contribute
+
+This guide is meant to provide guidelines for how to contribute to the Norad CLI project. These
+procedures should work in the majority of cases. At times, it will be necessary to step outside of
+these guidelines and Do What Makes Sense. This is an living document that we can continue to modify
+as we define the process that helps us add code quickly and safely.
+
+## Getting Started
+
+* If you haven't already, you'll want to set up a [development box](https://gitlab.cisco.com/norad/dev-box).
+  This provides a consistent environment for running tests.
+* We use [rubocop](https://github.com/bbatsov/rubocop) to enforce code quality and style guidelines.
+  You can familiarize yourself with the [style guide](https://github.com/bbatsov/ruby-style-guide).
+  You can also install a tool into your editor which will help you follow the style guideline. One
+  for vim can be found [here](https://github.com/scrooloose/syntastic).
+
+## Making Changes
+
+Fundamentally, we follow the Github Flow(1) methodology for branching and committing code. The
+process essentially breaks down as follows:
+
+1. Assign the feature you are beginning to work on to yourself in JIRA.
+2. Create a feature branch off of the master branch. Note that anything in master is always
+   deployable, so this branch will always have the latest code. Branch names should be descriptive.
+3. Your branch is your branch. Feel free to experiment and commit freely. You may wish to make your
+   life easier when it's time to merge into master by learning about [auto-squashing
+   commits](https://robots.thoughtbot.com/autosquashing-git-commits).[^1]
+4. You are free to push the feature branch to the origin as freqently as you wish. This will run the
+   CI suite. You can also run the test suite locally on your dev box. By pushing to the feature
+   branch, you can engage other engineers on the team if you need help. They can checkout your
+   branch and examine the code.
+5. When your feature is done, open a Merge Request in Gitlab.
+
+At this point in process, there is no requirement of any kind for your commit messages. Before
+merging into master, though, you will need a "good commit message" for any commits that aren't being
+squashed. Links to further reading on this topic are available in the Additional Resources section.
+
+## Submitting Changes
+
+When your feature is ready, or is at a state where you'd like to formally begin engaging the rest of
+the team, create a [Merge Request](https://gitlab.cisco.com/norad/norad/merge_requests)
+in Gitlab. Please write a meaningful title and detailed description that provides an overview of
+What your feature does and Why it does it. You can leave it to the code itself to explain the How,
+but feel free to call anything out here that you would like the reviewer(s) to pay special attention
+to.  If you feel that someone in particular needs to look at your Merge Request, you may assign the
+MR to them. Mentioning someone in the Merge Request description is another way to alert someone in
+particular you'd like for them to look at your MR, e.g. ```cc @bmanifol```.
+
+**ProTips**
+
+* Gitlab will autofill the title and description with your most recent commit when opening the Merge
+Request. So, writing a good commit for your last commit before opening the Merge Request can help
+you kill two birds with one stone.
+
+## Code Review Process
+
+The Code Review Process is meant to be an open-ended discussion about the feature that is being
+committed. It should address whether the changeset meets the requirements of the feature as well as
+the quality of the code itself. The reviewer(s) should also make sure that the feature includes an
+adequate number of meaningful tests.
+
+Please be polite in both giving and receiving feedback. Remember that it's a review of the code, not
+an individual. As a reviewer, do your best to separate your personal opinion of how you would do
+something from what is objectively constructive criticism. Please review the Thoughtbot guide for
+Code Reviews in the Additional Resources section (3).
+
+Make any changes to your feature branch that you and the reviewer agree should be made, and push
+those changes to your feature branch. This will automatically update your Merge Request. Repeat this
+process until the Merge Request is approved.
+
+The merge request must receive at least one **+1** before it can be merged. If individuals are
+called out to look at something during any point of the review process, they will need to provide a
+**+1** as well before it can be merged.
+
+## Merge Process
+
+Your feature got approved! Great! Now it's time to merge into master.
+
+1. Before code can be merged to master, **all tests must be passing**. In other words, you need a
+   green check from Gitlab CI.
+2. In order to keep the master branch's commit history clean, you may be required to rebase your
+   feature branch before it can be merged. This is a loose a requirement, but please consider
+   squashing interim commits into one or more block commits. The goal here is to keep the master
+   branch devoid of commits such as "fixing typo" or "trying out this method." To rebase, run the
+   following on your freature branch: ```git rebase -i origin/master```. See the additional
+   resources for more information on rebasing.
+3. After (force) pushing your rebased feature branch, the Merge Request can be merged **as long as
+   all tests still pass**.
+
+# Additional Resources
+
+1. [Github Flow](https://guides.github.com/introduction/flow/)
+2. [Code Review Guide](https://github.com/thoughtbot/guides/tree/master/code-review)
+3. [Style Guide](https://github.com/bbatsov/ruby-style-guide)
+4. [Git Tips](https://github.com/thoughtbot/guides/blob/master/protocol/git)
+5. [Git Rebase](https://help.github.com/articles/about-git-rebase/)
+6. [Auto-squashing Git Commits](https://robots.thoughtbot.com/autosquashing-git-commits)
+7. [Good Commit Messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
+8. [More Good Commit Messages](http://chris.beams.io/posts/git-commit/)
+9. [Even More Good Commit Messages](http://www.alexkras.com/19-git-tips-for-everyday-use/#good-commit-message)
+
+[^1]: Some background and additional reading on squashing commits. [Squashing Commits with Git](https://davidwalsh.name/squash-commits-git) deals with squashing commits in a feature branch. [git rebase --autosquash](https://coderwall.com/p/hh-4ea/git-rebase-autosquash) picks up where the previous article leaves off and explains how the "git rebase" option "--autosquash" complements squashing commits.

data/Gemfile

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

data/LICENSE

@@ -0,0 +1,201 @@
+                              Apache License
+                        Version 2.0, January 2004
+                     http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "{}"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright 2015 Cisco Systems, Inc.
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,119 @@
+# Norad
+
+The norad gem is a command line interface (CLI) to create new security tests and interface with an instance of norad.  Currently, the project only contains code to create new security tests.
+
+## Dependencies
+
+To use this tool to create new security tests, the only dependencies is Docker.  The easiest way to install Docker is through the community edition.
+
+[Docker Community Edition](https://www.docker.com/community-edition)
+
+The above site contains all the necessary information to install Docker on a Mac, Windows, or Linux machines.
+
+## Installation
+
+This utility can be installed simply by:
+
+```
+$ gem install norad
+```
+
+Once installed, a norad executable should be available.
+
+## Usage
+
+The norad executable has several subcommands to aid a developer in creating security tests.  The tool contains a help interface to provide information about the available subcommand and options.  An example of the available help:
+
+```
+$ norad help
+Commands:
+  norad help [COMMAND]     # Describe available commands or one specific command
+  norad repo <command>     # Commands for norad security repos housing security tests.
+  norad sectest <command>  # Commands to create new security tests. 
+```
+
+Additional help for subcommands (e.g. repo or sectest) is available by:
+
+```
+$ norad repo help
+Commands:
+  norad repo create REPONAME  # Create a new norad security test repository called REPONAME
+  norad repo help [COMMAND]   # Describe subcommands or one specific subcommand
+
+```
+
+Individual help for a command is available with:
+
+```
+$ norad repo create --help
+Usage:
+  norad create REPONAME
+
+Create a new norad security test repository called REPONAME
+```
+
+### Repo Subcommand
+
+The repo subcommand creates a new git repository to house new security tests.  It is a helper command which ensures new repositories conform to standard layout and ci best practices.  To create a new repository for housing multiple security tests:
+
+```
+$ norad repo create asig-security
+Initializing a new norad security test repository
+      create  asig-security/base
+      create  asig-security/spec
+License the repo under Apache 2? y
+Who is the copyright holder (Default: Cisco Systems, Inc.)?
+      create  asig-security/LICENSE
+      create  asig-security/.gitlab.ci.yml
+      create  asig-security/.gitignore
+      create  asig-security/CONTRIBUTING.md
+      create  asig-security/README.md
+```
+
+The user will be prompted whether to license the code under Apache 2 and for the copyright holder.  The norad framework is released under the Apache 2 license, test content is not required to be licensed the same. 
+
+As shown, a new directory, asig-security, has been created and multiple files created.  Changing directory into asig-security and running git status shows a new git repository waiting for an initial commit:
+
+```
+$ git status
+On branch master
+
+Initial commit
+
+Untracked files:
+  (use "git add <file>..." to include in what will be committed)
+
+    .gitignore
+    .gitlab.ci.yml
+    CONTRIBUTING.md
+    LICENSE
+    README.md
+
+nothing added to commit but untracked files present (use "git add" to track)
+```
+
+The repo command is only useful when starting an entirely new repository to house multiple security tests!  For general security test development inside of an existing repository see the below sectest subcommand.
+
+### Sectest Subcommand
+
+The sectest subcommand is where general security test tool development occurs.  The sectest subcommand can scaffold a new security test, build security test docker images, test images, execute a security test, and create a seed file for important into a Norad instance.  A listing of the current commands is:
+
+```
+$ norad help sectest
+Commands:
+  norad sectest build SECTESTNAME              # Builds the docker image for the security test SECTESTNAME
+  norad sectest build:all SECTESTNAME          # Builds all images for security test SECTESTNAME
+  norad sectest build:specs SECTESTNAME        # Builds the spec images for the security test SECTESTNAME
+  norad sectest execute SECTESTNAME ARGUMENTS  # Executes the specified security test SECTESTNAME w/ ARGUMENTS
+  norad sectest help [COMMAND]                 # Describe subcommands or one specific subcommand
+  norad sectest scaffold TESTNAME              # Create a new security test with standard files + testing
+  norad sectest seed                           # Create the containers.rb seed to import into the api
+  norad sectest spec SECTESTNAME               # Run the rspec tests for security tool SECTESTNAME
+```
+
+## Development
+
+## Contributing
+
+Bug reports and pull requests are welcome on Gitlab at https://gitlab.com/norad/cli
+

data/Rakefile

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec

data/bin/console

@@ -0,0 +1,15 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'bundler/setup'
+require 'norad'
+
+# 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

data/bin/norad

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby -U
+# frozen_string_literal: true
+
+require 'norad_cli'
+
+NoradCli::CLI.start(ARGV)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/norad_cli/cli/main.rb

@@ -0,0 +1,12 @@
+# frozen_string_literal: true
+require 'thor'
+require 'norad_cli/cli/secrepo'
+require 'norad_cli/cli/sectest'
+
+module NoradCli
+  class CLI < Thor
+    # Register all of the subcommands
+    register(Repo, 'repo', 'repo <command>', 'Commands for norad security repos housing security tests.')
+    register(Sectest, 'sectest', 'sectest <command>', 'Commands to create new security tests.')
+  end
+end

data/lib/norad_cli/cli/secrepo.rb

@@ -0,0 +1,46 @@
+# frozen_string_literal: true
+require 'thor'
+require 'git'
+require 'docker'
+
+class Repo < Thor
+  include Thor::Actions
+
+  def self.source_root
+    File.join(File.dirname(File.expand_path(__FILE__)), '../templates/')
+  end
+
+  # rubocop:disable Metrics/AbcSize
+  # rubocop:disable Metrics/MethodLength
+  desc 'create REPONAME', 'Create a new norad security test repository called REPONAME'
+  def create(repo_name)
+    say 'Initializing a new norad security test repository'
+
+    # Initialize a new git repository
+    Git.init(repo_name)
+
+    # Create the necessary directories
+    %w(base spec).each do |dirrepo_name|
+      empty_directory "#{repo_name}/#{dirrepo_name}"
+    end
+
+    # Ask about licensing
+    if yes?('License the repo under Apache 2?')
+      options[:year] = Date.today.year
+      options[:company] = ask('Who is the copyright holder (Default: Cisco Systems, Inc.)?')
+      options[:company] = 'Cisco Systems, Inc.' if options[:company].empty?
+      template 'LICENSE.erb', "#{repo_name}/LICENSE"
+    end
+
+    # Copy the necessary root files
+    copy_file 'ci/.gitlab.ci.yml', "#{repo_name}/.gitlab.ci.yml"
+    copy_file '.gitignore', "#{repo_name}/.gitignore"
+    copy_file 'CONTRIBUTING.md', "#{repo_name}/CONTRIBUTING.md"
+    copy_file 'README.md', "#{repo_name}/README.md"
+
+    # Copy the spec helper
+    copy_file 'spec/spec_helper.rb', "#{repo_name}/spec/spec_helper.rb"
+  end
+  # rubocop:enable Metrics/AbcSize
+  # rubocop:enable Metrics/MethodLength
+end