chef-ruby-lvm-attrib 0.3.13 → 0.3.14

data/lib/lvm/attributes/2.03.17(2)/pvsseg.yaml

@@ -0,0 +1,16 @@
+# These are column to object attribute mappings
+# generated by ./bin/generate_field_data based on
+# lvm2/lib/report/columns.h
+---
+- :method: pv_uuid
+  :column: pv_uuid
+  :type_hint: String
+  :description: For PhysicalVolume to PhysicalVolumeSegment relationship.
+- :method: size
+  :column: pvseg_size
+  :type_hint: Integer
+  :description: Number of extents in segment.
+- :method: start
+  :column: pvseg_start
+  :type_hint: Integer
+  :description: Physical Extent number of start of segment.

data/lib/lvm/attributes/2.03.17(2)/vgs.yaml

@@ -0,0 +1,144 @@
+# These are column to object attribute mappings
+# generated by ./bin/generate_field_data based on
+# lvm2/lib/report/columns.h
+---
+- :method: lv_count
+  :column: lv_count
+  :type_hint: Integer
+  :description: Number of LVs.
+- :method: max_lv
+  :column: max_lv
+  :type_hint: Integer
+  :description: Maximum number of LVs allowed in VG or 0 if unlimited.
+- :method: max_pv
+  :column: max_pv
+  :type_hint: Integer
+  :description: Maximum number of PVs allowed in VG or 0 if unlimited.
+- :method: pv_count
+  :column: pv_count
+  :type_hint: Integer
+  :description: Number of PVs in VG.
+- :method: snap_count
+  :column: snap_count
+  :type_hint: Integer
+  :description: Number of snapshots.
+- :method: allocation_policy
+  :column: vg_allocation_policy
+  :type_hint: String
+  :description: VG allocation policy.
+- :method: attr
+  :column: vg_attr
+  :type_hint: String
+  :description: Various attributes - see man page.
+- :method: autoactivation
+  :column: vg_autoactivation
+  :type_hint: String
+  :description: Set if VG autoactivation is enabled.
+- :method: clustered
+  :column: vg_clustered
+  :type_hint: String
+  :description: Set if VG is clustered.
+- :method: exported
+  :column: vg_exported
+  :type_hint: String
+  :description: Set if VG is exported.
+- :method: extendable
+  :column: vg_extendable
+  :type_hint: String
+  :description: Set if VG is extendable.
+- :method: extent_count
+  :column: vg_extent_count
+  :type_hint: Integer
+  :description: Total number of Physical Extents.
+- :method: extent_size
+  :column: vg_extent_size
+  :type_hint: Integer
+  :description: Size of Physical Extents in current units.
+- :method: fmt
+  :column: vg_fmt
+  :type_hint: String
+  :description: Type of metadata.
+- :method: free
+  :column: vg_free
+  :type_hint: Integer
+  :description: Total amount of free space in current units.
+- :method: free_count
+  :column: vg_free_count
+  :type_hint: Integer
+  :description: Total number of unallocated Physical Extents.
+- :method: lock_args
+  :column: vg_lock_args
+  :type_hint: String
+  :description: Lock args of the VG used by lvmlockd.
+- :method: lock_type
+  :column: vg_lock_type
+  :type_hint: String
+  :description: Lock type of the VG used by lvmlockd.
+- :method: mda_copies
+  :column: vg_mda_copies
+  :type_hint: Integer
+  :description: Target number of in use metadata areas in the VG.
+- :method: mda_count
+  :column: vg_mda_count
+  :type_hint: Integer
+  :description: Number of metadata areas on this VG.
+- :method: mda_free
+  :column: vg_mda_free
+  :type_hint: Integer
+  :description: Free metadata area space for this VG in current units.
+- :method: mda_size
+  :column: vg_mda_size
+  :type_hint: Integer
+  :description: Size of smallest metadata area for this VG in current units.
+- :method: mda_used_count
+  :column: vg_mda_used_count
+  :type_hint: Integer
+  :description: Number of metadata areas in use on this VG.
+- :method: missing_pv_count
+  :column: vg_missing_pv_count
+  :type_hint: Integer
+  :description: Number of PVs in VG which are missing.
+- :method: name
+  :column: vg_name
+  :type_hint: String
+  :description: Name.
+- :method: partial
+  :column: vg_partial
+  :type_hint: String
+  :description: Set if VG is partial.
+- :method: permissions
+  :column: vg_permissions
+  :type_hint: String
+  :description: VG permissions.
+- :method: profile
+  :column: vg_profile
+  :type_hint: String
+  :description: Configuration profile attached to this VG.
+- :method: seqno
+  :column: vg_seqno
+  :type_hint: Integer
+  :description: Revision number of internal metadata.  Incremented whenever it changes.
+- :method: shared
+  :column: vg_shared
+  :type_hint: String
+  :description: Set if VG is shared.
+- :method: size
+  :column: vg_size
+  :type_hint: Integer
+  :description: Total size of VG in current units.
+- :method: sysid
+  :column: vg_sysid
+  :type_hint: String
+  :description: System ID of the VG indicating which host owns it.
+- :method: systemid
+  :column: vg_systemid
+  :type_hint: String
+  :description: System ID of the VG indicating which host owns it.
+- :method: tags
+  :column: vg_tags
+  :type_hint: String
+  :description: Tags
+- :method: uuid
+  :column: vg_uuid
+  :type_hint: String
+  :description: Unique identifier.

data/lib/lvm/attributes.rb

@@ -1,9 +1,8 @@
 require "yaml" unless defined?(YAML)
+require_relative "version"
 
 module LVM
   module Attributes
-    VERSION = "0.3.13".freeze
-
     def load(version, name)
       cwd = __dir__
 

data/lib/lvm/version.rb

@@ -0,0 +1,5 @@
+module LVM
+  module Attributes
+    VERSION = "0.3.14".freeze
+  end
+end

metadata

@@ -1,39 +1,35 @@
 --- !ruby/object:Gem::Specification
 name: chef-ruby-lvm-attrib
 version: !ruby/object:Gem::Version
-  version: 0.3.13
+  version: 0.3.14
 platform: ruby
 authors:
-- Chef Software
+- Sous-Chefs
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-09-07 00:00:00.000000000 Z
+date: 2023-10-24 00:00:00.000000000 Z
 dependencies: []
 description: A list of attributes for LVM objects
 email:
-- oss@chef.io
+- help@sous-chefs.org
 executables:
 - generate_field_data
 extensions: []
 extra_rdoc_files: []
 files:
 - ".github/CODEOWNERS"
-- ".github/ISSUE_TEMPLATE/BUG_TEMPLATE.md"
-- ".github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md"
-- ".github/ISSUE_TEMPLATE/ENHANCEMENT_REQUEST_TEMPLATE.md"
-- ".github/ISSUE_TEMPLATE/SUPPORT_QUESTION.md"
-- ".github/PULL_REQUEST_TEMPLATE.md"
-- ".github/dependabot.yml"
 - ".github/workflows/ci.yml"
 - ".gitignore"
 - ".gitmodules"
+- ".markdownlint-cli2.yaml"
 - ".mdlrc"
 - ".rubocop.yml"
 - CHANGELOG.md
 - CODE_OF_CONDUCT.md
 - CONTRIBUTING.md
 - Gemfile
+- LICENSE
 - README.md
 - Rakefile
 - VERSION
@@ -635,17 +631,23 @@ files:
 - lib/lvm/attributes/2.03.16(2)/pvs.yaml
 - lib/lvm/attributes/2.03.16(2)/pvsseg.yaml
 - lib/lvm/attributes/2.03.16(2)/vgs.yaml
+- lib/lvm/attributes/2.03.17(2)/lvs.yaml
+- lib/lvm/attributes/2.03.17(2)/lvsseg.yaml
+- lib/lvm/attributes/2.03.17(2)/pvs.yaml
+- lib/lvm/attributes/2.03.17(2)/pvsseg.yaml
+- lib/lvm/attributes/2.03.17(2)/vgs.yaml
 - lib/lvm/attributes/2.03.21(2)/lvs.yaml
 - lib/lvm/attributes/2.03.21(2)/lvsseg.yaml
 - lib/lvm/attributes/2.03.21(2)/pvs.yaml
 - lib/lvm/attributes/2.03.21(2)/pvsseg.yaml
 - lib/lvm/attributes/2.03.21(2)/vgs.yaml
+- lib/lvm/version.rb
 - renovate.json
 - test/test_ruby-lvm-attributes.rb
 - update-lvm.sh
-homepage: https://github.com/chef/chef-ruby-lvm-attrib
+homepage: https://github.com/sous-chefs/chef-ruby-lvm-attrib
 licenses:
-- MIT
+- Apache-2.0
 metadata: {}
 post_install_message:
 rdoc_options: []

data/.github/ISSUE_TEMPLATE/BUG_TEMPLATE.md

@@ -1,29 +0,0 @@
----
-name: � Bug Report
-about: If something isn't working as expected �.
-labels: "Status: Untriaged"
----
-
-# Version:
-
-[Version of the project installed]
-
-# Environment:
-
-[Details about the environment such as the Operating System, cookbook details, etc...]
-
-# Scenario:
-
-[What you are trying to achieve and you can't?]
-
-# Steps to Reproduce:
-
-[If you are filing an issue what are the things we need to do in order to repro your problem?]
-
-# Expected Result:
-
-[What are you expecting to happen as the consequence of above reproduction steps?]
-
-# Actual Result:
-
-[What actually happens after the reproduction steps?]

data/.github/ISSUE_TEMPLATE/DESIGN_PROPOSAL.md

@@ -1,40 +0,0 @@
----
-name: Design Proposal
-about: I have a significant change I would like to propose and discuss before starting
-labels: "Status: Untriaged"
----
-
-### When a Change Needs a Design Proposal
-
-A design proposal should be opened any time a change meets one of the following qualifications:
-
-- Significantly changes the user experience of a project in a way that impacts users.
-- Significantly changes the underlying architecture of the project in a way that impacts other developers.
-- Changes the development or testing process of the project such as a change of CI systems or test frameworks.
-
-### Why We Use This Process
-
-- Allows all interested parties (including any community member) to discuss large impact changes to a project.
-- Serves as a durable paper trail for discussions regarding project architecture.
-- Forces design discussions to occur before PRs are created.
-- Reduces PR refactoring and rejected PRs.
-
----
-
-<!---  Proposal description and rationale.  -->
-
-## Motivation
-
-<!---
-    As a <<user_profile>>,
-    I want to <<functionality>>,
-    so that <<benefit>>.
- -->
-
-## Specification
-
-<!---  A detailed description of the planned implementation. -->
-
-## Downstream Impact
-
-<!---  Which other tools will be impacted by this work?  -->

data/.github/ISSUE_TEMPLATE/ENHANCEMENT_REQUEST_TEMPLATE.md

@@ -1,17 +0,0 @@
----
-name: 🚀 Enhancement Request
-about: I have a suggestion (and may want to implement it 🙂)!
-labels: "Status: Untriaged"
----
-
-### Describe the Enhancement:
-<!---  What you are trying to achieve that you can't? -->
-
-### Describe the Need:
-<!---  What kind of user do you believe would utilize this enhancement, and how many users might want this functionality -->
-
-### Current Alternative
-<!--- Is there a current alternative that you can utilize to workaround the lack of this enhancement -->
-
-### Can We Help You Implement This?:
-<!---  The best way to ensure your enhancement is built is to help implement the enhancement yourself. If you're interested in helping out we'd love to give you a hand to make this possible. Let us know if there's something you need. -->

data/.github/ISSUE_TEMPLATE/SUPPORT_QUESTION.md

@@ -1,12 +0,0 @@
----
-name: 🤗 Support Question
-about: If you have a question 💬, please check out our Slack!
----
-
-We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack.
-
- * Chef Community Slack at http://community-slack.chef.io/.
- * Chef Mailing List https://discourse.chef.io/
-
-
- Support issues opened here will be closed and redirected to Slack or Discourse.

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,15 +0,0 @@
-### Description
-
-[Please describe what this change achieves]
-
-### Issues Resolved
-
-[List any existing issues this PR resolves, or any Discourse or
-StackOverflow discussions that are relevant]
-
-### Check List
-
-- [ ] New functionality includes tests
-- [ ] All tests pass
-- [ ] All commits have been signed-off for the Developer Certificate of Origin. See <https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco>
-- [ ] PR title is a worthy inclusion in the CHANGELOG

data/.github/dependabot.yml

@@ -1,9 +0,0 @@
-version: 2
-updates:
-- package-ecosystem: bundler
-  directory: "/"
-  schedule:
-    interval: daily
-    time: "06:00"
-    timezone: America/Los_Angeles
-  open-pull-requests-limit: 10