vitess-activerecord-migration 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 3eae6c9228eb8d3d5ebae767cef06ff65c89b073e6598bf690ddbd0907e995a0
+  data.tar.gz: bed613b3ec15ac973a5dabd1957e054d68b5d7adaefb0938af03fba3b7b2be6e
+SHA512:
+  metadata.gz: bf5fef0a1132c9cc35a7af3314b64da6669653813d90dc50ddb65018ecfa456dc2c25d1b234a8c9a66a7d8f0838b186a0fa281f05249ef58b15e25b084410085
+  data.tar.gz: 213b03855f9303882dd237db331a7b030f1dfe704d18b70895b71b7dffb120165ce012bb932016dc8ce2ce45e9f18d9722ad77b1b65d6c5acd44ae4e0cf1aec5

data/.env

@@ -0,0 +1,3 @@
+RUBY_VERSION=${RUBY_VERSION:-3.2}
+RAILS_VERSION=${RAILS_VERSION:-~> 7.2.0}
+VITESS_VERSION=${VITESS_VERSION:-20.0}

data/.rspec

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

data/.rubocop.yml

@@ -0,0 +1,13 @@
+AllCops:
+  TargetRubyVersion: 2.7
+
+Style/StringLiterals:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Style/StringLiteralsInInterpolation:
+  Enabled: true
+  EnforcedStyle: double_quotes
+
+Layout/LineLength:
+  Max: 120

data/CHANGELOG.md

@@ -0,0 +1,5 @@
+## [Unreleased]
+
+## [0.1.0] - 2024-09-02
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders 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, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at yoheimuta@gmail.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Dockerfile

@@ -0,0 +1,10 @@
+ARG RUBY_VERSION=""
+
+FROM ruby:$RUBY_VERSION
+
+WORKDIR /migration
+
+ARG RAILS_VERSION=""
+ENV RAILS_VERSION=$RAILS_VERSION
+
+CMD ["tail", "-f", "/dev/null"]

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2024 Yohei Yoshimuta
+
+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/Makefile

@@ -0,0 +1,9 @@
+e2e-test-setup:
+	test/endtoend/get_deps.sh
+
+migration-test-setup: e2e-test-setup
+	echo "Setup Migration test"
+	test/endtoend/migration_test.sh
+
+keyspace-serving-check:
+	test/endtoend/keyspace_serving_check.sh

data/README.md

@@ -0,0 +1,98 @@
+# Vitess::Activerecord::Migration
+
+vitess-activerecord-migration is a gem for integrating Vitess with ActiveRecord migrations.
+
+Vitess::Activerecord::Migration provides tools to integrate Vitess with ActiveRecord migrations, 
+allowing for seamless database schema changes in a Vitess environment.
+
+## Installation
+
+```
+gem 'vitess-activerecord-migration'
+```
+
+## Usage
+
+Create a config file under config/initializers.
+
+```ruby
+# config/initializers/vitess_activerecord_migration.rb
+ActiveRecord::Migration.prepend(Vitess::Activerecord::Migration)
+```
+
+The default ddl strategy is `vitess` with no options.
+
+When you want to set the ddl strategy and its options for one shot, you can set them in the migration file.
+
+```ruby
+def default_ddl_strategy
+  "direct"
+end
+def change
+  create_table :test_vitess_users do |t|
+    t.string :name
+  end
+end
+```
+
+When you want to set the default ddl strategy and its options, you can override the following methods.
+
+```ruby
+# lib/vitess/activerecord/app_migration.rb
+module Vitess
+  module Activerecord
+    module AppMigration
+      def default_ddl_strategy
+        "vitess --prefer-instant-ddl"
+      end
+    end
+  end
+end
+```
+
+```ruby
+# config/initializers/vitess_activerecord_migration.rb
+require 'vitess/activerecord/app_migration'
+ActiveRecord::Migration.prepend(Vitess::Activerecord::Migration)
+ActiveRecord::Migration.prepend(Vitess::Activerecord::AppMigration)
+```
+
+
+## Development
+
+After checking out the repo, run the following command to start related containers.
+
+```bash
+$ docker compose up
+```
+
+Then, you can run the following command to create a vitess cluster.
+
+```bash
+$ docker exec -it migration-endtoend /bin/bash
+323e040cee42:/endtoend# make migration-test-setup
+```
+
+Finally, you can run the test suite to verify that the gem works correctly.
+
+```bash
+$ docker exec -it migration /bin/bash
+root@0401705ea521:/migration# rake spec
+```
+
+To install this gem onto your local machine, run `bundle exec rake install`.
+To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`,
+which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/yoheimuta/vitess-activerecord-migration.
+This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/[USERNAME]/vitess-activerecord-migration/blob/main/CODE_OF_CONDUCT.md).
+
+## 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 Vitess::Activerecord::Migration project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/vitess-activerecord-migration/blob/main/CODE_OF_CONDUCT.md).

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/compose.ci.yml

@@ -0,0 +1,14 @@
+services:
+  migration:
+    command: bash -c "git config --global --add safe.directory /migration && bin/setup && rake spec"
+    depends_on:
+      migration-endtoend:
+        condition: service_healthy
+  migration-endtoend:
+    command: bash -c "dockerd-entrypoint.sh & sleep 5 && unset DOCKER_HOST && make migration-test-setup"
+    healthcheck:
+      test: ["CMD", "make", "keyspace-serving-check"]
+      interval: 10s
+      timeout: 10s
+      retries: 60
+      start_period: 1m

data/compose.override.yml

@@ -0,0 +1,18 @@
+services:
+  migration:
+    command: bash -c "bin/setup && tail -f /dev/null"
+  migration-endtoend:
+    ports:
+      # http
+      - "53303:3303"
+      # mysql (vtgate)
+      - "53306:3306"
+  migration-mysql:
+    image: mysql:8.0
+    container_name: migration-mysql
+    ports:
+      - "18306:3306"
+    environment:
+      MYSQL_ALLOW_EMPTY_PASSWORD: yes
+    networks:
+      - migration-default

data/compose.yml

@@ -0,0 +1,32 @@
+services:
+  migration:
+    build:
+      context: .
+      args:
+        RUBY_VERSION: ${RUBY_VERSION}
+        RAILS_VERSION: ${RAILS_VERSION}
+    container_name: migration
+    volumes:
+      - bundle:/usr/local/bundle
+      - .:/migration
+    networks:
+      - migration-default
+  migration-endtoend:
+    build:
+      context: ./test/endtoend
+      args:
+        VITESS_VERSION: ${VITESS_VERSION}
+    container_name: migration-endtoend
+    privileged: true
+    volumes:
+      - .:/endtoend
+      - tmp:/endtoend/tmp
+    networks:
+      - migration-default
+
+networks:
+  migration-default:
+
+volumes:
+  bundle:
+  tmp:

data/lib/vitess/activerecord/migration/version.rb

@@ -0,0 +1,9 @@
+# frozen_string_literal: true
+
+module Vitess
+  module Activerecord
+    module Migration
+      VERSION = "0.1.0"
+    end
+  end
+end

data/lib/vitess/activerecord/migration.rb

@@ -0,0 +1,146 @@
+# frozen_string_literal: true
+
+require_relative "migration/version"
+require "active_record"
+
+module Vitess
+  module Activerecord
+    module Migration
+      class Error < StandardError; end
+
+      # Returns the default DDL strategy.
+      # This method is called and set before executing the change, up, or down methods.
+      #
+      # If you want to use a different strategy like `direct`, override this method.
+      def default_ddl_strategy
+        "vitess"
+      end
+
+      # Returns the timeout seconds for waiting for the completion of the DDL statement.
+      # Even after the timeout, the migration on Vitess will not be stopped, but a warning will be logged.
+      #
+      # Override this method if you want to change the default timeout.
+      def wait_timeout_seconds
+        7200 # 120 minutes
+      end
+
+      # Override exec_migration to set the default DDL strategy to vitess.
+      # This method is called every time a migration is executed.
+      # If you want to use a different DDL strategy, call with_ddl_strategy inside the change method or elsewhere.
+      def exec_migration(connection, direction)
+        @migration_direction = direction
+        @using_change_method = self.respond_to?(:change)
+        @migration_context = "#{self.version}_#{self.class.name.underscore}"
+        with_ddl_strategy default_ddl_strategy do
+          super(connection, direction)
+        end
+      end
+
+      # Override the create_table method.
+      # If using the Vitess strategy, wait for the completion of the CREATE TABLE statement.
+      # This prevents an evaluation error from occurring if you try to execute a DDL on that table before the creation is complete.
+      def create_table(table_name, **options)
+        super(table_name, **options)
+
+        # If create_table is called during revert, no additional processing is done.
+        # We expect the DROP statement to be issued automatically during revert, but if execute is run here,
+        # it will raise an IrreversibleMigration error, so this is to prevent that.
+        return if down_migration_in_change_method?
+
+        # If not using the Vitess strategy, do not wait for the completion of the CREATE TABLE statement.
+        return unless vitess_strategy?
+
+        wait_for_ddl
+      end
+
+      # Temporarily change the DDL strategy within the block.
+      #
+      # You can use this method inside the change method to change the strategy only during the execution of specific DDL statements.
+      # However, note that this makes the migration irreversible, so if it’s possible to handle this by overriding the default_ddl_strategy, use that instead.
+      def with_ddl_strategy(strategy)
+        if enable_vitess?
+          original_ddl_strategy = execute("SELECT @@ddl_strategy").first.first
+          execute("SET @@ddl_strategy='#{strategy}'")
+          execute("SET @@migration_context='#{@migration_context}'") unless strategy == "direct"
+          begin
+            yield
+            wait_for_ddl unless strategy == "direct"
+          ensure
+            execute("SET @@ddl_strategy='#{original_ddl_strategy}'")
+          end
+        else
+          yield
+        end
+      end
+
+      private
+
+      def vitess_strategy?
+        enable_vitess? && execute("SELECT @@ddl_strategy").first.first.include?("vitess")
+      end
+
+      def down_migration_in_change_method?
+        @migration_direction == :down && @using_change_method
+      end
+
+      def enable_vitess?
+        version = execute("SELECT VERSION()").first.first
+        version.include?("Vitess")
+      end
+
+      def wait_for_ddl
+        start_time = Time.now
+        timeout_seconds = wait_timeout_seconds
+        interval_seconds = 2
+        max_interval_seconds = 30
+
+        @stopped_uuid ||= []
+
+        loop do
+          migrations = ActiveRecord::Base.connection.select_all("SHOW VITESS_MIGRATIONS LIKE '#{@migration_context}'")
+
+          migrations.each do |migration|
+            id = migration["id"]
+            next if @stopped_uuid.include?(id)
+
+            details = %w[migration_uuid migration_statement added_timestamp started_timestamp is_immediate_operation progress eta_seconds retries]
+            detail_message = details.map { |column| "#{column}: #{migration[column]}" }.join(" | ")
+            Rails.logger.info("Vitess Migration #{id} checking status, #{detail_message}")
+
+            status = migration["migration_status"]
+            if %(complete failed cancelled).include?(status)
+              case status
+              when "complete"
+                Rails.logger.info("Vitess Migration #{id} completed successfully at #{migration["completed_timestamp"]}")
+              when "failed"
+                Rails.logger.error("Vitess Migration #{id} failed: #{migration["message"]} at #{migration["completed_timestamp"]}")
+              when "cancelled"
+                Rails.logger.warn("Vitess Migration #{id} was cancelled at #{migration["cancelled_timestamp"]}")
+              end
+              @stopped_uuid << id
+            else
+              Rails.logger.info("Vitess Migration #{id} is still #{status}")
+            end
+          end
+
+          if @stopped_uuid.count == migrations.count
+            Rails.logger.info("Vitess Migration all completed successfully")
+            break
+          end
+
+          if Time.now - start_time > timeout_seconds
+            Rails.logger.warn("Vitess Migration did not complete within #{timeout_seconds} seconds. Timing out.")
+            break
+          end
+
+          Rails.logger.info("Waiting #{interval_seconds} seconds for Vitess DDL to complete...")
+          sleep(interval_seconds)
+          interval_seconds = [interval_seconds * 2, max_interval_seconds].min
+        end
+      rescue => e
+        Rails.logger.error("An error occurred while waiting for Vitess DDL: #{e.message}")
+        Rails.logger.error(e.backtrace.join("\n"))
+      end
+    end
+  end
+end

data/sig/rails_support.rbs

@@ -0,0 +1,34 @@
+class RailsSupport
+  DATABASE_CONFIG: String
+
+  INIT_CONFIG: String
+
+  @migration_files: [String]
+  @rails_root: String
+
+  @schema_backup_path: String
+
+  @schema_path: String
+
+  def self.copy_template_file: (*String)-> void
+
+  def self.setup: -> void
+
+  def create_test_vitess_users: (String)->[String,String]
+
+  def generate_migration: -> String
+
+  def run: (String,String?)-> void
+
+  def run_test_env: (String)->void
+
+  def setup: -> void
+
+  def cleanup : -> void
+
+  private
+
+  def db_config: ->untyped
+
+  def rails_new: -> void
+end

data/sig/vitess/activerecord/migration.rbs

@@ -0,0 +1,33 @@
+module Vitess
+  module Activerecord
+    module Migration
+      VERSION: String
+      # See the writing guide of rbs: https://github.com/ruby/rbs#guides
+      @migration_context: String
+      @migration_direction: Symbol
+
+      @stopped_uuid: [String]
+      @using_change_method: bool
+
+      def create_table: (String, untyped)->void
+
+      def default_ddl_strategy: -> String
+
+      def wait_timeout_seconds: -> Integer
+
+      def exec_migration: (untyped, Symbol)-> void
+
+      def with_ddl_strategy: (String)-> void
+
+      private
+
+      def down_migration_in_change_method?: -> bool
+
+      def enable_vitess?: -> bool
+
+      def vitess_strategy?: -> bool
+
+      def wait_for_ddl: -> void
+    end
+  end
+end

data/vitess-activerecord-migration.gemspec

@@ -0,0 +1,40 @@
+# frozen_string_literal: true
+
+require_relative "lib/vitess/activerecord/migration/version"
+
+Gem::Specification.new do |spec|
+  spec.name = "vitess-activerecord-migration"
+  spec.version = Vitess::Activerecord::Migration::VERSION
+  spec.authors = ["Yohei Yoshimuta"]
+  spec.email = ["yoheimuta@gmail.com"]
+
+  spec.summary = "A gem for integrating Vitess with ActiveRecord migrations."
+  spec.description = "Vitess::Activerecord::Migration provides tools to integrate Vitess with ActiveRecord migrations, allowing for seamless database schema changes in a Vitess environment."
+  spec.homepage = "https://github.com/yoheimuta/vitess-activerecord-migration"
+  spec.license = "MIT"
+  spec.required_ruby_version = ">= 2.7.0"
+
+  spec.metadata["allowed_push_host"] = "https://rubygems.org"
+
+  spec.metadata["homepage_uri"] = spec.homepage
+  spec.metadata["source_code_uri"] = "https://github.com/yoheimuta/vitess-activerecord-migration"
+  spec.metadata["changelog_uri"] = "https://github.com/yoheimuta/vitess-activerecord-migration/blob/main/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(__dir__) do
+    `git ls-files -z`.split("\x0").reject do |f|
+      (File.expand_path(f) == __FILE__) ||
+        f.start_with?(*%w[bin/ test/ spec/ features/ .git .circleci appveyor Gemfile])
+    end
+  end
+  spec.bindir = "exe"
+  spec.executables = spec.files.grep(%r{\Aexe/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  # Uncomment to register a new dependency of your gem
+  spec.add_dependency "activerecord", ">= 6", "< 8.1"
+
+  # For more information and examples about making a new gem, check out our
+  # guide at: https://bundler.io/guides/creating_gem.html
+end

metadata

@@ -0,0 +1,88 @@
+--- !ruby/object:Gem::Specification
+name: vitess-activerecord-migration
+version: !ruby/object:Gem::Version
+  version: 0.1.0
+platform: ruby
+authors:
+- Yohei Yoshimuta
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2024-10-07 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: activerecord
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '6'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '8.1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '6'
+    - - "<"
+      - !ruby/object:Gem::Version
+        version: '8.1'
+description: Vitess::Activerecord::Migration provides tools to integrate Vitess with
+  ActiveRecord migrations, allowing for seamless database schema changes in a Vitess
+  environment.
+email:
+- yoheimuta@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".env"
+- ".rspec"
+- ".rubocop.yml"
+- CHANGELOG.md
+- CODE_OF_CONDUCT.md
+- Dockerfile
+- LICENSE.txt
+- Makefile
+- README.md
+- Rakefile
+- compose.ci.yml
+- compose.override.yml
+- compose.yml
+- lib/vitess/activerecord/migration.rb
+- lib/vitess/activerecord/migration/version.rb
+- sig/rails_support.rbs
+- sig/vitess/activerecord/migration.rbs
+- tmp/.keep
+- vitess-activerecord-migration.gemspec
+homepage: https://github.com/yoheimuta/vitess-activerecord-migration
+licenses:
+- MIT
+metadata:
+  allowed_push_host: https://rubygems.org
+  homepage_uri: https://github.com/yoheimuta/vitess-activerecord-migration
+  source_code_uri: https://github.com/yoheimuta/vitess-activerecord-migration
+  changelog_uri: https://github.com/yoheimuta/vitess-activerecord-migration/blob/main/CHANGELOG.md
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: 2.7.0
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubygems_version: 3.0.3.1
+signing_key: 
+specification_version: 4
+summary: A gem for integrating Vitess with ActiveRecord migrations.
+test_files: []