test-kitchen 1.23.3 → 1.23.4

data/docs/themes/kitchen/static/sass/vendor/fontawesome/fa-brands.scss

@@ -1,21 +0,0 @@
-/*!
- * Font Awesome Free 5.0.13 by @fontawesome - https://fontawesome.com
- * License - https://fontawesome.com/license (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
- */
-@import 'variables';
-
-@font-face {
-  font-family: 'Font Awesome 5 Brands';
-  font-style: normal;
-  font-weight: normal;
-  src: url('#{$fa-font-path}/fa-brands-400.eot');
-  src: url('#{$fa-font-path}/fa-brands-400.eot?#iefix') format('embedded-opentype'),
-  url('#{$fa-font-path}/fa-brands-400.woff2') format('woff2'),
-  url('#{$fa-font-path}/fa-brands-400.woff') format('woff'),
-  url('#{$fa-font-path}/fa-brands-400.ttf') format('truetype'),
-  url('#{$fa-font-path}/fa-brands-400.svg#fontawesome') format('svg');
-}
-
-.fab {
-  font-family: 'Font Awesome 5 Brands';
-}

data/docs/themes/kitchen/static/sass/vendor/fontawesome/fa-regular.scss

@@ -1,22 +0,0 @@
-/*!
- * Font Awesome Free 5.0.13 by @fontawesome - https://fontawesome.com
- * License - https://fontawesome.com/license (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
- */
-@import 'variables';
-
-@font-face {
-  font-family: 'Font Awesome 5 Free';
-  font-style: normal;
-  font-weight: 400;
-  src: url('#{$fa-font-path}/fa-regular-400.eot');
-  src: url('#{$fa-font-path}/fa-regular-400.eot?#iefix') format('embedded-opentype'),
-  url('#{$fa-font-path}/fa-regular-400.woff2') format('woff2'),
-  url('#{$fa-font-path}/fa-regular-400.woff') format('woff'),
-  url('#{$fa-font-path}/fa-regular-400.ttf') format('truetype'),
-  url('#{$fa-font-path}/fa-regular-400.svg#fontawesome') format('svg');
-}
-
-.far {
-  font-family: 'Font Awesome 5 Free';
-  font-weight: 400;
-}

data/docs/themes/kitchen/static/sass/vendor/fontawesome/fa-solid.scss

@@ -1,23 +0,0 @@
-/*!
- * Font Awesome Free 5.0.13 by @fontawesome - https://fontawesome.com
- * License - https://fontawesome.com/license (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
- */
-@import 'variables';
-
-@font-face {
-  font-family: 'Font Awesome 5 Free';
-  font-style: normal;
-  font-weight: 900;
-  src: url('#{$fa-font-path}/fa-solid-900.eot');
-  src: url('#{$fa-font-path}/fa-solid-900.eot?#iefix') format('embedded-opentype'),
-  url('#{$fa-font-path}/fa-solid-900.woff2') format('woff2'),
-  url('#{$fa-font-path}/fa-solid-900.woff') format('woff'),
-  url('#{$fa-font-path}/fa-solid-900.ttf') format('truetype'),
-  url('#{$fa-font-path}/fa-solid-900.svg#fontawesome') format('svg');
-}
-
-.fa,
-.fas {
-  font-family: 'Font Awesome 5 Free';
-  font-weight: 900;
-}

data/docs/themes/kitchen/static/sass/vendor/fontawesome/fontawesome.scss

@@ -1,16 +0,0 @@
-/*!
- * Font Awesome Free 5.0.13 by @fontawesome - https://fontawesome.com
- * License - https://fontawesome.com/license (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
- */
-@import 'variables';
-@import 'mixins';
-@import 'core';
-@import 'larger';
-@import 'fixed-width';
-@import 'list';
-@import 'bordered-pulled';
-@import 'animated';
-@import 'rotated-flipped';
-@import 'stacked';
-@import 'icons';
-@import 'screen-reader';

data/docs/themes/kitchen/theme.toml

@@ -1,8 +0,0 @@
-name = "kitchen"
-license = "Apache-2"
-licenselink = "https://github.com/yourname/yourtheme/blob/master/LICENSE.md"
-description = "The theme used for KitchenCI"
-homepage = "http://github.com/chef/chef-hugo-theme"
-tags = []
-features = []
-min_version = "0.38"

data/features/kitchen_action_commands.feature

@@ -1,164 +0,0 @@
-Feature: Running instance actions
-  In order to trigger discrete instance lifecyle actions
-  As an operator
-  I want to run a action commands
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    verifier:
-      name: dummy
-
-    platforms:
-      - name: cool
-      - name: beans
-
-    suites:
-      - name: client
-      - name: server
-    """
-
-  @spawn
-  Scenario: Creating a single instance
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+\<Not Created\>\s+\<None\>\Z/
-    When I run `kitchen create client-beans`
-    Then the output should contain "Finished creating <client-beans>"
-    And the exit status should be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+\<None\>\Z/
-
-  @spawn
-  Scenario: Creating a single instance that fails
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    driver:
-      fail_create: true
-    """
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+\<Not Created\>\s+\<None\>\Z/
-    When I run `kitchen create client-beans`
-    Then the output should contain "Create failed on instance <client-beans>"
-    And the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+\<Not Created\>\s+Kitchen::ActionFailed\Z/
-
-  @spawn
-  Scenario: Converging a single instance
-    When I successfully run `kitchen create client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+\<None\>\Z/
-    When I run `kitchen converge client-beans`
-    Then the output should contain "Finished converging <client-beans>"
-    And the exit status should be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Converged\s+\<None\>\Z/
-
-  @spawn
-  Scenario: Converging a single instance that fails
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    provisioner:
-      fail: true
-    """
-    When I successfully run `kitchen create client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+\<None\>\Z/
-    When I run `kitchen converge client-beans`
-    Then the output should contain "Converge failed on instance <client-beans>"
-    And the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+Kitchen::ActionFailed\Z/
-
-  @spawn
-  Scenario: Setting up a single instance
-    When I successfully run `kitchen converge client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Converged\s+\<None\>\Z/
-    When I run `kitchen setup client-beans`
-    Then the output should contain "Finished setting up <client-beans>"
-    And the exit status should be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Set Up\s+\<None\>\Z/
-
-  @spawn
-  Scenario: Setting up a single instance that fails
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    verifier:
-      fail: true
-    """
-    When I successfully run `kitchen converge client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Converged\s+\<None\>\Z/
-    When I run `kitchen verify client-beans`
-    Then the output should contain "Verify failed on instance <client-beans>"
-    And the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Set Up\s+Kitchen::ActionFailed\Z/
-
-  @spawn
-  Scenario: Verifying a single instance
-    When I successfully run `kitchen setup client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Set Up\s+\<None\>\Z/
-    When I run `kitchen verify client-beans`
-    Then the output should contain "Finished verifying <client-beans>"
-    And the exit status should be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Verified\s+\<None\>\Z/
-
-  @spawn
-  Scenario: Verifying a single instance that fails
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    verifier:
-      fail: true
-    """
-    When I successfully run `kitchen setup client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Set Up\s+\<None\>\Z/
-    When I run `kitchen verify client-beans`
-    Then the output should contain "Verify failed on instance <client-beans>"
-    And the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Set Up\s+Kitchen::ActionFailed\Z/
-
-  @spawn
-  Scenario: Destroying a single instance
-    When I successfully run `kitchen create client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+\<None\>\Z/
-    When I run `kitchen destroy client-beans`
-    Then the output should contain "Finished destroying <client-beans>"
-    And the exit status should be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+\<Not Created\>\s+\<None\>\Z/
-
-  @spawn
-  Scenario: Destroying a single instance that fails
-    Given a file named ".kitchen.local.yml" with:
-    """
-    ---
-    driver:
-      fail_destroy: true
-    """
-    When I successfully run `kitchen create client-beans`
-    And I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+\<None\>\Z/
-    When I run `kitchen destroy client-beans`
-    Then the output should contain "Destroy failed on instance <client-beans>"
-    And the exit status should not be 0
-    When I successfully run `kitchen list client-beans`
-    Then the stdout should match /^client-beans\s+.+\s+Created\s+Kitchen::ActionFailed\Z/

data/features/kitchen_command.feature

@@ -1,16 +0,0 @@
-Feature: A command line interface for Test Kitchen
-  In order to provide a quick and response development workflow
-  As a Test Kitchen user
-  I want a command line interface that has sane defaults and built in help
-
-  @spawn
-  Scenario: Displaying help
-    When I run `kitchen help`
-    Then the exit status should be 0
-    And the output should contain "kitchen console"
-    And the output should contain "kitchen version"
-
-  Scenario: Displaying the version of Test Kitchen
-    When I run `kitchen version`
-    Then the exit status should be 0
-    And the output should contain "Test Kitchen version"

data/features/kitchen_console_command.feature

@@ -1,35 +0,0 @@
-@ignore
-Feature: Running a console command
-  In order to interactively explore Kitchen's internals and wiring
-  As an opterator
-  I want to run a command to launch an interactive console session
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    platforms:
-      - name: flebian
-
-    suites:
-      - name: default
-      - name: full
-    """
-
-  @spawn
-  Scenario: Launching a session
-    When I run `kitchen console` interactively
-    And I type "instances.map { |i| i.name }"
-    And I type "exit"
-    Then the output should contain "kc(Kitchen::Config)> "
-    Then the output should contain:
-    """
-    ["default-flebian", "full-flebian"]
-    """
-    And the exit status should be 0

data/features/kitchen_defaults.feature

@@ -1,38 +0,0 @@
-Feature: Test Kitchen defaults
-  In order to have a more pleasant out of the box experience
-  As a user of Test Kitchen
-  I want to have some common defaults handled for me
-
-  Scenario: Windows platforms get the Winrm Transport by default
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver: dummy
-    provisioner: dummy
-    verifier: dummy
-
-    platforms:
-      - name: win-8.1
-
-    suites:
-      - name: default
-    """
-    When I successfully run `kitchen list`
-    Then the output should match /^default-win-81\s+Dummy\s+Dummy\s+Dummy\s+Winrm\s+\<Not Created\>\s+\<None\>$/
-
-  Scenario: Non-Windows platforms get the Ssh Transport by default
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver: dummy
-    provisioner: dummy
-    verifier: dummy
-
-    platforms:
-      - name: ubuntu-16.04
-
-    suites:
-      - name: default
-    """
-    When I successfully run `kitchen list`
-    Then the output should match /^default-ubuntu-1604\s+Dummy\s+Dummy\s+Dummy\s+Ssh\s+\<Not Created\>\s+\<None\>$/

data/features/kitchen_diagnose_command.feature

@@ -1,96 +0,0 @@
-Feature: Running a diagnosis command
-  In order to understand how Kitchen is wired together
-  As an operator and configuration sleuth
-  I want to run a command to get configuration information
-
-  Background:
-    Given a file named ".kitchen.yml" with:
-    """
-    ---
-    driver:
-      name: dummy
-
-    provisioner:
-      name: dummy
-
-    transport:
-      name: dummy
-
-    verifier:
-      name: dummy
-
-    platforms:
-      - name: cool
-      - name: beans
-
-    suites:
-      - name: client
-      - name: server
-    """
-
-  @spawn
-  Scenario: Displaying help
-    When I run `kitchen help diagnose`
-    Then the output should contain:
-    """
-    Usage:
-      kitchen diagnose
-    """
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Showing all instances
-    When I run `kitchen diagnose`
-    Then the output should contain "timestamp: "
-    Then the output should contain "kitchen_version: "
-    Then the output should contain "  client-cool:"
-    Then the output should contain "  client-beans:"
-    Then the output should contain "  server-cool:"
-    Then the output should contain "  server-beans:"
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Showing all instances with loader configuration
-    When I run `kitchen diagnose --loader`
-    Then the output should contain:
-    """
-    loader:
-      process_erb: true
-      process_local: true
-      process_global: true
-    """
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Showing all instances with plugin configuration
-    When I run `kitchen diagnose --plugins`
-    Then the output should contain "plugins:"
-    Then the output should contain "    class: Kitchen::Driver::Dummy"
-    Then the output should contain "    class: Kitchen::Provisioner::Dummy"
-    Then the output should contain "    class: Kitchen::Transport::Dummy"
-    Then the output should contain "    class: Kitchen::Verifier::Dummy"
-    And the exit status should be 0
-
-  @spawn
-  Scenario: Coping with loading failure
-    Given a file named ".kitchen.local.yml" with:
-    """
-    I'm a little teapot
-    """
-    When I run `kitchen diagnose --all`
-    Then the output should contain:
-    """
-        raw_data:
-          error:
-    """
-    And the output should contain:
-    """
-    instances:
-      error:
-    """
-    And the output should contain:
-    """
-    plugins:
-      error:
-    """
-    And the exit status should be 0