octopus-serverspec-extensions 0.17.1 → 0.19.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 5633418a1e8ae85805eeabef99aac9421b8fac79aa712af8561b269a2255dc8b
-  data.tar.gz: e03edfa9c91ca5e619942596655ce0c59b23b9f9175e7bd00b936458374982ed
+  metadata.gz: 158a488c7284b8d249affc20bcb90eee1e26a6700b66bbc3da3469c143d0352b
+  data.tar.gz: e9a8c680b4c4606672565c12663d5ad4f9051f59617c0d69aa73338f3afa42ec
 SHA512:
-  metadata.gz: 8cb9a7fa6a56d69103d8c458f1b890410754a72b558f665cdca0edf57c889b85ed4caa72f84ed6216dc81a8416aa577d2fb1c99d11dc075103e9ed676614c8dc
-  data.tar.gz: 81a37c15a7386cdf2cb43b40ab1ec3920b210be2b72a9d41b33322c308ea84028cef64f5b0821edd22944cbe075ca0bf0461f012639491c8bb3109320eac74a7
+  metadata.gz: efdeb27913b617b7e1e7bddc7f22893eeeed3f743fd02fba39c0c1a16cb94627a45256c687ec9f63aa30a6f7b9b0812ddf0384d9e8bbc668c7e4c18a517d38ee
+  data.tar.gz: c4efe6b587317aec62c5447761af436f4dd482edbab5b9160902fdc236fa1df4527a8392c6219079c5ddc98a04dff43006c0f80f91f3155bdea12b8bfe0199f7

data/.gitignore

@@ -1,14 +1,14 @@
-/.bundle/
-/.yardoc
-/Gemfile.lock
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-octopus-serverspec-extensions-*.gem
-vendor/
-/.idea/
-publish.ps1
-/.scratch/
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+octopus-serverspec-extensions-*.gem
+vendor/
+/.idea/
+publish.ps1
+/.scratch/

data/.rspec

@@ -1,2 +1,2 @@
---format documentation
---color
+--format documentation
+--color

data/.travis.yml

@@ -1,5 +1,5 @@
-sudo: false
-language: ruby
-rvm:
-  - 2.3.1
-before_install: gem install bundler -v 1.13.6
+sudo: false
+language: ruby
+rvm:
+  - 2.3.1
+before_install: gem install bundler -v 1.13.6

data/Gemfile

@@ -1,4 +1,4 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in octopus-serverspec-extensions.gemspec
-gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in octopus-serverspec-extensions.gemspec
+gemspec

data/LICENSE.txt

@@ -1,12 +1,12 @@
-Copyright (c) Octopus Deploy and contributors. All rights reserved.
-
-Licensed under the Apache License, Version 2.0 (the "License"); you may not use
-these files 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.
+Copyright (c) Octopus Deploy and contributors. All rights reserved.
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use
+these files 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,39 +1,39 @@
-# Octopus::Serverspec::Extensions
-
-SeverSpec extensions for Windows, adding support for chocolatey packages, npm packages, service accounts and more.
-
-## Installation
-
-Add this line to your application's Gemfile:
-
-```ruby
-gem 'octopus-serverspec-extensions'
-```
-
-And then execute:
-
-    $ bundle
-
-Or install it yourself as:
-
-    $ gem install octopus-serverspec-extensions
-
-## Usage
-
-TODO: Write usage instructions here
-
-## Development
-
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
-
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
-
-## Contributing
-
-Bug reports and pull requests are welcome on GitHub at https://github.com/octopus-deploy/octopus-serverspec-extensions.
-
-
-## License
-
-The gem is available as open source under the terms of the [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0).
-
+# Octopus::Serverspec::Extensions
+
+SeverSpec extensions for Windows, adding support for chocolatey packages, npm packages, service accounts and more.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'octopus-serverspec-extensions'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install octopus-serverspec-extensions
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/octopus-deploy/octopus-serverspec-extensions.
+
+
+## License
+
+The gem is available as open source under the terms of the [Apache 2.0 License](http://www.apache.org/licenses/LICENSE-2.0).
+

data/Rakefile

@@ -1,6 +1,6 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/console

@@ -1,14 +1,14 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "octopus/serverspec/extensions"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-require "irb"
-IRB.start
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "octopus/serverspec/extensions"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start

data/bin/setup

@@ -1,8 +1,8 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/docs/authentication.md

@@ -1,45 +1,45 @@
-# Authenticating to your Octopus Server
-
-There are two main ways of authenticating to your Octopus Server from your ServerSpec tests.
-
-#### 1. Using Automatic Environment Variables
-
-If you do not provide a URL and API key in your type call, the type will try to fall back to environment variables.
-
-This option is much cleaner to read, and helps to protect you from leaked credentials, but can be less explicit if you're testing against multiple Octopus Instances.
-
-| Variable              | Description                                                                             |
-|:----------------------|:----------------------------------------------------------------------------------------|
-| OCTOPUS_CLI_SERVER    | The http or https URL of your Octopus Deploy server: e.g. https://octopus.example.com/  |
-| OCTOPUS_CLI_API_KEY   | A valid API key, with rights to view the resources you're testing                       |
-
-The following example will attempt to use the Environment variables. If they are not present, it will raise an exception:
-
-```ruby
-describe octopus_deploy_account('myawsaccount').in_space('Octopus') do
-    it { should exist }
-end
-``` 
-
-#### 2. Provide creds with each type
-
-This method makes sense if you're testing multiple Octopus Servers in the same ruby script, and need a visual cue to which servers you're testing in a specific block.
- 
-Simply provide the URL and API key of your Octopus server as the first two parameters in your type
-
-The following example will connect to a specific server using a specific API key:
-
-```ruby
-describe octopus_deploy_account('https://octopus.example.com/', 'API-1234ABCDE5678FGHI', 'myawsaccount').in_space('Octopus') do
-    it { should exist }
-end
-``` 
-
-#### 3. Using your own Environment Variables
-You can provide the types with a different environment variable by using Ruby's `ENV[]` hash. 
-
-```ruby
-describe octopus_deploy_smtp_config(ENV['MY_OCTOPUS_URL'], ENV['MY_OCTOPUS_API_KEY']) do
-  it { should be_configured }
-end
-```
+# Authenticating to your Octopus Server
+
+There are two main ways of authenticating to your Octopus Server from your ServerSpec tests.
+
+#### 1. Using Automatic Environment Variables
+
+If you do not provide a URL and API key in your type call, the type will try to fall back to environment variables.
+
+This option is much cleaner to read, and helps to protect you from leaked credentials, but can be less explicit if you're testing against multiple Octopus Instances.
+
+| Variable              | Description                                                                             |
+|:----------------------|:----------------------------------------------------------------------------------------|
+| OCTOPUS_CLI_SERVER    | The http or https URL of your Octopus Deploy server: e.g. https://octopus.example.com/  |
+| OCTOPUS_CLI_API_KEY   | A valid API key, with rights to view the resources you're testing                       |
+
+The following example will attempt to use the Environment variables. If they are not present, it will raise an exception:
+
+```ruby
+describe octopus_deploy_account('myawsaccount').in_space('Octopus') do
+    it { should exist }
+end
+``` 
+
+#### 2. Provide creds with each type
+
+This method makes sense if you're testing multiple Octopus Servers in the same ruby script, and need a visual cue to which servers you're testing in a specific block.
+ 
+Simply provide the URL and API key of your Octopus server as the first two parameters in your type
+
+The following example will connect to a specific server using a specific API key:
+
+```ruby
+describe octopus_deploy_account('https://octopus.example.com/', 'API-1234ABCDE5678FGHI', 'myawsaccount').in_space('Octopus') do
+    it { should exist }
+end
+``` 
+
+#### 3. Using your own Environment Variables
+You can provide the types with a different environment variable by using Ruby's `ENV[]` hash. 
+
+```ruby
+describe octopus_deploy_smtp_config(ENV['MY_OCTOPUS_URL'], ENV['MY_OCTOPUS_API_KEY']) do
+  it { should be_configured }
+end
+```

data/docs/octopus_deploy_account.md

@@ -1,37 +1,37 @@
-# octopus_deploy_account
-
-Describes an [Octopus Infrastructure Account](https://octopus.com/docs/infrastructure/accounts).
-
-A number of properties of Accounts (such as passwords & secret keys) are [sensitive]() values, therefore we can't directly test them. 
-
-## Example
-
-```ruby
-
-describe octopus_deploy_account("myawsaccount").in_space("Octopus") do
-    it { should exist }
-    it { should be_aws_account }
-    it { should_not be_azure_account }
-    it { should have_description('My main AWS account') }
-end
-
-```
-
-#### Type
-
-```ruby
-octopus_deploy_account([server_url, api_key], account_name)
-octopus_account([server_url, api_key], account_name)
-```
-
-#### Matchers
-
-| Matcher | Description |
-|:--------|:------------|
-| should exist | Tests if an account of the name exists |
-| should be_aws_account | Amazon Web Services account |
-| should be_azure_account | Microsoft Azure account   |
-| should be_ssh_key_pair | SSH keypair |
-| should be_token | A token for use with services such as Kubernetes| 
-| should be_username_password | A username and password for use with services supporting user/pass |
-
+# octopus_deploy_account
+
+Describes an [Octopus Infrastructure Account](https://octopus.com/docs/infrastructure/accounts).
+
+A number of properties of Accounts (such as passwords & secret keys) are [sensitive]() values, therefore we can't directly test them. 
+
+## Example
+
+```ruby
+
+describe octopus_deploy_account("myawsaccount").in_space("Octopus") do
+    it { should exist }
+    it { should be_aws_account }
+    it { should_not be_azure_account }
+    it { should have_description('My main AWS account') }
+end
+
+```
+
+#### Type
+
+```ruby
+octopus_deploy_account([server_url, api_key], account_name)
+octopus_account([server_url, api_key], account_name)
+```
+
+#### Matchers
+
+| Matcher | Description |
+|:--------|:------------|
+| should exist | Tests if an account of the name exists |
+| should be_aws_account | Amazon Web Services account |
+| should be_azure_account | Microsoft Azure account   |
+| should be_ssh_key_pair | SSH keypair |
+| should be_token | A token for use with services such as Kubernetes| 
+| should be_username_password | A username and password for use with services supporting user/pass |
+

data/docs/octopus_deploy_doc_template.md

@@ -1,17 +1,17 @@
-# octopus_deploy_user
-
-
-
-## Example
-
-
-#### Type
-
-```ruby
-
-```
-
-#### Matchers
-
-| Matcher | Description |
+# octopus_deploy_user
+
+
+
+## Example
+
+
+#### Type
+
+```ruby
+
+```
+
+#### Matchers
+
+| Matcher | Description |
 |:--------|:------------|

data/docs/octopus_deploy_environment.md

@@ -1,33 +1,33 @@
-# octopus_deploy_environment
-
-Tests an Octopus Deploy [Environment](https://octopus.com/docs/infrastructure/environments) resource.
-
-## Example
-
-```ruby
-describe octopus_deploy_environment('Production').in_space('Team Octopus') do
-  it { should exist }
-end
-```
-
-#### Type
-
-This type can be instantiated in several ways, depending on [how you authenticate](authentication.md), and whether your target environment is in a [Space](https://octopus.com/blog/spaces-introduction).
-
-```ruby
-octopus_deploy_environment(url, api_key, environment_name)                 # url and apikey provided
-octopus_deploy_environment(environment_name)                               # using environment vars
-octopus_environment(environment_name).in_space(space_name)                 # using environment vars, in a [space](https://octopus.com/blog/spaces-introduction)
-octopus_environment(url, api_key, environment_name)
-octopus_environment(environment_name)
-octopus_environment(url, api_key, environment_name).in_space(space_name)
-```
-
-#### Matchers
-
-| Matcher | Description |
-|:--------|:------------|
-| should exist | Tests for the existence of a given Environment |
-| should use_guided_failure | Tests if the Environment has the Use Guided Failure default applied |
-| should allow_dynamic_infrastructure | Tests if the checkbox for [Allow Dynamic Infrastructure](https://octopus.com/docs/infrastructure/environments#enabling-dynamic-infrastructure) is checked |
+# octopus_deploy_environment
+
+Tests an Octopus Deploy [Environment](https://octopus.com/docs/infrastructure/environments) resource.
+
+## Example
+
+```ruby
+describe octopus_deploy_environment('Production').in_space('Team Octopus') do
+  it { should exist }
+end
+```
+
+#### Type
+
+This type can be instantiated in several ways, depending on [how you authenticate](authentication.md), and whether your target environment is in a [Space](https://octopus.com/blog/spaces-introduction).
+
+```ruby
+octopus_deploy_environment(url, api_key, environment_name)                 # url and apikey provided
+octopus_deploy_environment(environment_name)                               # using environment vars
+octopus_environment(environment_name).in_space(space_name)                 # using environment vars, in a [space](https://octopus.com/blog/spaces-introduction)
+octopus_environment(url, api_key, environment_name)
+octopus_environment(environment_name)
+octopus_environment(url, api_key, environment_name).in_space(space_name)
+```
+
+#### Matchers
+
+| Matcher | Description |
+|:--------|:------------|
+| should exist | Tests for the existence of a given Environment |
+| should use_guided_failure | Tests if the Environment has the Use Guided Failure default applied |
+| should allow_dynamic_infrastructure | Tests if the checkbox for [Allow Dynamic Infrastructure](https://octopus.com/docs/infrastructure/environments#enabling-dynamic-infrastructure) is checked |