omnibus-software 23.7.295 → 3002.0.0

data/.expeditor/determine_version.sh

@@ -1,15 +0,0 @@
-
-#!/bin/bash
-
-# This gets run as a pre-commit hook just prior to a merge to
-# determine the new version number.
-
-# Leading zeros are not permitted in strict SemVer
-YEAR=`date +"%y" | sed -e 's/^0//'` # Must be < 256 per Microsoft
-MONTH=`date +"%m" | sed -e 's/^0//'`
-
-OLD_BUILD=`cut -f3 -d. < VERSION`
-
-NEW_BUILD=$(($OLD_BUILD + 1)) # Monotonically increase the build number
-
-echo $YEAR.$MONTH.$NEW_BUILD > VERSION

data/.expeditor/push_git_tag.sh

@@ -1,12 +0,0 @@
-#!/bin/bash
-
-# This gets run as a post-commit hook after merge to add the version tag so it
-# is easy to determine what changes are in a particular build.
-#
-# https://expeditor.chef.io/docs/reference/action-filters/#post-commit
-
-
-VERSION=`cat VERSION`
-
-git tag $VERSION
-git push origin $VERSION

data/.expeditor/run_linux_tests.sh

@@ -1,16 +0,0 @@
-#!/bin/bash
-#
-# This script runs a passed in command, but first setups up the bundler caching on the repo
-
-set -ue
-
-export USER="root"
-export LANG=C.UTF-8 LANGUAGE=C.UTF-8
-
-echo "--- bundle install"
-
-bundle config --local path vendor/bundle
-bundle install --jobs=7 --retry=3
-
-echo "+++ bundle exec task"
-bundle exec $@

data/.expeditor/software_upload.pipeline.yml

@@ -1,17 +0,0 @@
----
-steps:
-- label: ":file_folder: upload software to internal sources"
-  agents:
-    queue: default
-  plugins:
-  - docker#v3.5.0:
-      image: chefes/omnibus-toolchain-ubuntu-2204-x86
-      shell:
-      - "/bin/bash"
-      - "-e"
-      - "-c"
-      propagate-environment: true
-  commands:
-  - export PATH=/opt/omnibus-toolchain/bin/:/app/bin:/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
-    && ./scripts/internal_sources.rb ./scripts/internal_sources.yml
-  timeout_in_minutes: 20

data/.expeditor/verify.pipeline.yml

@@ -1,52 +0,0 @@
----
-expeditor:
-  cached_folders:
-    - vendor
-  defaults:
-    buildkite:
-      retry:
-        automatic:
-          limit: 1
-      timeout_in_minutes: 30
-
-steps:
-
-- label: run-lint-and-specs-ruby-2.7
-  command:
-    - .expeditor/run_linux_tests.sh rake
-
-  expeditor:
-    executor:
-      docker:
-        image: ruby:2.7-buster
-
-- label: run-lint-and-specs-ruby-3.0
-  command:
-    - .expeditor/run_linux_tests.sh rake
-
-  expeditor:
-    executor:
-      docker:
-        image: ruby:3.0-buster
-
-- label: run-lint-and-specs-ruby-3.1
-  command:
-    - .expeditor/run_linux_tests.sh rake
-
-  expeditor:
-    executor:
-      docker:
-        image: ruby:3.1-buster
-
-- label: ":pipeline: generate-test-build-steps"
-  command: expeditor buildkite trigger-pipeline test/generate_steps.rb
-  agents:
-    queue: pipeline-trigger
-  plugins:
-    - docker#v3.5.0:
-        image: "$EXPEDITOR_TRIGGER_IMAGE_NAME:$EXPEDITOR_TRIGGER_IMAGE_VERSION"
-        propagate-environment: true
-        network: host
-        environment:
-        - AWS_ACCOUNT_ID
-        - AWS_REGION

data/.github/CODEOWNERS

@@ -1,5 +0,0 @@
-# Order is important. The last matching pattern has the most precedence.
-
-*                 @chef/chef-infra-reviewers @chef/chef-infra-approvers @chef/chef-infra-owners @chef/chef-infra-server-reviewers @chef/chef-infra-server-approvers @chef/chef-infra-server-owners @chef/infra-packages
-.expeditor/       @chef/jex-team @chef/infra-packages
-*.md              @chef/docs-team

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,11 +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 https://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/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

data/.github/lock.yml

@@ -1 +0,0 @@
-daysUntilLock: 60

data/.gitignore

@@ -1,17 +0,0 @@
-*.gem
-.bundle
-Gemfile.lock
-vendor
-pkg/*
-test/pkg/*
-/binstubs
-/bin
-
-# avoid generic ctags files
-tags
-gems.tags
-gemtags
-.tags
-.gem.tags
-.gemtags
-.tags_sorted_by_file

data/CHANGELOG.md

@@ -1,18 +0,0 @@
-# Changelog
-
-<!-- latest_release -->
-<!-- latest_release -->
-
-<!-- release_rollup since=23.6.292 -->
-### Changes since 23.6.292 release
-<!-- release_rollup -->
-
-<!-- latest_stable_release -->
-## [23.6.292](https://github.com/chef/omnibus-software/tree/23.6.292) (2023-06-14)
-<!-- latest_stable_release -->
-
-## [23.6.291](https://github.com/chef/omnibus-software/tree/23.6.291) (2023-06-05)
-
-## [23.2.283](https://github.com/chef/omnibus-software/tree/23.2.283) (2023-02-20)
-
-## [23.2.281](https://github.com/chef/omnibus-software/tree/23.2.281) (2023-02-06)

data/CODE_OF_CONDUCT.md

@@ -1 +0,0 @@
-Please refer to the Chef Community Code of Conduct at https://www.chef.io/code-of-conduct/

data/CONTRIBUTING.md

@@ -1 +0,0 @@
-Please refer to https://github.com/chef/chef/blob/main/CONTRIBUTING.md

data/Dockerfile

@@ -1,21 +0,0 @@
-FROM ubuntu:18.04
-
-RUN apt-get update -y -q && apt-get install -y \
-      autoconf \
-      binutils \
-      binutils-doc \
-      bison \
-      build-essential \
-      curl \
-      devscripts \
-      dpkg-dev \
-      fakeroot \
-      flex \
-      gettext \
-      gnupg \
-      ncurses-dev \
-      ncurses-dev \
-      wget \
-      zlib1g-dev
-
-RUN curl -L https://omnitruck.chef.io/install.sh | bash -s -- -P omnibus-toolchain

data/Gemfile

@@ -1,10 +0,0 @@
-source "https://rubygems.org"
-gemspec
-
-group :development, :test do
-  gem "omnibus", git: "https://github.com/chef/omnibus", branch: "main"
-  gem "highline"
-  gem "rake"
-  gem "chefstyle"
-  gem "ohai"
-end

data/LICENSE

@@ -1,201 +0,0 @@
-                              Apache License
-                        Version 2.0, January 2004
-                     http://www.apache.org/licenses/
-
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-   "License" shall mean the terms and conditions for use, reproduction,
-   and distribution as defined by Sections 1 through 9 of this document.
-
-   "Licensor" shall mean the copyright owner or entity authorized by
-   the copyright owner that is granting the License.
-
-   "Legal Entity" shall mean the union of the acting entity and all
-   other entities that control, are controlled by, or are under common
-   control with that entity. For the purposes of this definition,
-   "control" means (i) the power, direct or indirect, to cause the
-   direction or management of such entity, whether by contract or
-   otherwise, or (ii) ownership of fifty percent (50%) or more of the
-   outstanding shares, or (iii) beneficial ownership of such entity.
-
-   "You" (or "Your") shall mean an individual or Legal Entity
-   exercising permissions granted by this License.
-
-   "Source" form shall mean the preferred form for making modifications,
-   including but not limited to software source code, documentation
-   source, and configuration files.
-
-   "Object" form shall mean any form resulting from mechanical
-   transformation or translation of a Source form, including but
-   not limited to compiled object code, generated documentation,
-   and conversions to other media types.
-
-   "Work" shall mean the work of authorship, whether in Source or
-   Object form, made available under the License, as indicated by a
-   copyright notice that is included in or attached to the work
-   (an example is provided in the Appendix below).
-
-   "Derivative Works" shall mean any work, whether in Source or Object
-   form, that is based on (or derived from) the Work and for which the
-   editorial revisions, annotations, elaborations, or other modifications
-   represent, as a whole, an original work of authorship. For the purposes
-   of this License, Derivative Works shall not include works that remain
-   separable from, or merely link (or bind by name) to the interfaces of,
-   the Work and Derivative Works thereof.
-
-   "Contribution" shall mean any work of authorship, including
-   the original version of the Work and any modifications or additions
-   to that Work or Derivative Works thereof, that is intentionally
-   submitted to Licensor for inclusion in the Work by the copyright owner
-   or by an individual or Legal Entity authorized to submit on behalf of
-   the copyright owner. For the purposes of this definition, "submitted"
-   means any form of electronic, verbal, or written communication sent
-   to the Licensor or its representatives, including but not limited to
-   communication on electronic mailing lists, source code control systems,
-   and issue tracking systems that are managed by, or on behalf of, the
-   Licensor for the purpose of discussing and improving the Work, but
-   excluding communication that is conspicuously marked or otherwise
-   designated in writing by the copyright owner as "Not a Contribution."
-
-   "Contributor" shall mean Licensor and any individual or Legal Entity
-   on behalf of whom a Contribution has been received by Licensor and
-   subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of
-   this License, each Contributor hereby grants to You a perpetual,
-   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-   copyright license to reproduce, prepare Derivative Works of,
-   publicly display, publicly perform, sublicense, and distribute the
-   Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of
-   this License, each Contributor hereby grants to You a perpetual,
-   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-   (except as stated in this section) patent license to make, have made,
-   use, offer to sell, sell, import, and otherwise transfer the Work,
-   where such license applies only to those patent claims licensable
-   by such Contributor that are necessarily infringed by their
-   Contribution(s) alone or by combination of their Contribution(s)
-   with the Work to which such Contribution(s) was submitted. If You
-   institute patent litigation against any entity (including a
-   cross-claim or counterclaim in a lawsuit) alleging that the Work
-   or a Contribution incorporated within the Work constitutes direct
-   or contributory patent infringement, then any patent licenses
-   granted to You under this License for that Work shall terminate
-   as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the
-   Work or Derivative Works thereof in any medium, with or without
-   modifications, and in Source or Object form, provided that You
-   meet the following conditions:
-
-   (a) You must give any other recipients of the Work or
-       Derivative Works a copy of this License; and
-
-   (b) You must cause any modified files to carry prominent notices
-       stating that You changed the files; and
-
-   (c) You must retain, in the Source form of any Derivative Works
-       that You distribute, all copyright, patent, trademark, and
-       attribution notices from the Source form of the Work,
-       excluding those notices that do not pertain to any part of
-       the Derivative Works; and
-
-   (d) If the Work includes a "NOTICE" text file as part of its
-       distribution, then any Derivative Works that You distribute must
-       include a readable copy of the attribution notices contained
-       within such NOTICE file, excluding those notices that do not
-       pertain to any part of the Derivative Works, in at least one
-       of the following places: within a NOTICE text file distributed
-       as part of the Derivative Works; within the Source form or
-       documentation, if provided along with the Derivative Works; or,
-       within a display generated by the Derivative Works, if and
-       wherever such third-party notices normally appear. The contents
-       of the NOTICE file are for informational purposes only and
-       do not modify the License. You may add Your own attribution
-       notices within Derivative Works that You distribute, alongside
-       or as an addendum to the NOTICE text from the Work, provided
-       that such additional attribution notices cannot be construed
-       as modifying the License.
-
-   You may add Your own copyright statement to Your modifications and
-   may provide additional or different license terms and conditions
-   for use, reproduction, or distribution of Your modifications, or
-   for any such Derivative Works as a whole, provided Your use,
-   reproduction, and distribution of the Work otherwise complies with
-   the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise,
-   any Contribution intentionally submitted for inclusion in the Work
-   by You to the Licensor shall be under the terms and conditions of
-   this License, without any additional terms or conditions.
-   Notwithstanding the above, nothing herein shall supersede or modify
-   the terms of any separate license agreement you may have executed
-   with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade
-   names, trademarks, service marks, or product names of the Licensor,
-   except as required for reasonable and customary use in describing the
-   origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or
-   agreed to in writing, Licensor provides the Work (and each
-   Contributor provides its Contributions) on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-   implied, including, without limitation, any warranties or conditions
-   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-   PARTICULAR PURPOSE. You are solely responsible for determining the
-   appropriateness of using or redistributing the Work and assume any
-   risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory,
-   whether in tort (including negligence), contract, or otherwise,
-   unless required by applicable law (such as deliberate and grossly
-   negligent acts) or agreed to in writing, shall any Contributor be
-   liable to You for damages, including any direct, indirect, special,
-   incidental, or consequential damages of any character arising as a
-   result of this License or out of the use or inability to use the
-   Work (including but not limited to damages for loss of goodwill,
-   work stoppage, computer failure or malfunction, or any and all
-   other commercial damages or losses), even if such Contributor
-   has been advised of the possibility of such damages.
-
-9. Accepting Warranty or Additional Liability. While redistributing
-   the Work or Derivative Works thereof, You may choose to offer,
-   and charge a fee for, acceptance of support, warranty, indemnity,
-   or other liability obligations and/or rights consistent with this
-   License. However, in accepting such obligations, You may act only
-   on Your own behalf and on Your sole responsibility, not on behalf
-   of any other Contributor, and only if You agree to indemnify,
-   defend, and hold each Contributor harmless for any liability
-   incurred by, or claims asserted against, such Contributor by reason
-   of your accepting any such warranty or additional liability.
-
-END OF TERMS AND CONDITIONS
-
-APPENDIX: How to apply the Apache License to your work.
-
-   To apply the Apache License to your work, attach the following
-   boilerplate notice, with the fields enclosed by brackets "[]"
-   replaced with your own identifying information. (Don't include
-   the brackets!)  The text should be enclosed in the appropriate
-   comment syntax for the file format. We also recommend that a
-   file or class name and description of purpose be included on the
-   same "printed page" as the copyright notice for easier
-   identification within third-party archives.
-
-Copyright [yyyy] [name of copyright owner]
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.

data/README.md

@@ -1,99 +0,0 @@
-# Omnibus Software
-
-[![Build Status](https://badge.buildkite.com/e07e55eb2f281ec50dbd0f2bdbf8da4a2f246b864bffd17dfb.svg)](https://buildkite.com/chef-oss/chef-omnibus-software-main-verify)
-
-**Umbrella Project**: [Chef Foundation](https://github.com/chef/chef-oss-practices/blob/main/projects/chef-foundation.md)
-
-**Project State**: [Active](https://github.com/chef/chef-oss-practices/blob/main/repo-management/repo-states.md#active)
-
-**Issues [Response Time Maximum](https://github.com/chef/chef-oss-practices/blob/main/repo-management/repo-states.md)**: 14 days
-
-**Pull Request [Response Time Maximum](https://github.com/chef/chef-oss-practices/blob/main/repo-management/repo-states.md)**: 14 days
-
-This repository contains shared software descriptions, for use by any [Omnibus](https://github.com/chef/omnibus) project that needs them.
-
-This project is managed by the CHEF Release Engineering team. For more information on the Release Engineering team's contribution, triage, and release process, please consult the [CHEF Release Engineering OSS Management Guide](https://docs.google.com/a/opscode.com/document/d/1oJB0vZb_3bl7_ZU2YMDBkMFdL-EWplW1BJv_FXTUOzg/edit).
-
-**The main branch of this project corresponds to the main branch of omnibus!**
-
-## Using Your Own Software Definitions
-
-This repository is the collection of Chef Software's software definitions. We like that others get utility out of them, but they are not meant to be comprehensive collection of all software on the planet. For more information, please read [Omnibus, a look forward](https://blog.chef.io/omnibus-a-look-forward) on the Chef blog.
-
-For more information on writing your own software definitions, please see [the Omnibus README](https://github.com/chef/omnibus#sharing-software-definitions).
-
-## Versioning
-
-This repository is versioned and tagged using the `YY.MM.BUILD` to allow folks to be able to access the state of the software definition at a specific point in time. We do however encourage folks to pull in the latest whenever possible.
-
-## Contributing
-
-For information on contributing to this project please see our [Contributing Documentation](https://github.com/chef/chef/blob/main/CONTRIBUTING.md)
-
-### Run Linux Tests in Docker
-
-Run `.expeditor/run_linux_tests.sh rake` in the ruby image of your choice.
-
-```
-docker run -it --rm -v $PWD:/src -w /src ruby:2.7-buster .expeditor/run_linux_tests.sh rake
-```
-
-### Testing On Ubuntu 18.04 via Docker
-
-#### Interactive Testing
-
-If you want to enter an interactive shell in a dockerized omnibus build environment on Ubuntu 18.04 you can run the following command.
-
-```
-docker-compose run --rm -e SOFTWARE=<SOFTWARE> -e VERSION=<VERSION> builder
-
-# Example
-docker-compose run --rm -e SOFTWARE=go -e VERSION=1.17.6 builder
-```
-
-Now you should be in a shell in the container ready to explore, modify or build. The omnibus-software repository will be mounted inside the container which makes it easy to edit code with your editor and test it in the container.
-
-You can start the build by running the following command in your shell.
-
-```
-bundle exec omnibus build test
-```
-
-Omnibus git caching is enabled for the build so you can rerun the build command and it will use the cache for any software that was already successfully built. This can save a lot of time when troubleshooting software that has dependencies on other software that builds fine.
-
-The following command will clean the omnibus project and purge the packages and caches.
-
-```
-bundle exec omnibus clean test --purge
-```
-
-The container will automatically be destroyed when you exit it without requiring any further cleanup.
-
-#### Non-Interactive Testing
-
-If you only want to run a build without an interactive shell you can set the `CI` environment variable as you see in the following command.
-
-```
-docker-compose run --rm -e SOFTWARE=<SOFTWARE> -e VERSION=<VERSION> -e CI=true builder
-```
-
-The container will automatically be destroyed when you exit it without requiring any further cleanup.
-
-## License & Copyright
-
-- Copyright:: Copyright (c) 2012-2021 Chef Software, Inc.
-- License:: Apache License, Version 2.0
-
-```text
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
-```