Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix failure to set initially ungettable volume options like client.ssl #98

Merged
merged 1 commit into from
Mar 19, 2017
Merged

Conversation

chewi
Copy link
Contributor

@chewi chewi commented Mar 16, 2017

It's not clear why but attempting to get client.ssl before it is set results in an error and an exit status of 2. This is different to getting a fictional option like foo.bar, which results in a different error and an exit status of 1.

Let's prevent an exit status of 2 from raising an exception and mark the resource as non-existent in this case.

After resetting client.ssl, it returns to its ungettable state so do not perform subsequent resets when the resource is non-existent.

It's not clear why but attempting to get client.ssl before it is set
results in an error and an exit status of 2. This is different to
getting a fictional option like foo.bar, which results in a different
error and an exit status of 1.

Let's prevent an exit status of 2 from raising an exception and mark
the resource as non-existent in this case.

After resetting client.ssl, it returns to its ungettable state so do
not perform subsequent resets when the resource is non-existent.
@shortdudey123 shortdudey123 merged commit 7e07e33 into shortdudey123:master Mar 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants