chef-apply 0.1.2 → 0.1.15

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3a54dba100bb799ac0f8ca9be4be3ad58417503b8569e4a680253797aea1b224
-  data.tar.gz: 5c9a8c1b67027704995776ffdab56cf4253ce71a78dbbc9b4d2b1b44123d1234
+  metadata.gz: 0df85558e397b290c68203bfc9aa7aaabcee645005f7823a674f65b85104995a
+  data.tar.gz: 7883623a75def593e7c9a0511902e710eef87cb3c2fc9ebf6029c5a2e2751cbd
 SHA512:
-  metadata.gz: 03a2c835d18864aad23a3936ea2b05da1b0e7cb48dcfe0cf0adfa7373aef57a5dd56752c7b5571cb57e530642846ca208678523dfdf1996be4549decf4a1dadb
-  data.tar.gz: 4684c9dd0a76a42774b80634784a611ccbb189ab7a55b78496d76f1c197ef1018190a6164e6cca7f90720f8d7aa9981caacb1a0810a599dcc988397e98c69d64
+  metadata.gz: a3b814a29f688ccbc498ea6c5c7f701952e1f64e117e3edafffb9e92d89eda04ab312a6341b183ed48d3426d0158b4c163855ad666b22dca47befb1fe8291bca
+  data.tar.gz: ffcf3eee2345331f815537d322aab9a51392a118e8a140c324e0a56c284198d3acfb2bcb105ad6f10d13e82672aed6ebed6450c84441490bafc054305b83953d

data/Gemfile.lock

@@ -18,7 +18,7 @@ GIT
 PATH
   remote: .
   specs:
-    chef-apply (0.1.2)
+    chef-apply (0.1.15)
       chef (>= 14.0)
       chef-dk (>= 3.0)
       chef-telemetry
@@ -38,13 +38,13 @@ GEM
     addressable (2.5.2)
       public_suffix (>= 2.0.2, < 4.0)
     ast (2.4.0)
-    aws-sdk (2.11.86)
-      aws-sdk-resources (= 2.11.86)
-    aws-sdk-core (2.11.86)
+    aws-sdk (2.11.95)
+      aws-sdk-resources (= 2.11.95)
+    aws-sdk-core (2.11.95)
       aws-sigv4 (~> 1.0)
       jmespath (~> 1.0)
-    aws-sdk-resources (2.11.86)
-      aws-sdk-core (= 2.11.86)
+    aws-sdk-resources (2.11.95)
+      aws-sdk-core (= 2.11.95)
     aws-sigv4 (1.0.3)
     azure_mgmt_resources (0.16.0)
       ms_rest_azure (~> 0.10.0)
@@ -237,14 +237,14 @@ GEM
       mixlib-log
     mixlib-authentication (2.1.1)
     mixlib-cli (1.7.0)
-    mixlib-config (2.2.12)
+    mixlib-config (2.2.13)
       tomlrb
     mixlib-install (3.11.2)
       mixlib-shellout
       mixlib-versioning
       thor
     mixlib-log (2.0.4)
-    mixlib-shellout (2.3.2)
+    mixlib-shellout (2.4.0)
     mixlib-versioning (1.2.2)
     molinillo (0.6.5)
     ms_rest (0.7.2)
@@ -268,7 +268,7 @@ GEM
     net-ssh-multi (1.2.1)
       net-ssh (>= 2.6.5)
       net-ssh-gateway (>= 1.2.0)
-    net-telnet (0.1.1)
+    net-telnet (0.2.0)
     nori (2.6.0)
     ohai (14.3.0)
       chef-config (>= 12.8, < 15)
@@ -304,9 +304,9 @@ GEM
       binding_of_caller (>= 0.7)
       pry (>= 0.9.11)
     public_suffix (3.0.2)
-    r18n-core (3.0.4)
-    r18n-desktop (3.0.4)
-      r18n-core (= 3.0.4)
+    r18n-core (3.0.5)
+    r18n-desktop (3.0.5)
+      r18n-core (= 3.0.5)
     rack (2.0.5)
     rainbow (3.0.0)
     rake (12.3.1)
@@ -371,8 +371,8 @@ GEM
     toml-rb (1.1.1)
       citrus (~> 3.0, > 3.0)
     tomlrb (1.2.7)
-    tty-color (0.4.2)
-    tty-cursor (0.5.0)
+    tty-color (0.4.3)
+    tty-cursor (0.6.0)
     tty-spinner (0.8.0)
       tty-cursor (>= 0.5.0)
     unf (0.1.4)

data/README.md

@@ -1,8 +1,7 @@
-# Chef Run
+# Chef Apply
+[![Gem Version](https://badge.fury.io/rb/chef-apply.svg)](https://badge.fury.io/rb/chef-apply)
 
-Welcome to your new gem! In this directory, you'll find the files you need to be able to package up your Ruby library into a gem. Put your Ruby code in the file `lib/chef_apply`.
-
-TODO: Delete this and the text above, and describe your gem
+The ad-hoc execution tool for the Chef ecosystem.
 
 ## Installation
 
@@ -20,22 +19,38 @@ Or install it yourself as:
 
     $ gem install chef-apply
 
-## Usage
 
-TODO: Write usage instructions here
+## Contributing/Development
+
+Please read our [Community Contributions Guidelines](https://docs.chef.io/community_contributions.html), and ensure you are signing all your commits with DCO sign-off.
 
-## Development
+The general development process is:
 
-TODO: Write usage development here
+1. Fork this repo and clone it to your workstation.
+2. Create a feature branch for your change.
+3. Write code and tests.
+4. Push your feature branch to GitHub and open a pull request against master.
 
-## Contributing
+Once your repository is set up, you can start working on the code. We do utilize RSpec for test driven development, so you'll need to get a development environment running. Follow the above procedure ("Installing from Git") to get your local copy of the source running.
 
-TODO: Write usage contributing here
+# License
 
-## License
+|                      |                                          |
+|:---------------------|:-----------------------------------------|
+| **Copyright:**       | Copyright 2018, Chef Software, Inc.
+| **License:**         | Apache License, Version 2.0
 
-The gem is available as open source under the terms of the [Apache License, Version 2.0](https://opensource.org/licenses/Apache-2.0).
+```
+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
 
-## Code of Conduct
+    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.
+```
 
-TODO: Write usage code of conduct here

data/i18n/en.yml

@@ -158,356 +158,32 @@ cli:
     connection_failed: "Connection failed: %1"
 
 status:
-  generate_policyfile:
-    generating:  Generating local policyfile...
-    success: Generated local policyfile
+  generate_temp_cookbook:
+    generating: Packaging cookbook...
+    success: Packaging cookbook... done!
+  generate_local_policy:
+    generating: Generating local policyfile...
+    exporting:  Generating local policyfile... exporting...
+    success: Generating local policyfile... exporting... done!
   install_chef:
-    installing: Installing Chef client version %1.
     checking_for_client: Checking for Chef client.
-    upgrading: Upgrading Chef client from version %1 to %2.
+    verifying: Verifying Chef client installation.
     downloading: Downloading Chef client installer into local cache.
     uploading: Uploading Chef client installer to target.
-    verifying: Verifying Chef client installation.
+    installing: Installing Chef client version %1.
+    upgrading: Upgrading Chef client from version %1 to %2.
     already_present: Chef client version %1 already installed on target.
     install_success: Successfully installed Chef client version %1
     upgrade_success: Successfully upgraded Chef client from version %1 to %2.
     failure: "An error occurred while installing Chef client: %1"
   converge:
-    multi_header: "Converging targets:"
-    converging_recipe: Converging local recipe %1 on target...
-    converging_resource: Converging %1 on target...
+    header: !!pl
+      1: Applying %2 from %3 to target.
+      n: Applying %2 from %3 to targets.
+    converging: Applying %1...
     creating_local_policy: Creating local policy...
     creating_remote_policy: Pushing remote policy to target...
     uploading_trusted_certs: Uploading local trusted certs to target...
-    running_chef: Running Chef on target...
-    success: "Successfully converged target!"
-    failure: "Failed to converge target."
+    success: "Successfully converged %1."
+    failure: "Failed to converge %1."
     reboot: "Reboot scheduled on target."
-
-# Error definitions, usage Text.e.ERR999
-# General format:
-# First Line: brief description of the error
-# Second line: blank
-# Third+ : detailed description, max 76 characters per line
-errors:
-  # Catch-all for the worst case
-  UNKNOWN: An unknown error has occurred.
-
-  # Installer action errors
-  CHEFINS002: |
-    The target does not have chef-client installed.
-
-    This command is powered by the Chef client.  In order to make use of it
-    on this node, the Chef client must be installed first.
-
-    Re-running this command without the '--no-install' flag will
-    automatically perform the installation.
-
-  CHEFINS003: |
-    The target has an older version of Chef client installed.
-
-    The target has version %1 installed, but this command
-    requires a minimum version of %2.
-
-    Please upgrade the Chef client on this node to version %2 or later.
-
-  # Local errors trying to create policy to send to target
-  CHEFPOLICY001: |
-    Could not create local Policyfile bundle.
-
-    The following error was reported:
-
-      %1
-
-  # Remote execution and file operation errors are prefixed CHEFRMT
-  CHEFRMT001: |
-    The command '%1' exited with return code '%2' on '%3'.
-
-    The following error was reported:
-
-      %4
-
-  # Remote chef client run failure start here.
-  CHEFCCR001: |
-    Could not determine reason for converge failure.
-
-    STDOUT (may be blank)
-
-      %1
-
-    STDERR (may be blank)
-
-      %2
-
-    An error occurred while converging the remote host.
-    I was unable to retrieve the log file which would allow
-    me to provide more information.  Above is the output
-    that occurred while trying to retrieve the remote log file.
-
-  CHEFCCR002: |
-    The converge of the remote host failed for the
-    following reason:
-
-      %1
-
-  CHEFCCR003: |
-    The action '%1' is not valid.
-
-    Valid actions are:
-
-      %2
-
-    For more information, please consult the documentation
-    for this resource:
-
-      https://docs.chef.io/resource_reference.html
-
-  CHEFCCR004: |
-    A property value you provided is not valid:
-
-      %1
-
-    Please consult the documentation for properties
-    supported by your resource and their valid values:
-
-      https://docs.chef.io/resource_reference.html
-
-  CHEFCCR005: |
-    '%1' is not a valid Chef resource.
-
-    Please consult the documentation for a list of valid resources:
-
-      https://docs.chef.io/resource_reference.html
-
-  CHEFCCR006: |
-    '%1' is not a property of '%2'.
-
-    Please consult the documentation for %2 for a list of
-    valid properties:
-
-      https://docs.chef.io/resource_reference.html
-
-  CHEFCCR099: |
-    The converge of the remote host failed.
-
-    Please examine the log file for a detailed cause of failure.
-
-  # Train-related errors (connectivy, auth failure, etc)
-  # are prefixed CHEFTRN. Non-specific descendants of Train::Error
-  # will resolve to CHEFTRN001, and we can add additional
-  # more specific text as we need it.
-  CHEFTRN001: |
-    An error has occurred on the %1 connection to %2:
-
-    %2.
-
-  CHEFTRN002: |
-    An remote error has occurred:
-
-      %1.
-
-  CHEFTRN003: |
-    Password required for sudo.
-
-    This target requires a password to perform sudo operations.  Please provide a
-    password using the --sudo-password option. For example if the sudo password is
-    in the environment variable $CHEF_RUN_SUDO_PASSWORD, you could use:
-
-    --sudo-password $CHEF_RUN_SUDO_PASSWORD
-
-  CHEFTRN004: |
-    Incorrect sudo password provided.
-
-    Please ensure that the password you provided with "--sudo-password" is correct.
-
-  CHEFTRN005: |
-    sudo command '%1' not found.
-
-    Please verify that the --sudo-command '%1' is valid
-    and installed on this node.
-
-  CHEFTRN006: |
-    sudo requires tty on this system
-
-    In order to continue, sudo must be configured to no longer require tty.
-    You can do this by modifying /etc/sudoers:
-
-    For all users:
-      Defaults !requiretty
-
-    Per-user:
-      Defaults:username !requiretty
-
-  CHEFTRN007: |
-    No authentication methods available.
-
-    Try...
-    - Provide a password with "--password PASSWORD"
-    - Provide a key with "-identity-file PATH/TO/FILE"
-    - Enable ssh-agent and add keys
-    - Add a host entry to your ssh configuration
-
-    Additional instructions can be found in the troubleshooting documentation:
-
-    https://www.chef.sh/docs/chef-workstation/troubleshooting/#error-code-cheftrn007
-
-  CHEFTRN999: |
-    Connection failed: %1
-
-    The following error occured while attempting to connect and authenticate to the target.
-
-    %1
-
-  # CLI argument validation errors
-  CHEFVAL002: |
-    You must supply <TARGET[S]> and either <RESOURCE> and <RESOURCE_NAME> or <RECIPE>
-
-  CHEFVAL003: |
-    Property '%1' did not match the 'key=value' syntax required
-
-  CHEFVAL004: |
-    Please provide a recipe in the form 'path/to/recipe/file.rb',
-    'path/to/cookbook', 'cookbook_name' or 'cookbook_name::recipe_name'.
-
-    You provided '%1'.
-
-  CHEFVAL005: |
-    The cookbook provided could not be loaded. Ensure it contains a valid
-    'metadata.rb'.
-
-    Cookbook path is '%1'.
-
-  CHEFVAL006: |
-    Cookbook '%1' could not be found in any of the following directories
-
-    %2
-
-  CHEFVAL007: |
-    There is no default recipe in cookbook '%2'. Please provide the name of the recipe to run, for example:
-      %2::some_recipe
-
-    Cookbook path is '%1'.
-
-  CHEFVAL008: |
-    There is no recipe named '%2' in the cookbook '%4', which I found at '%1'.
-
-    Please include the name of the recipe you wish to converge on the remote target.
-
-    These are the available recipes in '%4':
-    %3
-
-  CHEFVAL009: |
-    File extension '%1' is unsupported. Currently recipes must be specified with a `.rb` extension.
-
-  CHEFVAL010: |
-    The flag '%1' does not exist.
-
-      Available flags are:
-    %2
-
-  CHEFVAL011: |
-    The protocol '%1' is not supported.
-
-    Currently supported remote access protocols are:
-
-      %2
-
-  # General errors/unknown errors are handled with CHEFINT
-  CHEFINT001: |
-    An unexpected error has occurred:
-
-      %1
-
-  # Maps to: NameError
-  CHEFNET001: |
-    A network error occurred:
-
-      %1
-
-    Please verify the host name or address is correct and that the host is
-    reachable before trying again.
-
-  # Remote chef client run failure start here.
-  CHEFUPL003: |
-    Uploading config to target failed.
-
-  CHEFUPL004: |
-    Uploading handler to target failed.
-
-  CHEFUPL005: |
-    Uploading policy bundle to target failed.
-
-  # Maps to: SSL::SSLError with message text indicating verification failure
-  CHEFNET002: |
-    SSL host verification failed.
-
-    I could not verify the identity of the remote host.
-
-    If you are certain that you are connecting to the correct host,
-    you can specify the '--no-ssl-verify' option for this command, or
-    make it the default by setting the following in your configuration:
-
-      [connection.winrm]
-      ssl_verify=false
-
-  # Errors specifying target ranges
-  CHEFRANGE001: |
-    The target '%1' contains an invalid range.
-
-    The range '%2' mixes alphabetic and numeric values.
-    A range must be one or the other.
-
-  CHEFRANGE002:
-    The target '%1' contains too many ranges.
-
-    A single target name can contain up two ranges.
-
-  CHEFRANGE003: !!pl
-    1:
-      The target provided resolves to too many hosts.
-
-      At this time there is a limit of %2 hosts in a single operation.
-    n:
-      The targets provided resolve to too many hosts.
-
-      At this time there is a limit of %2 hosts in a single operation.
-
-  # Errors related to multi-target execution
-  CHEFMULTI001: |
-    One or more actions has failed.
-
-    A complete list of failures and possible resolutions can
-    be found in the file below:
-
-      %1
-
-  # Errors relating to target state:
-  CHEFTARG001: |
-    '%1' is not a supported target operating system at this time.
-
-    We plan to support a range of target operating systems,
-    but during this targeted beta we are constraining our efforts
-    to Windows and Linux.
-
-  footer:
-    both: |
-      If you are not able to resolve this issue, please contact Chef support
-      at beta@chef.io and include the log file and stack trace from the
-      locations below:
-
-        %1
-        %2
-
-    log_only:  |
-      If you are not able to resolve this issue, please contact Chef support
-      at beta@chef.io and include the log file from the location below:
-        %1
-
-    stack_only:  |
-      If you are not able to resolve this issue, please contact Chef support
-      at beta@chef.io and include the stack trace from the location below:
-        %1
-
-    neither:  |
-      If you are not able to resolve this issue, please contact Chef support
-      at beta@chef.io