Created
October 13, 2015 12:11
-
-
Save sheldonh/61a9a41195073467471c to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature: Legacy bootstrapping | |
As a legacy service component | |
In order to use the configuration service without changing hosting strategy | |
I want to bootstrap the configuration service from a file. | |
Scenario: Legacy bootstrapping | |
Given no environmental service configuration | |
And a service configuration file | |
When I seed the environment from the file | |
And I bootstrap the configuration service from the environment | |
Then I receive a functioning configuration service | |
And the environmental service configuration has been scrubbed | |
And the seeding file has not been scrubbed | |
Scenario: Missing legacy bootstrapping | |
Given environmental service configuration | |
And a missing service configuration file | |
When I seed the environment from the file | |
And I bootstrap the configuration service from the environment | |
Then the missing service configuration file does not cause a problem | |
And I receive a functioning configuration service | |
And the environmental service configuration has been scrubbed | |
Scenario: Conflicting legacy bootstrapping | |
Given environmental service configuration | |
And a service configuration file | |
When I seed the environment from the file | |
And I bootstrap the configuration service from the environment | |
Then I receive a functioning configuration service | |
And environmental service configuration overrode the service configuration file | |
Scenario: Invalid legacy bootstrapping | |
Given a service configuration file with invalid contents | |
When I seed the environment from the file | |
Then I am immediately interrupted and presented with an error | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment