Sha256: a9b652a4b503c7e5edf66304aca9ed1b40e07c13d58f3814d2ac3f3d93883cd2
Contents?: true
Size: 887 Bytes
Versions: 15
Compression:
Stored size: 887 Bytes
Contents
Feature: dynamic commands for managing service state
As a motherbrain plugin author using the service orchestration pattern
I want to manage the state of my service using a dedicated command
So that I don't have lots of duplicated commands in my plugin
Background:
Given a valid motherbrain configuration
Scenario: listing the command
Given a cookbook "awesomed" at version "1.2.3" with a plugin that can bootstrap
When I run the "awesomed service -e Foo" command
Then the output should contain:
"""
Usage: "mb service [COMPONENT].[SERVICE] [STATE]".
"""
And the exit status should be 1
Scenario: Get a service to start
Given a cookbook "awesomed" at version "1.2.3" with a plugin that can bootstrap
When I create an environment named "test_env"
And I run the "awesomed service app.tomcat start -e test_env" command
Version data entries
15 entries across 15 versions & 1 rubygems