knife-clc 0.0.2.pre → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 000fe34de838800cf1f4759fcd93da92641e0ab4
-  data.tar.gz: bb2fc50621cc92e9363f297e30ad32e5e88888df
+  metadata.gz: c0f3c9fab4bde69c1c1137b572f3530cf21fed65
+  data.tar.gz: d1968bb875a1f577a6bf0372065d180d0beb7860
 SHA512:
-  metadata.gz: 3867db4a72e1953f12a618404aef6822ac01bce7e9dfc5ab16776a7beb4dd9bbb38f09fdbde2289a446a19ea2e44443327a6852b5916e4737da40b1b4f8ac3b9
-  data.tar.gz: 3f79fc3d2083a100acb455dbd76ac34af4bf49ae3fbdf422d081307f560d1a5328cce516538ea1acfcbc8d04e2ac3121e491fe04413d960d966d79b3360a4c9f
+  metadata.gz: c13901e423f7973696a24d324f3a5dd17c577b5bc433d343f4a893defcf4366164ecf3833bc85fee1e1950c4336845f69800bb8dc3cb269ad17f78b685330231
+  data.tar.gz: 3f624f4b53f272970606d9158becad7950df5ba38bffb7515e69fc27c357a4d82d8038a6015e540025f29379e72136c98c0616b3d33707a5c8465aedc14e699b

data/README.md

@@ -112,7 +112,7 @@ Specific command options can be found by invoking the subcommand with a `--help`
 * [knife clc server show ID (options)](#knife-clc-server-show)
 * [knife clc template list (options)](#knife-clc-template-list)
 
-**Note:** Some commands provide access to long-running cloud operations. These commands are **asynchronous**(async) by default (they don't wait for the operation to complete before continuing their work and they don't return an output immediately). All of them support the `--wait` option, which makes the command pause until the operation either completes or fails.
+**Note:** Some commands provide access to long-running cloud operations. These commands are **asynchronous** (async) by default (they don't wait for the operation to complete before continuing their work and they don't return an output immediately). All of them support the `--wait` option, which makes the command pause until the operation either completes or fails.
 
 Several types of resources are scoped by the datacenter they reside in. Commands querying for these resources support the `--datacenter ID` option, which returns resources for a specific data center. Some of the commands support the `--all` option, which returns all resources from all data centers (this command is much slower).
 
@@ -142,7 +142,7 @@ $ knife clc group list --datacenter ca1 --view table
 ```
 
 ### `knife clc ip create`
-**Asynchronous**. **Scoped by server**. Assigns a public IP to a specified server. Applies the passes protocol and source restrictions. While the CLC API supports TCP, UDP and ICMP permissions only, this command provides several useful aliases to the most frequently used protocols: `ssh`, `sftp`, `ftp`, `http`, `https`, `ftp`, and `ftps`. These same options can be provided during server creation.
+**Asynchronous**. **Scoped by server**. Assigns a public IP to a specified server. Applies the passes protocol and source restrictions. While the CLC API supports TCP, UDP and ICMP permissions only, this command provides several useful aliases to the most frequently used protocols: `winrm`, `ssh`, `sftp`, `ftp`, `http`, `https`, `ftp`, and `ftps`. These same options can be provided during server creation.
 
 ```bash
 $ knife clc ip create --server ca1altdqasrv01 \
@@ -187,9 +187,13 @@ $ knife clc server create --name 'QASrv' \
 ```
 
 #### Bootstrap flag
-This command supports the `--bootstrap` flag, which allows the launched machine to connect to your Chef Server installation. Only the **Linux** platform is supported.
+This command supports the `--bootstrap` flag, which allows the launched machine to connect to your Chef Server installation. Both **Linux** and **Windows** platforms are supported. Knife determines platform automatically, but it can be overriden by `--botstrap-platform` option. Current implementation bootstraps Linux nodes via SSH, and Windows nodes via WinRM protocol. Bootstrap specific options (as well as platform specific ones) are labelled in command manual accordingly. For example:
 
-The async bootstrap variant does not require public IP access to the machine. Chef Server credentials and other parameters will be sent to the server. They will be used by the Chef Client installation script during launch.
+```bash
+-x, --winrm-user USERNAME        [Bootstrap] (Windows Only) The WinRM username
+```
+
+The asynchronous bootstrap variant does not require public IP access to the machine. Chef Server credentials and other parameters will be sent to the server. They will be used by the Chef Client installation script during launch.
 
 **Note:** Bootstrapping errors will cancel a launch operation.
 
@@ -205,9 +209,9 @@ $ knife clc server create --name 'QASrv' \
 --tags one,two,three
 ```
 
-The synchronous(sync) bootstrap variant is very similar to the bootstrap used in other Knife plugins. It requires an SSH connection to the server.
+The synchronous bootstrap variant is very similar to the bootstrap used in other Knife plugins. It requires an SSH connection to the server.
 
-**Note:** The plugin will refuse to launch a server unless a public IP with SSH access is requested.
+**Note:** The plugin will refuse to launch a server unless a public IP is requested. Linux machines require SSH access port (TCP:22 by default). Windows machines require WinRM access port (defaults to TCP:5985 or TCP:5986 depending on `--winrm-transport`).
 
 Example for custom SSH port:
 

data/lib/knife-clc/version.rb

@@ -1,5 +1,5 @@
 module Knife
   module Clc
-    VERSION = '0.0.2.pre'
+    VERSION = '0.0.2'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: knife-clc
 version: !ruby/object:Gem::Version
-  version: 0.0.2.pre
+  version: 0.0.2
 platform: ruby
 authors:
 - Alexander Sologub
@@ -278,9 +278,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.4.6