stove 2.0.0 → 3.0.0

data/lib/stove/jira.rb

@@ -1,88 +0,0 @@
-require 'faraday'
-require 'faraday_middleware'
-
-module Stove
-  class JIRA
-    include Mixin::Instanceable
-    include Logify
-    include Mixin::Optionable
-
-    option :base_url,
-      ENV['JIRA_URL'] || 'https://tickets.opscode.com/rest/api/2'
-
-    def issue(key, options = {})
-      connection.get("issue/#{key}", options).body
-    end
-
-    def search(query = {})
-      jql = query.map { |k,v| %Q|#{k} = "#{v}"| }.join(' AND ')
-      connection.get('search', jql: jql).body
-    end
-
-    def close_and_comment(key, comment)
-      transitions = issue(key, expand: 'transitions')['transitions']
-      close = transitions.first { |transition| transition['name'] == 'Close' }
-
-      if close.nil?
-        log.warn("Issue #{key} does not have a `Close' transition")
-        return
-      end
-
-      connection.post("issue/#{key}/transitions", {
-        transition: { id: close['id'] },
-        update: {
-          comment: [
-            { add: { body: comment.to_s } }
-          ]
-        },
-        fields: {
-          resolution: {
-            name: 'Fixed'
-          },
-          assignee: {
-            name: nil
-          }
-        }
-      })
-    end
-
-    private
-
-    def connection
-      @connection ||= Faraday.new(base_url) do |builder|
-        # Encode request bodies as JSON
-        builder.request :json
-
-        # Add basic authentication information
-        builder.request :basic_auth, Stove::Config[:jira][:username],
-                                     Stove::Config[:jira][:password]
-
-        # Handle any common errors
-        builder.use Stove::Middleware::Exceptions
-
-        # Decode responses as JSON if the Content-Type is json
-        builder.response :json
-        builder.response :json_fix
-
-        # Allow up to 3 redirects
-        builder.response :follow_redirects, limit: 3
-
-        # Log all requests and responses (useful for development)
-        builder.response :logger, log
-
-        # Raise errors on 40x and 50x responses
-        builder.response :raise_error
-
-        # Use the default adapter (Net::HTTP)
-        builder.adapter :net_http
-
-        # Set the User-Agent header for logging purposes
-        builder.headers[:user_agent] = Stove::USER_AGENT
-
-        # Set some options, such as timeouts
-        builder.options[:timeout]      = 30
-        builder.options[:open_timeout] = 30
-      end
-    end
-  end
-end

data/lib/stove/middlewares/chef_authentication.rb

@@ -1,60 +0,0 @@
-require 'pp'
-
-module Stove
-  class Middleware::ChefAuthentication < Faraday::Middleware
-    dependency do
-      require 'mixlib/authentication/signedheaderauth'
-      require 'openssl'
-      require 'uri'
-    end
-
-    #
-    # @param [Faraday::Application] app
-    # @param [String] client
-    #   the name of the client to use for Chef
-    # @param [OpenSSL::PKey::RSA] key
-    #   the RSA private key to sign with
-    #
-    def initialize(app, client, key)
-      super(app)
-
-      @client = client
-      @key    = OpenSSL::PKey::RSA.new(File.read(key))
-    end
-
-    def call(env)
-      env[:request_headers].merge!(signing_object(env))
-      @app.call(env)
-    end
-
-    private
-
-    def signing_object(env)
-      params = {
-        :http_method => env[:method],
-        :timestamp   => Time.now.utc.iso8601,
-        :user_id     => @client,
-        :path        => env[:url].path,
-        :body        => env[:body] || '',
-      }
-
-      # Royal fucking hack
-      #   1. (n.) This code sample
-      #   2. (v.) Having to decompose a Faraday response because Mixlib
-      #           Authentication couldn't get a date to the prom
-      if env[:body] && env[:body].is_a?(Faraday::CompositeReadIO)
-        file = env[:body]
-          .instance_variable_get(:@parts)
-          .first { |part| part.is_a?(Faraday::Parts::FilePart) }
-          .instance_variable_get(:@io)
-          .instance_variable_get(:@ios)[1]
-          .instance_variable_get(:@local_path)
-
-        params[:file] = File.new(file)
-      end
-
-      object = Mixlib::Authentication::SignedHeaderAuth.signing_object(params)
-      object.sign(@key)
-    end
-  end
-end

data/lib/stove/middlewares/exceptions.rb

@@ -1,17 +0,0 @@
-module Stove
-  class Middleware::Exceptions < Faraday::Middleware
-    include Logify
-
-    def call(env)
-      begin
-        @app.call(env)
-      rescue Faraday::Error::ConnectionFailed
-        url = env[:url].to_s.gsub(env[:url].path, '')
-        raise Error::ServerUnavailable.new(url: url)
-      rescue Faraday::Error::ClientError => e
-        log.debug(env.inspect)
-        raise
-      end
-    end
-  end
-end

data/lib/stove/mixins/filterable.rb

@@ -1,11 +0,0 @@
-module Stove
-  module Mixin::Filterable
-    def before(action, message, &block)
-      Runner.filters[action][:before] << Filter.new(self, message, &block)
-    end
-
-    def after(action, message, &block)
-      Runner.filters[action][:after] << Filter.new(self, message, &block)
-    end
-  end
-end

data/lib/stove/plugins/github.rb

@@ -1,107 +0,0 @@
-module Stove
-  class Plugin::GitHub < Plugin::Base
-    id 'github'
-    description 'Publish the release to GitHub'
-
-    onload do
-      require 'faraday'
-      require 'faraday_middleware'
-      require 'octokit'
-    end
-
-    validate(:git) do
-      options[:git]
-    end
-
-    validate(:configuration) do
-      Config.has_key?(:github)
-    end
-
-    validate(:access_token) do
-      Config[:github].has_key?(:access_token)
-    end
-
-    after(:upload, 'Publishing the release to GitHub') do
-      release = client.create_release(repository, cookbook.tag_version,
-        name: cookbook.tag_version,
-        body: cookbook.changeset,
-      )
-      asset = client.upload_asset("repos/#{repository}/releases/#{release.id}", cookbook.tarball,
-        content_type: 'application/x-gzip',
-        name: filename,
-      )
-      client.update_release_asset("repos/#{repository}/releases/assets/#{asset.id}",
-        name: filename,
-        label: 'Download Cookbook',
-      )
-    end
-
-    def client
-      return @client if @client
-
-      config = {}.tap do |h|
-        h[:middleware]   = middleware
-        h[:access_token] = Config[:github][:access_token]
-        h[:api_endpoint] = Config[:github][:api_endpoint] if Config[:github][:api_endpoint]
-      end
-
-      @client = Octokit::Client.new(config)
-      @client
-    end
-
-    def changeset
-      @changeset ||= cookbook.changeset.split("\n")[2..-1].join("\n").strip
-    end
-
-    def repository
-      @repository ||= Octokit::Repository.from_url(repo_url)
-    end
-
-    def filename
-      @filename ||= "#{cookbook.name}-#{cookbook.version}.tar.gz"
-    end
-
-    def middleware
-      Faraday::Builder.new do |builder|
-        # Handle any common errors
-        builder.use Stove::Middleware::Exceptions
-        builder.use Octokit::Response::RaiseError
-
-        # Log all requests and responses (useful for development)
-        builder.response :logger, log
-
-        # Raise errors on 40x and 50x responses
-        builder.response :raise_error
-
-        # Use the default adapter (Net::HTTP)
-        builder.adapter :net_http
-      end
-    end
-
-    #
-    # The URL for this repository on GitHub. This method automatically
-    # translates SSH and git:// URLs to https:// URLs.
-    #
-    # @return [String]
-    #
-    def repo_url
-      return @repo_url if @repo_url
-
-      path = File.join('.git', 'config')
-      log.debug("Calculating repo_url from `#{path}'")
-
-      config = File.read(path)
-      log.debug("Config contents:\n#{config}")
-
-      config =~ /\[remote "#{options[:remote]}"\]\n\s+url = (.+)$/
-      log.debug("Match: #{$1.inspect}")
-
-      @repo_url = $1.to_s
-                    .strip
-                    .gsub(/\.git$/, '')
-                    .gsub(/^\S+@(\S+):/, 'https://\1/')
-                    .gsub('git://', 'https://')
-      @repo_url
-    end
-  end
-end

data/lib/stove/plugins/jira.rb

@@ -1,72 +0,0 @@
-module Stove
-  class Plugin::JIRA < Plugin::Base
-    id 'jira'
-    description 'Resolve JIRA issues'
-
-    validate(:configuration) do
-      Config.has_key?(:jira)
-    end
-
-    validate(:username) do
-      Config[:jira].has_key?(:username)
-    end
-
-    validate(:password) do
-      Config[:jira].has_key?(:password)
-    end
-
-    before(:changelog, 'Generate JIRA changeset') do
-      by_type = unreleased_issues.inject({}) do |hash, issue|
-        type = issue['fields']['issuetype']['name']
-        hash[type] ||= []
-        hash[type] << {
-          key:     issue['key'],
-          summary: issue['fields']['summary'],
-        }
-
-        hash
-      end
-
-      # Calculate the JIRA path based off of the JIRA base_url
-      jira_base = URI.parse(JIRA.base_url)
-      jira_base.path = ''
-      jira_base = jira_base.to_s
-      log.debug("JIRA base is `#{jira_base}'")
-
-      contents = []
-
-      by_type.each do |type, issues|
-        contents << "### #{type}"
-        issues.sort { |a, b| b[:key].to_i <=> a[:key].to_i }.each do |issue|
-          url = "#{jira_base}/browse/#{issue[:key]}"
-          contents << "- **[#{issue[:key]}](#{url})** - #{issue[:summary]}"
-        end
-        contents << ''
-      end
-
-      cookbook.changeset = contents.join("\n")
-    end
-
-    after(:upload, 'Resolving JIRA issues') do
-      unreleased_issues.collect do |issue|
-        Thread.new do
-          JIRA.close_and_comment(issue['key'], "Released in #{cookbook.version}")
-        end
-      end.map(&:join)
-    end
-
-    #
-    # The list of unreleased tickets on JIRA.
-    #
-    # @return [Array<Hash>]
-    #
-    def unreleased_issues
-      @unreleased_issues ||= JIRA.search(
-        project:    'COOK',
-        resolution: 'Fixed',
-        status:     'Fix Committed',
-        component:  cookbook.name,
-      )['issues']
-    end
-  end
-end

data/locales/en.yml

@@ -1,230 +0,0 @@
-en:
-  stove:
-    errors:
-      abstract_method: >
-        `%{method}` is an abstract method. You must override this method in
-        your subclass with the proper implementation and logic. For more
-        information, please see the inline documentation for %{method}. If you
-        are not a developer, this is most likely a bug. Please file a bug report
-        at https://github.com/sethvargo/stove/issues/new and include the
-        command(s) you ran to arrive at this error.
-
-      git_failed: >
-        An error occurred while running:
-
-            git %{command}
-
-        There is likely an informative message from git that explains what
-        happened right above this message.
-
-      metadata_not_found: >
-        The file at `%{path}' does not exist or does not contain valid metadata.
-        Please make sure you have specified the correct path and that the
-        metdata file exists.
-
-      server_unavailable: >
-        The server at `%{url}` is unavailable or is not currently accepting
-        client connections. Please ensure the server is accessible via ping (or
-        telnet) on your local network. If this error persists, please contact
-        your network administrator.
-
-
-    validations:
-      # Bump validations
-      # ----------------
-      bump:
-        changed: >
-          The version you are trying to bump already exists! You must specify a
-          new version.
-
-        incremented: >
-          The cookbook version you are attempting to bump to is less than the
-          existing version. You cannot (re-)release a previous version of the
-          same cookbook. Please specify a higher version.
-
-
-      # Changelog validations
-      # ---------------------
-      changelog:
-        editor: >
-          The `$EDITOR' environment variable is not set. In order to use the
-          Changelog plugin, you must set a default editor for Stove to open when
-          generating the CHANGLEOG. You can set the editor like this:
-
-              export EDITOR=vi
-
-        exists: >
-          There is no `CHANGELOG.md' found at `%{path}. In order to use the
-          Changelog plugin, you must have a changelog in markdown format at the
-          root of your cookbook. You can also skip the Changelog plugin by
-          specifying the `--no-changelog' option:
-
-              bake x.y.z --no-changelog
-
-        format: >
-          The changelog at `%{path}' does not appear to be a valid format. The
-          changelog must be in the following format:
-
-              [Cookbook Name]
-              ===============
-
-              v[version] ([release date])
-              ---------------------------
-              - [Release point]
-
-          For example:
-
-              Apache 2
-              ========
-
-              v1.0.0 (2013-04-05)
-              -------------------
-              - Initial release
-
-
-      # Git validations
-      # ---------------
-      git:
-        clean: >
-          The cookbook at `%{path}' has untracked files! In order to use the git
-          plugin, you must have a clean working directory. Please commit or
-          stash your changes before running Stove again.
-
-        repository: >
-          The cookbook at `%{path}' does not appear to be a valid git
-          repository. In order to use the git plugin, your cookbook must be
-          initialized as a git repository. To create a git repository, run:
-
-              git init %{path}
-
-        up_to_date: >
-          The cookbook at `%{path}' is out of sync with the remote repository.
-          Please update your local cache with the remote repository before
-          continuing:
-
-              git pull
-
-          And then push your local changes to the remote repository:
-
-              git push
-
-
-      # GitHub validations
-      # ------------------
-      github:
-        access_token: >
-          The Stove configuration for GitHub does not contain an access token.
-          In order to use the GitHub plugin, you must set an access token in the
-          GitHub section of the `~/.stove' file:
-
-              {
-                "github": {
-                  "access_token": "YOUR_ACCESS_TOKEN"
-                }
-              }
-
-          You can generate an access token for GitHub by following the
-          instructions at: https://help.github.com/articles/creating-an-access-token-for-command-line-use.
-
-        configuration: >
-          The Stove configuration for GitHub does not exist! In order to use the
-          GitHub plugin, you must set your GitHub information in the `~/.stove'
-          file:
-
-              {
-                "github": {
-                  "access_token": "YOUR_ACCESS_TOKEN"
-                }
-              }
-
-        git: >
-          In order to use the GitHub plugin, you must also activate the `git'
-          plugin.
-
-
-      # JIRA validations
-      # ----------------
-      jira:
-        configuration: >
-          The Stove configuration for JIRA does not exist! In order to use the
-          JIRA plugin, you must set your JIRA information in the `~/.stove'
-          file:
-
-              {
-                "jira": {
-                  "username": "YOUR_USERNAME",
-                  "password": "YOUR_PASSWORD"
-                }
-              }
-
-        password: >
-          The Stove configuration for JIRA does not contain a password. In order
-          to use JIRA features, you must set a password in the jira section of
-          the `~/.stove' file:
-
-              {
-                "jira": {
-                  "password": "YOUR_PASSWORD"
-                }
-              }
-
-        username: >
-          The Stove configuration for JIRA does not contain a username. In order
-          to use JIRA features, you must set a username in the jira section of
-          the `~/.stove' file:
-
-              {
-                "jira": {
-                  "username": "YOUR_USERNAME"
-                }
-              }
-
-      # Community validations
-      # ---------------------
-      community:
-        configuration: >
-          The Stove configuration for the Chef community site does not exist! In
-          order to perform operations against the Chef community site, you must
-          set your username and path to your client key in the community section
-          of the `~/.stove' file:
-
-              {
-                "community": {
-                  "username": "YOUR_USERNAME",
-                  "key": "YOUR_KEY_PATH"
-                }
-              }
-
-        key: >
-          The Stove configuration for the Chef community site does not contain a
-          key. In order to use the Chef community site features, you must set
-          the path to your key the community section of the `~/.stove' file:
-
-              {
-                "community": {
-                  "key": "YOUR_KEY_PATH"
-                }
-              }
-
-        username: >
-          The Stove configuration for the Chef community site does not contain a
-          username. In order to use the Chef community site features, you must
-          set a username the community section of the `~/.stove' file:
-
-              {
-                "community": {
-                  "username": "YOUR_USERNAME"
-                }
-              }
-
-        category: >
-          You did not specify a category! The Chef community site requires all
-          cookbooks belong to a category. For existing cookboks, Stove can query
-          the Chef community site API and automatically complete the category
-          for you. However, for new cookbooks, you must specify the `--category'
-          flag at runtime:
-
-              bake x.y.z --category Utilities
-
-          For a complete listing of categories, please see the Chef community
-          site.