This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Don't die simply because config var is missing from provisioning response #66
Conversation
This file contains 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
…d, use only a minor warning
bjeanes
added a commit
that referenced
this pull request
Jan 14, 2014
Don't die simply because config var is missing from provisioning response
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR for issue #62
Instead of throwing an error when a config var is missing from the initial provisioning response (because reasons in #62), just print a nice yellow warning with the missing config var's name.
Deleted the related test.
Happy to discuss in depth if we feel the need.