opscode-pushy-client 2.5.6 → 2.99.0

data/omnibus/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/omnibus/README.md

@@ -1,141 +0,0 @@
-Client Tools Omnibus project
-============================
-This project creates full-stack platform-specific packages for Push Jobs Client.
-
-Installation
-------------
-You must have a sane Ruby 1.9+ environment with Bundler installed. Ensure all
-the required gems are installed:
-
-```shell
-$ bundle install --without development
-```
-
-Usage
------
-### Build
-
-You create a platform-specific package using the `build project` command:
-
-```shell
-$ bundle exec omnibus build push-jobs-client
-```
-
-The platform/architecture type of the package created will match the platform
-where the `build project` command is invoked. For example, running this command
-on a MacBook Pro will generate a Mac OS X package. After the build completes
-packages will be available in the `pkg/` folder.
-
-### Clean
-
-You can clean up all temporary files generated during the build process with
-the `clean` command:
-
-```shell
-$ bundle exec omnibus clean push-jobs-client
-```
-
-Adding the `--purge` purge option removes __ALL__ files generated during the
-build including the project install directory (`/opt/chef`) and
-the package cache directory (`/var/cache/omnibus/pkg`):
-
-```shell
-$ bundle exec omnibus clean push-jobs-client --purge
-```
-
-### Publish
-
-Omnibus has a built-in mechanism for releasing to a variety of "backends", such
-as Amazon S3 and Artifactory. You must set the proper credentials in your `omnibus.rb`
-config file or specify them via the command line.
-
-```shell
-$ bundle exec omnibus publish path/to/*.deb --backend s3
-```
-
-### Help
-
-Full help for the Omnibus command line interface can be accessed with the
-`help` command:
-
-```shell
-$ bundle exec omnibus help
-```
-
-Kitchen-based Build Environment
--------------------------------
-Every Omnibus project ships will a project-specific
-[Berksfile](http://berkshelf.com/) that will allow you to build your omnibus projects on all of the projects listed
-in the `.kitchen.yml`. You can add/remove additional platforms as needed by
-changing the list found in the `.kitchen.yml` `platforms` YAML stanza.
-
-This build environment is designed to get you up-and-running quickly. However,
-there is nothing that restricts you to building on other platforms. Simply use
-the [omnibus cookbook](https://github.com/opscode-cookbooks/omnibus) to setup
-your desired platform and execute the build steps listed above.
-
-The default build environment requires Test Kitchen and VirtualBox for local
-development. Test Kitchen also exposes the ability to provision instances using
-various cloud providers like AWS, DigitalOcean, or OpenStack. For more
-information, please see the [Test Kitchen documentation](http://kitchen.ci).
-
-Once you have tweaked your `.kitchen.yml` (or `.kitchen.local.yml`) to your
-liking, you can bring up an individual build environment using the `kitchen`
-command.
-
-```shell
-$ kitchen converge push-jobs-client-ubuntu-1204
-```
-
-Then login to the instance and build the project as described in the Usage
-section:
-
-```shell
-$ kitchen login push-jobs-client-ubuntu-1204
-[vagrant@ubuntu...] $ cd opscode-pushy-client/omnibus
-[vagrant@ubuntu...] $ source ~/load-omnibus-toolchain.sh
-[vagrant@ubuntu...] $ bundle install --without development # Don't install dev tools!
-[vagrant@ubuntu...] $ ...
-[vagrant@ubuntu...] $ bundle exec omnibus build push-jobs-client -l internal
-```
-
-You can also login to Windows instances but will have to manually call the
-`load-omnibus-toolchain.bat` script which initializes the build environment.
-Please note the mounted code directory is also at `C:\home\vagrant\opscode-pushy-client\omnibus`
-as opposed to `C:\Users\vagrant\opscode-pushy-client\omnibus`.
-
-```shell
-$ bundle exec kitchen login push-jobs-client-windows-81-professional
-Last login: Sat Sep 13 10:19:04 2014 from 172.16.27.1
-Microsoft Windows [Version 6.3.9600]
-(c) 2013 Microsoft Corporation. All rights reserved.
-
-C:\Users\vagrant>load-omnibus-toolchain.bat
-
-C:\Users\vagrant>cd C:\home\vagrant\opscode-pushy-client\omnibus
-
-C:\home\vagrant\opscode-pushy-client\omnibus>bundle install --without development
-
-C:\home\vagrant\opscode-pushy-client\omnibus>bundle exec omnibus build push-jobs-client -l internal
-```
-
-For a complete list of all commands and platforms, run `kitchen list` or
-`kitchen help`.
-
-License
--------
-```text
-Copyright 2012-2014 Chef Software, Inc.
-
-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/omnibus/acceptance/Berksfile

@@ -1,6 +0,0 @@
-source 'https://supermarket.chef.io'
-
-metadata
-
-cookbook 'apt'
-cookbook 'chef-server-ctl', git: 'https://github.com/stephenlauck/chef-server-ctl.git'

data/omnibus/acceptance/Berksfile.lock

@@ -1,35 +0,0 @@
-DEPENDENCIES
-  apt
-  chef-server-ctl
-    git: https://github.com/stephenlauck/chef-server-ctl.git
-    revision: 55bfa054f9d5cda86f1a96b28b5ccaddbec7a69d
-  push_jobs_acceptance
-    path: .
-    metadata: true
-
-GRAPH
-  apt (5.0.0)
-    compat_resource (>= 12.14.7)
-  chef-ingredient (0.21.2)
-    compat_resource (>= 12.10)
-  chef-server (5.1.0)
-    chef-ingredient (>= 0.18.0)
-  chef-server-ctl (0.1.0)
-    chef-server (>= 0.0.0)
-  compat_resource (12.16.2)
-  hostsfile (2.4.5)
-  packagecloud (0.2.5)
-  push-jobs (3.2.2)
-    chef-ingredient (>= 0.19.0)
-    compat_resource (>= 12.14.6)
-    runit (>= 1.2.0)
-  push_jobs_acceptance (0.1.0)
-    chef-server (>= 0.0.0)
-    chef-server-ctl (>= 0.0.0)
-    hostsfile (>= 0.0.0)
-    push-jobs (>= 0.0.0)
-  runit (3.0.0)
-    packagecloud (>= 0.0.0)
-    yum-epel (>= 0.0.0)
-  yum-epel (2.0.0)
-    compat_resource (>= 12.14.6)

data/omnibus/acceptance/Makefile

@@ -1,13 +0,0 @@
-
-chef-server:
-	kitchen converge chef-server-ubuntu-1404
-
-windows-client:
-	kitchen converge push-jobs-client-windows-2012r2
-
-ubuntu-client:
-	kitchen converge push-jobs-client-ubuntu-1404
-
-clean:
-	find .chef/$* ! -name 'knife.rb' -type f -exec rm -f {} +
-	kitchen destroy

data/omnibus/acceptance/README.md

@@ -1,29 +0,0 @@
-# Push Client Omnibus Local Acceptance Environment
-
-This environment should be use for acceptance testing on Push Jobs Client
-omnibus packages. It's primary purpose is to give you a quick testing
-environment that may or may not fit all your needs.
-
-## Getting Started
-
-First, build your Chef Server.
-
-    make chef-server
-
-Then, build the client of your choice, either Ubuntu OR Windows.
-
-    make ubuntu-client
-    make windows-client
-
-## Using the Windows VM
-
-The default Windows VM listed in the `.kitchen.yml` file is a private image
-available to Chef employees. This is done because of licensing. If you want to
-use your own Windows image, you can override it using a `.kitchen.local.yml`
-or by temporarily over-writing the value in `.kitchen.yml`.
-
-## Cleanup
-
-To destroy the VM and cleanup all the associated artifacts, run the following:
-
-    make clean

data/omnibus/acceptance/metadata.rb

@@ -1,12 +0,0 @@
-name 'push_jobs_acceptance'
-maintainer 'The Authors'
-maintainer_email 'you@example.com'
-license 'all_rights'
-description 'Installs/Configures push-jobs-acceptance'
-long_description 'Installs/Configures push-jobs-acceptance'
-version '0.1.0'
-
-depends 'chef-server'
-depends 'chef-server-ctl'
-depends 'push-jobs'
-depends 'hostsfile'

data/omnibus/acceptance/recipes/chef-server-user-org.rb

@@ -1,31 +0,0 @@
-chef_server_user 'acceptance' do
-  firstname 'Example'
-  lastname 'User'
-  email 'acceptance@push-jobs.test'
-  password 'password'
-  private_key_path '/tmp/acceptance/.chef/acceptance.pem'
-  action :create
-end
-
-chef_server_org 'example' do
-  org_long_name 'Example Organization'
-  org_private_key_path '/tmp/acceptance/.chef/example.pem'
-  action :create
-end
-
-chef_server_org 'example' do
-  admins %w( acceptance )
-  action :add_admin
-end
-
-execute "knife ssl fetch https://192.168.33.30"
-
-execute "create-client" do
-  command "knife client create push-client --disable-editing -c /tmp/acceptance/.chef/knife.rb > /tmp/acceptance/.chef/push-client.pem"
-  not_if "knife client list | grep push-client"
-end
-#
-# execute "create-node" do
-#   command "knife node create push-client -c /tmp/acceptance/.chef/knife.rb"
-#   action :nothing
-# end