cpl 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 2392653f1a75e0dc398590cc5c0e9d89d4769a50af3432b2861e01ff794e8cda
+  data.tar.gz: 13c33cc6465394b90b1fd8e94f711c98135bfdcb25756db7d3b7b0c8bfc819fa
+SHA512:
+  metadata.gz: bc2b5f2555b8f329ad8d5b2be9f5762e6f265f499baaa035e65c24257b47c26459842f2611ee8d352af65b3dcabf4f0e6570007c59f5ca543f3edb382ed04747
+  data.tar.gz: 904028e00550311c8b9327fb3a17a8a00c75b4806e81ca8359d5b3f6ae55b19f8a89efbc3ccc087e4f62e2243930587df1f693ebbbac9470377b0e6905e0dd19

data/.github/workflows/ci.yml

@@ -0,0 +1,60 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+jobs:
+  rubocop:
+    runs-on: ubuntu-latest
+    name: Rubocop
+    strategy:
+      matrix:
+        ruby:
+          - "2.7"
+          - "3.0"
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          rubygems: latest
+      - name: Install dependencies
+        run: bundle install
+      - name: Analyze code
+        run: bundle exec rubocop
+
+  rspec:
+    needs: rubocop
+    runs-on: ubuntu-latest
+    name: RSpec
+    env:
+      RAILS_ENV: test
+    strategy:
+      matrix:
+        ruby:
+          - "2.7"
+          - "3.0"
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: ${{ matrix.ruby }}
+          rubygems: latest
+          bundler-cache: false
+      - name: Install dependencies
+        run: bundle install
+      - name: Run tests
+        run: bundle exec rspec spec
+      - name: Upload coverage results
+        uses: actions/upload-artifact@master
+        if: always()
+        with:
+          name: coverage-report
+          path: coverage

data/.gitignore

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

data/.rspec

@@ -0,0 +1 @@
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,16 @@
+require:
+  - rubocop-rake
+  - rubocop-rspec
+
+AllCops:
+  TargetRubyVersion: 2.7
+  NewCops: enable
+
+Metrics/AbcSize:
+  Enabled: false
+
+Style/Documentation:
+  Enabled: false
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2023-02-08
+
+- Initial release

data/CONTRIBUTING.md

@@ -0,0 +1,12 @@
+# Contributing
+
+## Linting
+Be sure to run `rubocop -a` before committing code.
+
+## Debugging
+
+1. Install gem: `gem install debug`
+2. Require: Add a `require "debug"` statement to the file you want to debug.
+3. Add breakpoint: Add a `debugger` statement to the line you want to debug.
+4. Modify the `lib/command/test.rb` file to triggger the code that you want to run.
+5. Run the test in your test app with a `.controlplane` directory. `cpl test -a my-app-name`

data/Gemfile

@@ -0,0 +1,7 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+gemspec
+
+gem "rake", "~> 13.0"

data/Gemfile.lock

@@ -0,0 +1,104 @@
+PATH
+  remote: .
+  specs:
+    cpl (0.1.0)
+      cgi (~> 0.3.6)
+      debug (~> 1.7.1)
+      dotenv (~> 2.8.1)
+      json (~> 2.6.3)
+      net-http (~> 0.3.2)
+      pathname (~> 0.2.1)
+      psych (~> 5.1.0)
+      tempfile (~> 0.1.3)
+      thor (~> 1.2.1)
+      yaml (~> 0.2.1)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.2)
+    cgi (0.3.6)
+    debug (1.7.1)
+      irb (>= 1.5.0)
+      reline (>= 0.3.1)
+    diff-lcs (1.5.0)
+    docile (1.4.0)
+    dotenv (2.8.1)
+    io-console (0.6.0)
+    irb (1.6.2)
+      reline (>= 0.3.0)
+    json (2.6.3)
+    net-http (0.3.2)
+      uri
+    parallel (1.22.1)
+    parser (3.2.0.0)
+      ast (~> 2.4.1)
+    pathname (0.2.1)
+    psych (5.1.0)
+      stringio
+    rainbow (3.1.1)
+    rake (13.0.6)
+    regexp_parser (2.6.2)
+    reline (0.3.2)
+      io-console (~> 0.5)
+    rexml (3.2.5)
+    rspec (3.12.0)
+      rspec-core (~> 3.12.0)
+      rspec-expectations (~> 3.12.0)
+      rspec-mocks (~> 3.12.0)
+    rspec-core (3.12.1)
+      rspec-support (~> 3.12.0)
+    rspec-expectations (3.12.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-mocks (3.12.3)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.12.0)
+    rspec-support (3.12.0)
+    rubocop (1.45.0)
+      json (~> 2.3)
+      parallel (~> 1.10)
+      parser (>= 3.2.0.0)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 1.8, < 3.0)
+      rexml (>= 3.2.5, < 4.0)
+      rubocop-ast (>= 1.24.1, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 2.4.0, < 3.0)
+    rubocop-ast (1.24.1)
+      parser (>= 3.1.1.0)
+    rubocop-capybara (2.17.0)
+      rubocop (~> 1.41)
+    rubocop-rake (0.6.0)
+      rubocop (~> 1.0)
+    rubocop-rspec (2.18.1)
+      rubocop (~> 1.33)
+      rubocop-capybara (~> 2.17)
+    ruby-progressbar (1.11.0)
+    simplecov (0.22.0)
+      docile (~> 1.1)
+      simplecov-html (~> 0.11)
+      simplecov_json_formatter (~> 0.1)
+    simplecov-html (0.12.3)
+    simplecov_json_formatter (0.1.4)
+    stringio (3.0.5)
+    tempfile (0.1.3)
+    thor (1.2.1)
+    unicode-display_width (2.4.2)
+    uri (0.12.0)
+    yaml (0.2.1)
+
+PLATFORMS
+  x86_64-linux
+
+DEPENDENCIES
+  cpl!
+  rake (~> 13.0)
+  rspec (~> 3.12.0)
+  rubocop (~> 1.45.0)
+  rubocop-rake (~> 0.6.0)
+  rubocop-rspec (~> 2.18.1)
+  simplecov (~> 0.22.0)
+
+BUNDLED WITH
+   2.4.6

data/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 ShakaCode
+
+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,318 @@
+# Heroku to Control Plane
+
+_A playbook for migrating from [Heroku](https://heroku.com) to [Control Plane](https://controlplane.com)_
+
+This playbook shows how to move "Heroku apps" to "Control Plane workloads" via an open-source `cpl` CLI on top of Control Plane's `cpln` CLI.
+
+Heroku provides a UX and CLI that enables easy publishing of Ruby on Rails and other apps. This ease of use comes via many "Heroku" abstractions and naming conventions.
+Control Plane, on the other hand, gives you access to raw cloud computing power. However, you need to know precisely how to use it.
+
+To simplify migration to and usage of Control Plane for Heroku users, this repository provides a **concept mapping** and a **helper CLI** based on templates to save lots of day-to-day typing (and human errors).
+
+1. [Key features](#key-features)
+2. [Concept mapping](#concept-mapping)
+3. [Installation](#installation)
+4. [Example CLI flow for application build/deployment](#example-cli-flow-for-application-builddeployment)
+5. [Example project modifications for Control Plane](#example-project-modifications-for-control-plane)
+6. [Environment](#environment)
+7. [Database](#database)
+8. [In-memory databases](#in-memory-databases)
+9. [CLI commands reference](#cli-commands-reference)
+10. [Mapping of Heroku Commands to `cpl` and `cpln`](#mapping-of-heroku-commands-to-cpl-and-cpln)
+11. [Examples](#examples)
+12. [Migrating Postgres database from Heroku infrastructure](/postgres.md)
+13. [Migrating Redis database from Heroku infrastructure](/redis.md)
+
+## Key features
+
+- A `cpl` command to complement the default Control Plane `cpln` command with "Heroku style scripting." The Ruby source can serve as inspiration for your own scripts.
+- Easy to understand Heroku to Control Plane conventions in setup and naming.
+- **Safe, production-ready** equivalents of `heroku run` and `heroku run:detached` for Control Plane.
+- Automatic sequential release tagging for Docker images.
+- A project-aware CLI which enables working on multiple projects.
+
+## Concept mapping
+
+On Heroku, everything runs as an app, which means an entity that:
+
+1. Runs code from a Git repo
+2. Runs several process types, as defined in the `Procfile`
+3. Has dynos, which are Linux containers that run these process types
+4. Has add-ons, including the database and other services
+5. Has common environment variables
+
+On Control Plane, we can map a Heroku app to a GVC (Global Virtual Cloud). Such a cloud consists of workloads, which can be anything that can run as a container.
+
+**Mapping of Concepts:**
+
+| Heroku           | Control Plane                               |
+| ---------------- | ------------------------------------------- |
+| _app_            | _GVC_ (Global Virtual Cloud)                |
+| _dyno_           | _workload_                                  |
+| _add-on_         | either a _workload_ or an external resource |
+| _review app_     | _GVC (app)_ in staging _organization_       |
+| _staging env_    | _GVC (app)_ in staging _organization_       |
+| _production env_ | _GVC (app)_ in production _organization_    |
+
+On Heroku, dyno types are specified in the `Procfile` and configured via the CLI/UI; add-ons are configured only via the CLI/UI.
+On Control Plane, workloads are created either by _templates_ (preferred way) or via the CLI/UI.
+
+For the typical Rails app, this means:
+
+| Function          | Examples             | On Heroku     | On Control Plane                                                                                                  |
+| ----------------- | -------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------- |
+| web traffic       | `rails`, `sinatra`   | `web` dyno    | workload with app image                                                                                           |
+| background jobs   | `sidekiq`, `resque`  | `worker` dyno | workload with app image                                                                                           |
+| db                | `postgres`, `mysql`  | add-on        | external provider or can be set up for development/testing with Docker image (lacks persistence between restarts) |
+| in-memory db      | `redis`, `memcached` | add-on        | external provider or can be set up for development/testing with Docker image (lacks persistence between restarts) |
+| special something | `mailtrap`           | add-on        | external provider or can be set up for development/testing with Docker image (lacks persistence between restarts) |
+
+## Installation
+
+**Note:** `cpl` CLI is configured via a local clone clone of this repo. We may publish it later as a Ruby gem or Node package.
+
+1. Install `node` (required for Control Plane CLI).
+2. Install `ruby` (required for these helpers).
+3. Install Control Plane CLI (adds `cpln` command) and configure credentials.
+
+```sh
+npm install -g @controlplane/cli
+cpln login
+```
+
+4. Install this repo locally and alias `cpl` command globally for easier access, e.g.:
+
+```sh
+git clone https://github.com/shakacode/heroku-to-control-plane
+
+# Create an alias in some local shell startup script, e.g., `.profile`, `.bashrc`, etc.
+alias cpl="~/projects/heroku-to-control-plane/cpl"
+```
+
+- For each Git project that you want to deploy to Control Plane, copy project-specific configs to a `.controlplane` directory at the top of your project. `cpl` will pick those up depending on which project
+  folder tree it runs. Thus, this automates running several projects with different configs without explicitly switching configs.
+
+5. Create a `Dockerfile` for your production deployment. See [this example](https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/.controlplane/Dockerfile).
+
+## Example CLI flow for application build/deployment
+
+**Notes:**
+
+1. `myapp` is an app name defined in the `.controlplane/controlplane.yml` file, such as `ror-tutorial` in [this `controlplane.yml` file](https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/.controlplane/controlplane.yml).
+2. Other files in the `.controlplane/templates` directory are used by the `cpl setup` command.
+
+```sh
+# Provision infrastructure (one-time-only for new apps) using templates.
+# Note how the arguments correspond to files in the `.controlplane/templates` directory.
+cpl setup gvc postgres redis memcached rails sidekiq -a myapp
+
+# Build and push image with auto-tagging "myapp:1_456".
+cpl build-image -a myapp --commit 456
+
+# Prepare database.
+cpl run:detached rails db:prepare -a myapp --image latest
+
+# Promote latest image.
+cpl promote-image -a myapp
+
+# Open app in browser.
+cpl open -a myapp
+```
+
+## Example project modifications for Control Plane
+
+_See this for a complete example._
+
+To learn how to migrate an app, we recommend that you first follow along with [this example project](https://github.com/shakacode/react-webpack-rails-tutorial).
+
+1. Create the `.controlplane` directory at the top of your project and copy files from the `templates` directory of this repo to
+   something as follows:
+
+```sh
+app_main_folder/
+  .controlplane/
+    Dockerfile          # Your app's Dockerfile, with some Control Plane changes.
+    controlplane.yml
+    entrypoint.sh       # App-specific, edit as needed.
+    templates/
+      gvc.yml
+      memcached.yml
+      postgres.yml
+      rails.yml
+      redis.yml
+      sidekiq.yml
+```
+
+The example [`.controlplane` directory](https://github.com/shakacode/react-webpack-rails-tutorial/tree/master/.controlplane) already contains these files.
+
+2. Edit your `controlplane.yml` file as needed. For example, see [this `controlplane.yml` file](https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/.controlplane/controlplane.yml).
+
+```yaml
+# Keys beginning with "cpln_" correspond to your settings in Control Plane.
+
+aliases:
+  common: &common
+    # Organization name for staging (customize to your needs).
+    # Production apps will use a different Control Plane organization, specified below, for security.
+    cpln_org: my-org-staging
+
+    # Example apps use only one location. Control Plane offers the ability to use multiple locations.
+    # TODO -- allow specification of multiple locations
+    default_location: aws-us-east-2
+
+    # Configure the workload name used as a template for one-off scripts, like a Heroku one-off dyno.
+    one_off_workload: rails
+
+    # Workloads that are for the application itself and are using application Docker images.
+    app_workloads:
+      - rails
+      - sidekiq
+
+    # Additional "service type" workloads, using non-application Docker images.
+    additional_workloads:
+      - redis
+      - postgres
+      - memcached
+
+apps:
+  my-app-staging:
+    # Use the values from the common section above.
+    <<: *common
+  my-app-review:
+    <<: *common
+    # If `match_if_app_name_starts_with` == `true`, then use this config for app names starting with this name,
+    # e.g., "my-app-review-pr123", "my-app-review-anything-goes", etc.
+    match_if_app_name_starts_with: true
+  my-app-production:
+    <<: *common
+    # Use a different organization for production.
+    cpln_org: my-org-production
+    # Allows running the command `cpl pipeline-promote my-app-staging` to promote the staging app to production.
+    upstream: my-app-staging
+  my-app-other:
+    <<: *common
+    # You can specify a different `Dockerfile` relative to the `.controlplane` directory (default is just "Dockerfile").
+    dockerfile: ../some_other/Dockerfile
+```
+
+3. We recommend that you try out the commands listed in [the example](https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/.controlplane/readme.md). These steps will guide you through:
+   1. Provision the GVC and workloads
+   2. Build the Docker image
+   3. Run Rails migrations, like in the Heroku release phase
+   4. Promote the lastest Docker image
+
+## Environment
+
+There are two main places where we can set up environment variables in Control Plane:
+
+- **In `workload/container/env`** - those are container-specific and need to be set up individually for each container.
+
+- **In `gvc/env`** - this is a "common" place to keep env vars which we can share among different workloads.
+  Those common variables are not visible by default, and we should explicitly enable them via the `inheritEnv` property.
+
+In general, `gvc/env` vars are useful for "app" types of workloads, e.g., `rails`, `sidekiq`, as they can easily share
+common configs (the same way as on a Heroku app). They are not needed for non-app workloads,
+e.g., `redis`, `memcached`.
+
+It is ok to keep most of the environment variables for non-production environments in the app templates as, in general,
+they are not secret and can be committed to the repository.
+
+It is also possible to set up a Secret store (of type Dictionary), which we can reference as,
+e.g., `cpln://secret/MY_SECRET_STORE_NAME/MY_SECRET_VAR_NAME`.
+In such a case, we also need to set up an app Identity and proper Policy to access the secret.
+
+```yaml
+# In `templates/gvc.yml`:
+spec:
+  env:
+    - name: MY_GLOBAL_VAR
+      value: 'value'
+    - name: MY_SECRET_GLOBAL_VAR
+      value: 'cpln://secret/MY_SECRET_STORE_NAME/MY_SECRET_GLOBAL_VAR'
+
+# In `templates/rails.yml`:
+spec:
+  containers:
+    - name: rails
+      env:
+        - name: MY_LOCAL_VAR
+          value: 'value'
+        - name: MY_SECRET_LOCAL_VAR
+          value: 'cpln://secret/MY_SECRET_STORE_NAME/MY_SECRET_LOCAL_VAR'
+      inheritEnv: true # To enable global env inheritance
+```
+
+## Database
+
+There are several options for a database setup on Control Plane:
+
+1. **Heroku Postgres**. It is the least recommended but simplest. We only need to provision the Postgres add-on on Heroku and
+   copy its `XXXXXX_URL` connection string. This is good for quick testing, but unsuitable for the long term.
+
+2. **Control Plane container**. We can set it up as a workload using one of the default [Docker Hub](https://hub.docker.com/) images.
+   However, such a setup lacks persistence between container restarts.
+   We can use this only for an example or test app
+   where the database doesn't keep any serious data and where such data is restorable.
+
+3. Any other cloud provider for Postgres, e.g., Amazon's RDS can be a quick go-to. Here are [instructions for setting up a free tier of RDS.](https://aws.amazon.com/premiumsupport/knowledge-center/free-tier-rds-launch/).
+
+**Tip:** If you are using RDS for development/testing purposes, you might consider running such a database publicly
+accessible (Heroku actually does that for all of its Postgres databases unless they are within private spaces). Then we can connect to
+such a database from everywhere with only the correct username/password.
+
+By default, we have structured our templates to accomplish this with only a single free tier or low tier AWS RDS instance
+that can serve all your development/testing needs for small/medium applications, e.g., as follows:
+
+```
+aws-rds-single-pg-instance
+  mydb-staging
+  mydb-review-111
+  mydb-review-222
+  mydb-review-333
+```
+
+Additionally, we provide a default `postgres` template in this repo optimized for Control Plane and suitable
+for development purposes.
+
+## In-memory databases
+
+E.g. Redis, Memcached.
+
+For development purposes, it's useful to set those up as Control Plane workloads, as in most cases they don't keep any
+valuable data and can be safely restarted (sometimes), which doesn't affect application performance.
+
+For production purposes or where restarts are not an option, you should use external cloud services.
+
+We provide default `redis` and `memcached` templates in this repo optimized for Control Plane and suitable
+for development purposes.
+
+## CLI commands reference:
+
+Click [here](/docs/commands.md) to see the commands.
+
+You can also run:
+
+```sh
+cpl --help
+```
+
+## Mapping of Heroku Commands to `cpl` and `cpln`
+
+**`[WIP]`**
+
+| Heroku Command                                                                                                   | `cpl` or `cpln` |
+| ---------------------------------------------------------------------------------------------------------------- | --------------- |
+| `[heroku ps](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-ps-type-type)`                     | `cpl ps`        |
+| `[heroku config](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-config)`                       | ?               |
+| `[heroku maintenance](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-maintenance)`             | ?               |
+| `[heroku logs](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-logs)`                           | `cpl logs`      |
+| `[heroku pg](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-pg-database)`                      | ?               |
+| `[heroku pipelines:promote](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-pipelines-promote)` | `cpl promote`   |
+| `[heroku psql](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-psql-database)`                  | ?               |
+| `[heroku redis](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-redis-database)`                | ?               |
+| `[heroku releases](https://devcenter.heroku.com/articles/heroku-cli-commands#heroku-releases)`                   | ?               |
+
+## Examples
+
+1. See `examples/` and `templates/` folders of this repo.
+2. See `.controlplane` directory of this live example: [react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial/tree/master/.controlplane)

data/Rakefile

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

data/bin/cpl

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require "cpl"
+
+Cpl::Cli.start

data/cpl

@@ -0,0 +1,15 @@
+#!/bin/sh
+
+SCRIPT_DIR=$(dirname $(realpath $0))
+
+# exports .env to vars
+#
+# Example .env:
+# CPLN_TOKEN=xxx
+#
+if [ -f "$SCRIPT_DIR/.env" ]; then
+  export $(grep -v '^#' $SCRIPT_DIR/.env | xargs -0)
+fi
+
+# exec $SCRIPT_DIR/old_commands/main.sh "$@"
+exec ruby $SCRIPT_DIR/lib/main.rb "$@"

data/cpl.gemspec

@@ -0,0 +1,42 @@
+# frozen_string_literal: true
+
+require_relative "lib/cpl/version"
+
+Gem::Specification.new do |spec|
+  spec.name    = "cpl"
+  spec.version = Cpl::VERSION
+  spec.authors = ["Justin Gordon", "Sergey Tarasov"]
+  spec.email   = ["justin@shakacode.com", "sergey@shakacode.com"]
+
+  spec.summary     = "Heroku to Control Plane"
+  spec.description = "Helper CLI for migrating from Heroku to Control Plane"
+  spec.homepage    = "https://github.com/shakacode/heroku-to-control-plane"
+  spec.license     = "MIT"
+
+  spec.required_ruby_version = ">= 2.7.0"
+
+  spec.add_dependency "cgi",      "~> 0.3.6"
+  spec.add_dependency "debug",    "~> 1.7.1"
+  spec.add_dependency "dotenv",   "~> 2.8.1"
+  spec.add_dependency "json",     "~> 2.6.3"
+  spec.add_dependency "net-http", "~> 0.3.2"
+  spec.add_dependency "pathname", "~> 0.2.1"
+  spec.add_dependency "psych",    "~> 5.1.0"
+  spec.add_dependency "tempfile", "~> 0.1.3"
+  spec.add_dependency "thor",     "~> 1.2.1"
+  spec.add_dependency "yaml",     "~> 0.2.1"
+
+  spec.add_development_dependency "rspec",         "~> 3.12.0"
+  spec.add_development_dependency "rubocop",       "~> 1.45.0"
+  spec.add_development_dependency "rubocop-rake",  "~> 0.6.0"
+  spec.add_development_dependency "rubocop-rspec", "~> 2.18.1"
+  spec.add_development_dependency "simplecov",     "~> 0.22.0"
+
+  spec.files = `git ls-files -z`.split("\x0").reject do |file|
+    file.match(%r{^(coverage|pkg|spec|tmp)/})
+  end
+
+  spec.executables = ["cpl"]
+
+  spec.metadata["rubygems_mfa_required"] = "true"
+end