psplugin_releases 0.1.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 22e3ab67fed0b34ee0ae66ed54ed7f01da963633
+  data.tar.gz: 19d0e294ed6971940c5139d15a9638662c734a9f
+SHA512:
+  metadata.gz: 71c8bc0b0af3c3e26114beaef1cb96d823e0156906dad54bf58a0e7b8813ef46e9f6422b02961edc224cedd7e1892dd970369e8ec13e5608fdab7c2e7223ff10
+  data.tar.gz: 898b806e77b9dc3dda6a472ff79b5dbc950e65d0a75db06ad433a0555e8ee9e453648ccbb3fb340cd55f66c268f0fb699d4c9de325cbd07764116df20d7ce48b

data/.gitignore

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

data/.rspec

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

data/.travis.yml

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

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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 lbnetid+rb@gmail.com. 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

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

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Laurent B.
+
+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,150 @@
+Releases
+========
+
+[![Gem Version](https://badge.fury.io/rb/psplugin_releases.svg)](https://rubygems.org/gems/psplugin_releases) [![Pipeline status](https://gitlab.com/tools4devops/psplugins/psplugin_releases/badges/master/pipeline.svg)](https://gitlab.com/tools4devops/psplugins/psplugin_releases/commits/master)
+
+[PowerStencil] is the Swiss-army knife templating workflow for developers and ops.
+
+`Releases` is a [PowerStencil] plugin.
+
+See [official website][PowerStencil site].
+
+
+<!-- TOC -->
+
+- [What is a PowerStencil plugin ?](#what-is-a-powerstencil-plugin-)
+- [Using this plugin in your `PowerStencil` projects](#using-this-plugin-in-your-powerstencil-projects)
+- [Goal of this plugin](#goal-of-this-plugin)
+- [Plugin dependencies](#plugin-dependencies)
+- [Plugin capabilities](#plugin-capabilities)
+    - [Subcommands and options](#subcommands-and-options)
+    - [DSL in templates and in `power_stencil shell`](#dsl-in-templates-and-in-power_stencil-shell)
+    - [Entity types](#entity-types)
+        - [`release`](#release)
+- [Contributing](#contributing)
+    - [License](#license)
+    - [Code of Conduct](#code-of-conduct)
+
+<!-- /TOC -->
+
+# What is a PowerStencil plugin ?
+
+A `PowerStencil` plugin can be used in the context of a `PowerStencil` project and bring extra features to a standard project.
+
+If you don't know what `PowerStencil` is made for, you may read [the documentation][PowerStencil] first.
+
+Features provided by a plugin can be:
+
+* Extra config.
+* Extra subcommands or options added to the `power_stencil` command-line.
+* Extra post-build actions.
+* Extra DSL methods available in templates and in `power_stencil shell`.
+* Extra entity types.
+* Extra templates-templates.
+
+# Using this plugin in your `PowerStencil` projects
+
+To use this plugin within your `PowerStencil` project, you need to:
+
+* be within a `PowerStencil` project :wink:.
+* declare this plugin in the project configuration (from the root of your project in the `.ps_project/versioned-config.yaml` file).
+
+In this yaml configuration file, you just have to add a new entry in the `:project_plugins` array or simply create it if it is not yet existing:
+
+```yaml
+:project_plugins:
+  - psplugin_releases
+```
+If this plugin is not already present on your machine, you may have to download it:
+
+    $ power_stencil plugin --install
+
+And then you may see information about the plugin by running:
+
+* `power_stencil info` in the plugins section.
+* `power_stencil plugin --list -v`
+
+# Goal of this plugin
+
+The goal of this plugin is to be able to build anything you can already build within your `PowerStencil` project but in the context of a `release`.
+You can then use the information provided by the `release` within your build templates.
+
+# Plugin dependencies
+
+There is no external dependency for this plugin.
+
+# Plugin capabilities
+
+This plugin provides the following features:
+
+## Subcommands and options
+
+This does not bring any new subcommand. It just adds an option to the `power_stencil build` subcommand:
+
+* `--release`
+
+which expects a entity ID of the type `release` to be provided.
+
+For example:
+
+    $ power_stencil build a_buildable_entity_type/an_entity --release release/my_release
+
+## DSL in templates and in `power_stencil shell`
+
+This plugin brings release-related methods to the `PowerStencil` DSL, available in both templates and in the `power_stencil shell`:
+
+* `target_release(raise_error: true)` returns the release passed on the command line to the `build` sub-command, or `nil` if no release was provided [on the command line](#subcommands-and-options) (or raise an error).
+* `target_release?` will simply say if a release was provided on the command-line, without raising any error.
+
+
+## Entity types
+
+
+### `release`
+
+The idea is that a `release` has a `version` (following semantic versioning principles) and a `content`.
+
+`content` is a hash which keys are entities and values are versions (following semantic versioning principles). `content` represents obviously the content of a `release`.
+
+On top of this it brings:
+* `bump(level: :patch)` will bump the version of the release, following semantic versioning rules. `:patch` is the default, but could be `:minor`, or `:major` (see `PowerStencil::Utils::SemanticVersion::MANDATORY_LEVELS`).
+* `bump_content(*content_key, content_increment: :patch, release_increment: :patch)`, a convenient methods to manage the version of each of the content entities version as well as the global release version. By default, it will bump the versions of all entities "_passed_" to the method (ie found from `content_key`), and them bump the version of the release itself.
+  * `content_key`, can be an entity ID, a type and a name, or even an entity or an array of entities.
+  * `content_increment` and `release_increment` define how to  increase versions. 
+* inheritance between releases themself. Each release being able to have one upstream and multiple downstream releases.
+  * One release can have a `parent` release.
+  * One release can have multiple `children` releases.
+
+:information_source: Use `release` to keep consistency between an arbitrary number of entities which may have version requirements on each others.
+
+# Contributing
+
+Bug reports and pull requests are welcome on Gitlab at https://gitlab.com/tools4devops/psplugins/releases/issues. 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.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License].
+
+## Code of Conduct
+
+Everyone interacting in the PowerStencil project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct].
+
+<!-- End of Document -->
+
+<!-- Pages -->
+[code of conduct]: CODE_OF_CONDUCT.md
+
+<!-- Code links -->
+
+<!-- Illustrations -->
+[simple-flow-image]: doc/images/power-stencil-simple-flow.svg
+
+<!-- External links -->
+[MIT License]: http://opensource.org/licenses/MIT "The MIT license"
+[ERB]: https://ruby-doc.org/stdlib-2.6.3/libdoc/erb/rdoc/ERB.html "Quick ERB description"
+[Haml]: http://haml.info/ "The templating engine for XML-like documents"
+[Ruby]: https://www.ruby-lang.org "The powerful Ruby language"
+[Rails]: https://rubyonrails.org/ "The Ruby on Rails framework"
+[PowerStencil site]: https://powerstencil.brizone.org "Official PowerStencil website"
+[PowerStencil]: https://gitlab.com/tools4devops/power_stencil/blob/master/README.md "PowerStencil documentation"
+[PowerStencil plugins]: https://gitlab.com/tools4devops/power_stencil/blob/master/doc/plugins.md "PowerStencil plugins documentation"

data/Rakefile

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

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "Releases"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/etc/command_line.yaml

@@ -0,0 +1,9 @@
+# This is an example
+# With this file, you can contribute to the power_stencil
+# command-line global semantic
+:subcommands:
+  build:
+    :options:
+      release:
+        :type: entity
+        :summary: Performs the build in the context of a specific release

data/etc/plugin_capabilities.yaml

@@ -0,0 +1,32 @@
+---
+# This file defines the capabilities exposed by the plugin. This file is mandatory
+# for a plugin to be considered as valid.
+
+# Define the main module of the plugin. In this module you can define the build method
+# if the plugin exposes a build (actually a post build hook occurring after the files
+# are "detemplatized")
+:plugin_module: Releases
+
+# In the processors defined in the hereunder hash you map a subcommand with the processor 
+# that will handle it. A plugin can define as many subcommands as needed, or none...
+# Hash keys should match sub-commands declared in the `command_line.yaml` file and processor 
+# classes should expose an `execute` method.
+:processors: null
+
+# This is the name of the method called after the files are detemplatized. This method has
+# to be a module method in the `plugin_module` module.
+:build: null
+
+# If a dsl module is declared it will be injected in the DSL available in the shell or templates
+:dsl:
+  - Releases::Dsl::ReleasesDsl
+
+# These are the files (array) defining entity types. These files should not be already 
+# required by the plugin as they will be required by the framework when needed.
+:entity_definitions:
+  - releases/entity_definitions/release_entity
+
+# A list of root directories where you can find templates in directories named from the
+# entity types they are attached to. 
+:templates: null
+

data/etc/templates/.git_keep

@@ -0,0 +1 @@
+

data/etc/templates/releases_entity/.copy_ignore

@@ -0,0 +1,2 @@
+.subst_ignore
+.copy_ignore

data/etc/templates/releases_entity/.subst_ignore

@@ -0,0 +1 @@
+**

data/etc/templates/releases_entity/message.txt

@@ -0,0 +1,7 @@
+
+This message has been generated on the <%= Time.now %>
+This is an example of what you can do, and how much PowerStencil is customizable ! Check the plugin generated code and
+taylor it to your needs...
+
+This text is the result of a full build process of the entity '<%= build_target.as_path %>' by the plugin '<%= build_target.buildable_by %>'.
+

data/lib/releases/dsl/releases_dsl.rb

@@ -0,0 +1,27 @@
+module Releases
+  module Dsl
+
+    module ReleasesDsl
+
+      def target_release?
+        return false if project.config[:release].nil?
+        return false if target_release(raise_error: false).nil?
+
+        true
+      end
+
+      def target_release(raise_error: true)
+        if project.config[:release].nil?
+          project.logger.warn "Call to DSL method 'target_release', but no target release specified in the config."
+          return nil
+        end
+        rel = entity PowerStencil.config[:release]
+        false_or_raise "Invalid release '#{project.config[:release]}' !", raise_error: raise_error if rel.nil?
+        false_or_raise "'#{project.config[:release]}' is not a release (this is a '#{rel.type}') !", raise_error: raise_error unless rel.type == :release
+        rel
+      end
+
+    end
+
+  end
+end

data/lib/releases/entity_definitions/release_entity.rb

@@ -0,0 +1,101 @@
+module Releases
+  module EntityDefinitions
+
+    class ReleaseEntity < PowerStencil::SystemEntityDefinitions::ProjectEntity
+
+      DEFAULT_VERSION = '0.0.1'
+
+      entity_type :release
+
+      field :version
+      field :content, :is_hash
+      has_one :release, name: :parent, with_reverse_method: :children
+
+      def initialize(fields: {}, universe: nil, user: false)
+        super
+        self.version = DEFAULT_VERSION if version.nil?
+      end
+
+      def full_name
+        '%s v%s' % [name, version]
+      end
+
+      def bump_content(*content_key, content_increment: :patch, release_increment: :patch)
+        get_entity(*content_key) do |entity|
+          content[entity] = bump_version content[entity], content_increment
+        end
+        self.version = bump_version version, release_increment
+      rescue => e
+        raise PowerStencil::Error, "Cannot bump_content because '#{e.message}'"
+      end
+
+      def bump(level: :patch)
+        self.version = bump_version version, level
+      end
+
+      def specifically_valid?(raise_error: false)
+        content.each do |entity, version|
+          unless entity.is_a? UniverseCompiler::Entity::Base
+            return false_or_raise"Invalid hash in release content of #{as_path} ! Key should be an entity !", raise_error: raise_error
+          end
+          unless PowerStencil::Utils::SemanticVersion.valid_version?(version, raise_error: false)
+            return false_or_raise"Invalid version '#{version}' defined for #{entity.as_path} in release #{as_path} !", raise_error: raise_error
+          end
+        end
+        true
+      end
+
+      def save(uri = source_uri, raise_error: true, force_save: false, force_files_generation: false )
+        self.content = content.map { |entity, version| [entity, version.to_s] }.to_h
+        super
+      end
+
+      private
+
+      def get_entity(*entity_criteria, &block)
+        case entity_criteria.size
+        when 1
+          case entity_criteria.first
+          when UniverseCompiler::Entity::Base
+            entity = entity_criteria.first
+            yield entity
+
+          when Array
+            entity_criteria.first.each do |entity|
+              yield entity
+            end
+
+          when String
+            if md = entity_criteria.first.match(/^\s*(?<type>[^\/]+)\/(?<name>.+)\s*$/)
+              search_type = md[:type].to_sym
+              search_name = md[:name]
+              entity = project_engine.entity search_type, search_name, project_engine.root_universe
+              yield entity
+            else
+              raise PowerStencil::Error, 'Invalid entity search ID'
+            end
+
+          else
+            raise PowerStencil::Error, 'Invalid entity search_criteria'
+          end
+
+        when 2
+          entity = project_engine.entity *entity_criteria, project_engine.root_universe
+          yield entity
+
+        else
+          raise PowerStencil::Error, 'Invalid entity search_criteria number'
+        end
+
+      end
+
+      def bump_version(a_version, level)
+        cur_version =  PowerStencil::Utils::SemanticVersion.new a_version
+        cur_version.increment(level).to_s
+      end
+
+
+    end
+
+  end
+end

data/lib/releases/plugin_helper.rb

@@ -0,0 +1,17 @@
+module Releases
+  module PluginHelper
+
+    def plugin_templates_path
+      File.join plugin_root_path, 'etc', 'templates'
+    end
+
+    def command_line_definition_file_path
+      File.join plugin_root_path, 'etc', 'command_line.yaml'
+    end
+
+    def plugin_root_path
+      File.expand_path File.join('..', '..', '..'), __FILE__
+    end
+
+  end
+end

data/lib/releases/version.rb

@@ -0,0 +1,3 @@
+module Releases
+  VERSION = '0.1.1'.freeze
+end

data/lib/releases.rb

@@ -0,0 +1,18 @@
+require 'releases/version'
+require 'releases/plugin_helper'
+require 'releases/dsl/releases_dsl'
+
+module Releases
+
+  def self.post_build_hook(built_entity, generated_files_path)
+    # This is an example of what you could do after files are generated, ie pretty much anything...
+    case built_entity.type
+    when :releases_entity
+      generated_file = File.join generated_files_path, 'message.txt'
+      puts File.readlines(generated_file)
+    else
+      raise PowerStencil::Error, 'Plugin releases doesnt know how handle the build of a releases_entity entity type !'
+    end
+  end
+
+end

data/psplugin_releases.gemspec

@@ -0,0 +1,48 @@
+
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'releases/version'
+
+Gem::Specification.new do |spec|
+  spec.name          = 'psplugin_releases'
+  spec.version       = Releases::VERSION
+  spec.authors       = ['Laurent Briais']
+  spec.email         = ['powerstencil-contact@brizone.org']
+
+  spec.summary       = %q{releases is a plugin for the power_stencil framework.}
+  spec.description   = %q{Release provides entities to manage releases, ie consistent sets of ... something.}
+  spec.homepage      = 'https://gitlab.com/tools4devops/psplugins/releases'
+  spec.license       = 'MIT'
+
+  # Change this and following metadata if you don't want your plugin to be an "official" PowerStencil plugin.
+  # ie deployed to https://gitlab.com/tools4devops/psplugins
+  source_code_uri = 'https://gitlab.com/tools4devops/psplugins/releases'
+
+  # Gem metadata
+  if spec.respond_to?(:metadata)
+    # Nice link to your home page on rubygems.org
+    spec.metadata['homepage_uri'] = spec.homepage
+
+    # You have to probably change this if you don't deploy to gitlab
+    spec.metadata['bug_tracker_uri'] = "#{source_code_uri}/issues"
+    spec.metadata['documentation_uri'] = "#{source_code_uri}/blob/master/README.md"
+    spec.metadata['source_code_uri'] = source_code_uri
+
+    # This metadata is mandatory for a PowerStencil plugin !!
+    spec.metadata['plugin_name'] = 'releases'
+  else
+    raise 'RubyGems 2.0 or newer is required to protect against public gem pushes and PowerStencil plugin mechanism !'
+  end
+
+  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+    f.match(%r{^(test|spec|features)/})
+  end
+  spec.bindir        = 'exe'
+  spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
+  spec.require_paths = ['lib']
+
+  spec.add_development_dependency 'bundler'
+  spec.add_development_dependency 'rake', '~> 10.0'
+  spec.add_development_dependency 'rspec', '~> 3.0'
+  spec.add_development_dependency 'power_stencil', '~> 0.9.0'
+end

metadata

@@ -0,0 +1,128 @@
+--- !ruby/object:Gem::Specification
+name: psplugin_releases
+version: !ruby/object:Gem::Version
+  version: 0.1.1
+platform: ruby
+authors:
+- Laurent Briais
+autorequire: 
+bindir: exe
+cert_chain: []
+date: 2019-11-11 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: bundler
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+- !ruby/object:Gem::Dependency
+  name: rake
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '10.0'
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '3.0'
+- !ruby/object:Gem::Dependency
+  name: power_stencil
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.9.0
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: 0.9.0
+description: Release provides entities to manage releases, ie consistent sets of ...
+  something.
+email:
+- powerstencil-contact@brizone.org
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- ".gitignore"
+- ".rspec"
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- bin/console
+- bin/setup
+- etc/command_line.yaml
+- etc/plugin_capabilities.yaml
+- etc/templates/.git_keep
+- etc/templates/releases_entity/.copy_ignore
+- etc/templates/releases_entity/.subst_ignore
+- etc/templates/releases_entity/message.txt
+- lib/releases.rb
+- lib/releases/dsl/releases_dsl.rb
+- lib/releases/entity_definitions/release_entity.rb
+- lib/releases/plugin_helper.rb
+- lib/releases/version.rb
+- psplugin_releases.gemspec
+homepage: https://gitlab.com/tools4devops/psplugins/releases
+licenses:
+- MIT
+metadata:
+  homepage_uri: https://gitlab.com/tools4devops/psplugins/releases
+  bug_tracker_uri: https://gitlab.com/tools4devops/psplugins/releases/issues
+  documentation_uri: https://gitlab.com/tools4devops/psplugins/releases/blob/master/README.md
+  source_code_uri: https://gitlab.com/tools4devops/psplugins/releases
+  plugin_name: releases
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ">="
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 2.5.1
+signing_key: 
+specification_version: 4
+summary: releases is a plugin for the power_stencil framework.
+test_files: []