sct 0.1.14 → 0.1.19

data/.gitignore

@@ -1,12 +0,0 @@
-/.bundle/
-/.yardoc
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-.idea/
-
-# rspec failure tracking
-.rspec_status

data/.rspec

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

data/.travis.yml

@@ -1,7 +0,0 @@
----
-sudo: false
-language: ruby
-cache: bundler
-rvm:
-  - 2.6.2
-before_install: gem install bundler -v 2.0.2

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at reshad@proactive.nl. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
-
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,4 +0,0 @@
-source "https://rubygems.org"
-
-# Specify your gem's dependencies in sct.gemspec
-gemspec

data/Gemfile.lock

@@ -1,48 +0,0 @@
-PATH
-  remote: .
-  specs:
-    sct (0.1.3)
-      class_interface (~> 0.1.1)
-      colored (~> 1.2)
-      commander (~> 4.4.7)
-      highline (>= 1.7.2)
-      hosts (~> 0.1.1)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    class_interface (0.1.1)
-    colored (1.2)
-    commander (4.4.7)
-      highline (~> 2.0.0)
-    diff-lcs (1.3)
-    highline (2.0.3)
-    hosts (0.1.1)
-      linebreak (~> 2.0.1)
-    linebreak (2.0.1)
-    rake (10.5.0)
-    rspec (3.9.0)
-      rspec-core (~> 3.9.0)
-      rspec-expectations (~> 3.9.0)
-      rspec-mocks (~> 3.9.0)
-    rspec-core (3.9.1)
-      rspec-support (~> 3.9.1)
-    rspec-expectations (3.9.0)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-mocks (3.9.1)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.9.0)
-    rspec-support (3.9.2)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bundler (~> 2.0)
-  rake (~> 10.0)
-  rspec (~> 3.0)
-  sct!
-
-BUNDLED WITH
-   2.1.4

data/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2020 Reshad Farid
-
-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

@@ -1,134 +0,0 @@
-# SCT
-The **SCT** command line tool helps developers set up and maintain a Kubernetes (k8s) cluster on their development machine which closely resembles the production setup.
-
-The tool is geared towards the implementation of a local development environment in compliance with the [*Visma Cloud Delivery Model*](https://www.visma.com/blog/our-large-scale-devops-transformation/) (SCT) to be deployed on *Google Cloud Services*.
-
-The SCT tool is a collection of commands that can be run from your local development environment. These commands will take care of some steps necessary to initialize the development environment, but also of some recurring tasks to keep this environment going on a daily base.
-
-This README will provide an installation guide, an overview of the available commands and a brief guide for developers that need to contribute to the **SCT** CLI tool.
-
-The tool is written in Ruby and is meant to run on *Windows, Linux and Mac* environments.
-
-## Installation
-
-1) Open a terminal or bash window and make sure [**Ruby**](https://www.ruby-lang.org/en/documentation/installation/) is installed on your machine with _version >= 2.6.*_
-
-        $ which ruby
-        $ ruby --version
-
-2) As this Ruby Gem is not yet published, you will need to install the *SCT* tool from this repository and use Ruby [**bundler**](https://bundler.io/) to manage dependencies.
-
-        $ gem install bundler
-
-3) Navigate to a (new) folder where you want the SCT code, and clone this repository:
-
-        $ git clone https://github.com/reshadf/sct.git
-
-4) Then let **bundler** manage the dependencies:
-
-        $ bundle
-
-5) And let **gem** create a binary:
-
-        $ gem install sct
-
-6) Now, the **sct** tool is available anywhere from the command line
-
-        $ sct --help
- 
-
-## Usage
-
-SCT offers a number of commands to help developers set up a local development environment for Visma Cloud To get an overview of what **sct** can do, run
-
-    $ sct --help
-
-To initialize a **sct** configuration file
-
-    $ sct init
-
-To patch the hostfile with the local IP of the k8s cluster:
-
-    $ sct hostfile
-
-To add the secret for the MySQL proxy:
-
-    $ sct mysql_proxy
-
-
-## Development
-
-For development of the **sct** tool, the installation needs to be a bit different.
-
-Repeat steps 1-3 from the installation instruction above.
-
-4) We will use [**rake**](https://github.com/ruby/rake) as a Ruby develoment tool for running tests and generating binaries:
-
-        $ gem install rake
-
-5) Use the setup script from the repo to install dependencies:
-
-        $ bin/setup
-
-5) Do tests to make sure everything works fine before you start:
-
-        $ rake spec
-
-6) Install dependency gems:
-
-        $ bundle exec rake install
-
-7) Your development environment is now ready. After you have made edits to the code, you can generate a new binary to test the code like this:
-
-        $ rake install
-
-8) You can then run the binary directly from the command line:
-
-        $ sct --help
-
-### Development tips
-
-- To release a new version, update the version number in `version.rb`, and then run:
-
-        $ bundle exec rake release
-
-    This will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
-
-### Adding commands
-
- Adding a new command is as simple as adding a new 'Command' Class to the *lib/sct/commands* folder. As long as you implement the constants and methods of  *lib/sct/command_interface.rb*, your new Command will automatically appear in the CLI Help and can be called. Use the *lib/sct/command_option.rb* to define command options. Examples of Command Classes can be found inside the *lib/sct/commands* folder.
-
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://gitlab.com/proactive-software/packages/sct. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
-
-## Releasing
-
-#### Ownership
-Owners of the Ruby Gem project are able to release a new version. You can check the ownership status at https://rubygems.org/gems/sct. If you are an owner you can continue with the following steps. If not you may request to become an owner, or ask an existing owner to do the release for you. 
-
-#### Authentication
-Owners should update their credentials once before they can actually release new versions. The steps to do this are:
-```$bash
-curl -u [YOUR-RUBYGEM-USERNAME] https://rubygems.org/api/v1/api_key.yaml > ~/.gem/credentials
-chmod 0600 ~/.gem/credentials
-```
-
-### Release steps
-#### Update version
-Before releasing you are required to update the version of the new release. You can do this manually by incrementing the value in the file `./sct/lib/sct/version.rb`. After this you need to commit this change and push it to the master branch.
-
-#### Release
-You are now ready to release. You can do this with a simple command in the SCT repository's root directory:
-```$xslt
-rake release
-```
-
-## License
-
-The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
-
-## Code of Conduct
-
-Everyone interacting in the Sct project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://gitlab.com/proactive-software/packages/sct/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -1,6 +0,0 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec

data/lib/sct.rb

@@ -1,61 +0,0 @@
-require 'sct'
-require "sct/config"
-require 'sct/command'
-require "sct/version"
-require 'colored'
-require 'commander'
-
-module Sct
-  class SctCore
-
-    program :name, 'sct'
-      program :version, Sct::VERSION
-      program :summary, 'CLI helper tool for local SCT development'
-      program :description, 'SCT is a CLI tool for developers using the Visma Continuous Deployment Model in conjunction with the Google Cloud Platform (GCP). It provides multiple command to set up and maintain a kubernetes cluster on a machine for local development'
-
-    def self.take_off(cmds)
-      self.new.run
-      cmds.each { |cmd| registerCommand(cmd) }
-    end
-
-    def run 
-      
-    end
-
-    def self.registerCommand(cmd)
-      # validate Command Class
-      if cmd.class != Class ||
-        !cmd.name.end_with?('Command')
-        return
-      end
-    
-      # validate if Command is meant to be public
-      if !cmd::IS_PUBLIC_COMMAND
-        return
-      end
-    
-      # register public Commands as CLI command
-      command self.deduceCommandNameFromClass(cmd) do |c|
-        c.syntax = cmd::SYNTAX
-        c.summary = cmd::SUMMARY
-        c.description = cmd::DESCRIPTION
-        c.example cmd::EXAMPLE_DESCRIPTION, cmd::EXAMPLE
-        cmd::OPTIONS.each { |option| c.option option.name, option.type, option.description }
-        c.action do |args, options|
-          cmd.new.execute(args, options)
-        end
-      end
-    end
-
-    # retrieves cli command-name from Command's full Class name
-    def self.deduceCommandNameFromClass(c)
-      name = c.name
-      if name.include?('::')
-        name = name.partition('::')[2]
-      end
-      # TODO replace camel-case capitals with '-'
-      return name.chomp('Command').downcase
-    end
-
-  end
-end

data/lib/sct/command_interface.rb

@@ -1,18 +0,0 @@
-require 'class_interface'
-
-class CommandInterface
-  IS_PUBLIC_COMMAND = true | false
-  SYNTAX = String
-  SUMMARY = String
-  DESCRIPTION = String
-  EXAMPLE = String
-  EXAMPLE_DESCRIPTION = String
-  OPTIONS = Array
-
-  def initialize
-  end
-
-  def execute(args, options)
-  end
-
-end

data/lib/sct/command_option.rb

@@ -1,14 +0,0 @@
-module Sct
-
-  class CommandOption
-    attr_reader :name, :type, :description
-
-    def initialize(name, type, description)
-      @name = name
-      @type = type
-      @description = description
-    end
-
-  end
-
-end

data/lib/sct/commands/cluster.rb

@@ -1,121 +0,0 @@
-require 'sct/command_interface'
-
-module Sct
-
-    class ClusterCommand
-
-        IS_PUBLIC_COMMAND = true
-        SYNTAX = 'sct cluster up | sct cluster down | sct cluster reset | sct cluster update-config'
-        SUMMARY = 'Starts/stops/resets or updates the config of the minikube cluster.'
-        EXAMPLE = 'sct cluster up | sct cluster down | sct cluster reset | sct cluster update-config'
-        EXAMPLE_DESCRIPTION = 'Starts/stops/resets or updates the config of the minikube cluster.'
-        DESCRIPTION = "sct cluster allows you to start, stop, reset or update the config of the Spend Cloud minikube cluster."
-
-        OPTIONS = []
-
-        def execute(args, options)
-            return puts "SCT has not been initialized. Run 'sct init' first.".red unless Sct::Config.exists
-
-            case args[0]
-                when "up"
-                    up
-                when "down"
-                    down
-                when "update-config"
-                    update_config
-                when "reset"
-                    reset
-                else
-                    puts "Unknown or missing argument. Please run 'sct cluster up','sct cluster down' or 'sct cluster update-config'".red
-            end
-        end
-
-        def up
-            start
-            system "kubectl delete pod -n kube-system $(kubectl get pods -n kube-system | grep registry-creds | awk '{print $1}')"
-            system "kubectl rollout status -n kube-system deployment/registry-creds"
-            post_start
-        end
-
-        def down
-            system "#{minikube} stop"
-        end
-
-        def update_config
-            if Sct::Helpers.operatingSystem == Sct::Helpers::WINDOWS
-                windows_home_path = Sct::Helpers.windowsHomePath
-                kube_file_path = windows_home_path+"/.kube/config"
-
-                if !File.exists?(kube_file_path)
-                    return puts "#{kube_file_path} doesn't exist".red
-                end
-
-                system("sed -e 's~\\\\~/~g' -e 's~C:~/mnt/c~g' < #{kube_file_path} > ~/.kube/minikube-config")
-
-                puts "#{kube_file_path} copied to ~/.kube/minikube-config".green
-            end
-
-            system "kubectl config use-context minikube"
-        end
-
-        def reset
-            system "#{minikube} delete"
-            start
-            system "kubectl create secret generic gcloud-credentials --from-file=\"$(echo ~)/.config/gcloud/application_default_credentials.json\""
-            system "kubectl create secret generic -n kube-system registry-creds-dpr --from-literal DOCKER_PRIVATE_REGISTRY_PASSWORD=changeme --from-literal DOCKER_PRIVATE_REGISTRY_SERVER=changeme --from-literal DOCKER_PRIVATE_REGISTRY_USER=changeme"
-            system "kubectl patch secret -n kube-system registry-creds-dpr -p='{\"metadata\": {\"labels\": { \"app\": \"registry-creds\", \"cloud\": \"dpr\", \"kubernetes.io/minikube-addons\": \"registry-creds\"}}}'"
-            system "kubectl create secret generic -n kube-system registry-creds-ecr --from-literal AWS_ACCESS_KEY_ID=changeme --from-literal AWS_SECRET_ACCESS_KEY=changeme --from-literal AWS_SESSION_TOKEN=\"\" --from-literal aws-account=changeme --from-literal aws-assume-role=changeme --from-literal aws-region=changeme"
-            system "kubectl patch secret -n kube-system registry-creds-ecr -p='{\"metadata\": {\"labels\": { \"app\": \"registry-creds\", \"cloud\": \"ecr\", \"kubernetes.io/minikube-addons\": \"registry-creds\"}}}'"
-            system "kubectl create secret generic -n kube-system registry-creds-gcr --from-file=\"$(echo ~)/.config/gcloud/application_default_credentials.json\" --from-literal=gcrurl=\"https://eu.gcr.io\""
-            system "kubectl patch secret -n kube-system registry-creds-gcr -p='{\"metadata\": {\"labels\": { \"app\": \"registry-creds\", \"cloud\": \"gcr\", \"kubernetes.io/minikube-addons\": \"registry-creds\"}}}'"
-            system "kubectl create secret generic -n kube-system registry-creds-acr --from-literal ACR_PASSWORD=changeme --from-literal ACR_CLIENT_ID=changeme --from-literal ACR_URL=changeme"
-            system "kubectl patch secret -n kube-system registry-creds-acr -p='{\"metadata\": {\"labels\": { \"app\": \"registry-creds\", \"cloud\": \"acr\", \"kubernetes.io/minikube-addons\": \"registry-creds\"}}}'"
-            system "#{minikube} addons enable registry-creds"
-            system "#{minikube} addons enable ingress"
-            system "kubectl rollout status -n kube-system deployment/registry-creds"
-            system "kubectl rollout status -n kube-system deployment/nginx-ingress-controller"
-            wait_for_gcr_secret
-            system "kubectl apply -f ~/development/spend-cloud/k8s/"
-            post_start
-        end
-
-        def start
-            system "#{minikube} start --cpus=$(cat /proc/cpuinfo | grep processor | wc -l) --memory=16G"
-            system "#{minikube} ssh -- 'sudo su -c \"echo 10048576 > /proc/sys/fs/inotify/max_user_watches\"'"
-            update_config
-        end
-
-        def post_start
-            system "kubectl rollout status deployment/spend-cloud-api"
-            system "sudo sct hostfile"
-            puts "\n✔️ You can visit your environment at 👉 https://spend-cloud.spend.cloud.local 👌 (might still take a few minutes)"
-        end
-
-        def wait_for_gcr_secret
-            puts "Waiting for Google Cloud Registry secret to become available...".yellow
-
-            while true
-                secrets = `kubectl get secrets`
-
-                if secrets.include? "gcr-secret"
-                    puts "Google Cloud Registry secret is now available.".green
-                    break
-                else
-                    sleep 1
-                end
-            end
-        end
-
-        def minikube
-            if Sct::Helpers.operatingSystem == Sct::Helpers::WINDOWS
-                return "minikube.exe"
-            else
-                return "minikube"
-            end
-        end
-
-        implements CommandInterface
-
-    end
-
-end