secvault 2.6.0 → 2.7.1

data/CODE_OF_CONDUCT.md

@@ -1,132 +0,0 @@
-# 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, caste, color, 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 email 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
-[INSERT CONTACT METHOD].
-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.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

data/USAGE_EXAMPLES.md

@@ -1,65 +0,0 @@
-# Secvault API
-
-Secvault provides separate control over secrets loading and Rails integration.
-
-## Core Methods
-
-### `Secvault.start!(files: [])`
-
-Loads secrets from YAML files. Returns `true`/`false`.
-
-- **Default**: Uses `config/secrets.yml` if `files` is empty
-- **Access**: Secrets available via `Secvault.secrets`
-- **Non-invasive**: Does not modify `Rails.application.secrets`
-
-### `Secvault.integrate_with_rails!`
-
-Replaces `Rails.application.secrets` with Secvault's loaded secrets. Returns `true`/`false`.
-
-### `Secvault.secrets`
-
-Access to loaded secrets as `ActiveSupport::OrderedOptions`.
-
-### Status Methods
-
-- `Secvault.active?` - Returns `true` if secrets have been loaded
-- `Secvault.rails_integrated?` - Returns `true` if Rails integration is active
-
-## Usage
-
-### Standalone
-
-```ruby
-# Load secrets independently
-Secvault.start!
-api_key = Secvault.secrets.api_key
-```
-
-### With Rails Integration
-
-```ruby
-# Load and integrate with Rails
-Secvault.start!
-Secvault.integrate_with_rails!
-api_key = Rails.application.secrets.api_key
-```
-
-### Multiple Files
-
-```ruby
-# Files are deep-merged in order
-Secvault.start!(files: [
-  'config/shared_secrets.yml',
-  'config/secrets.yml'
-])
-```
-
-### Error Handling
-
-```ruby
-if Secvault.start!(files: ['config/secrets.yml'])
-  if Secvault.integrate_with_rails!
-    # Both operations successful
-  end
-end
-```

data/lib/secvault/generators/secrets_generator.rb

@@ -1,100 +0,0 @@
-# frozen_string_literal: true
-
-require "rails/generators/base"
-require "active_support/encrypted_file"
-require "securerandom"
-
-module Secvault
-  module Generators
-    class SecretsGenerator < Rails::Generators::Base
-      source_root File.expand_path("templates", __dir__)
-
-      desc "Creates a secrets.yml file for secrets management"
-
-      class_option :force, type: :boolean, default: false, desc: "Overwrite existing secrets.yml"
-      class_option :encrypted, type: :boolean, default: false, desc: "Create encrypted secrets.yml (default: plain YAML)"
-
-      def create_secrets_file
-        secrets_path = Rails.root.join("config/secrets.yml")
-        key_path = Rails.root.join("config/secrets.yml.key")
-
-        if secrets_path.exist? && !options[:force]
-          say "Secrets file already exists at config/secrets.yml", :yellow
-          return
-        end
-
-        default_content = generate_default_secrets
-
-        if options[:encrypted]
-          # Create encrypted secrets file
-          unless key_path.exist?
-            key = ActiveSupport::EncryptedFile.generate_key
-            File.write(key_path, key)
-            say "Generated encryption key in config/secrets.yml.key", :green
-          end
-
-          encrypted_file = ActiveSupport::EncryptedFile.new(
-            content_path: secrets_path,
-            key_path: key_path,
-            env_key: "RAILS_SECRETS_KEY",
-            raise_if_missing_key: true
-          )
-
-          encrypted_file.write(default_content)
-          say "Created encrypted secrets.yml file", :green
-          say "Add config/secrets.yml.key to your .gitignore file", :yellow
-        else
-          # Create plain YAML secrets file
-          File.write(secrets_path, default_content)
-          say "Created plain secrets.yml file", :green
-          say "Remember to add config/secrets.yml to your .gitignore if it contains sensitive data", :yellow
-        end
-      end
-
-      def add_to_gitignore
-        gitignore_path = Rails.root.join(".gitignore")
-        key_entry = "/config/secrets.yml.key"
-
-        if gitignore_path.exist?
-          gitignore_content = File.read(gitignore_path)
-          unless gitignore_content.include?(key_entry)
-            File.open(gitignore_path, "a") do |f|
-              f.puts "\n# Ignore encrypted secrets key"
-              f.puts key_entry
-            end
-            say "Added secrets key to .gitignore", :green
-          end
-        end
-      end
-
-      private
-
-      def generate_default_secrets
-        <<~YAML
-          # Be sure to restart your server when you modify this file.
-          
-          # Your secret key is used for verifying the integrity of signed cookies.
-          # If you change this key, all old signed cookies will become invalid!
-          
-          # Make sure the secret is at least 30 characters and all random,
-          # no regular words or you'll be exposed to dictionary attacks.
-          # You can use `rails secret` to generate a secure secret key.
-          
-          # Make sure the secrets in this file are kept private
-          # if you're sharing your code publicly.
-          
-          development:
-            secret_key_base: #{SecureRandom.hex(64)}
-          
-          test:
-            secret_key_base: #{SecureRandom.hex(64)}
-          
-          # Do not keep production secrets in the repository,
-          # instead read values from the environment.
-          production:
-            secret_key_base: <%= ENV["SECRET_KEY_BASE"] %>
-        YAML
-      end
-    end
-  end
-end

data/lib/secvault/secrets_helper.rb

@@ -1,44 +0,0 @@
-# frozen_string_literal: true
-
-module Secvault
-  class SecretsHelper
-    def initialize(app)
-      @app = app
-      @secrets_path = app.root.join("config/secrets.yml")
-      @key_path = app.root.join("config/secrets.yml.key")
-    end
-
-    def secrets
-      @secrets ||= load_secrets
-    end
-
-    def [](key)
-      secrets[key.to_sym]
-    end
-
-    def fetch(key, default = nil)
-      secrets.fetch(key.to_sym, default)
-    end
-
-    def key?(key)
-      secrets.key?(key.to_sym)
-    end
-
-    def empty?
-      secrets.empty?
-    end
-
-    def to_h
-      secrets.dup
-    end
-
-    private
-
-    def load_secrets
-      return {} unless @secrets_path.exist?
-
-      env_secrets = Secvault::Secrets.read_secrets(@secrets_path, @key_path, Rails.env)
-      env_secrets || {}
-    end
-  end
-end

data/sig/secvault.rbs

@@ -1,4 +0,0 @@
-module Secvault
-  VERSION: String
-  # See the writing guide of rbs: https://github.com/ruby/rbs#guides
-end