Skip to content

Conversation

@stacywsmith
Copy link
Contributor

Fix a regression caused by #109.

The new check argument added to junos_commit by #109 was not correctly specified. Therefore, the following error was produced when the task ommitted the check argument (default behavior).

fatal: [r0]: FAILED! => {"changed": false, "failed": true, "msg": "value of check must be one of: yes,on,1,true,1,True,no,off,0,false,0,False, got: False"}

This change correctly specifies the argument's type as bool.

The new check argument added to junos_commit by #109 was not correctly
specified. Therefore, the following error was produced when the
task ommitted the check argument (default behavior).
```
fatal: [r0]: FAILED! => {"changed": false, "failed": true, "msg": "value of check must be one of: yes,on,1,true,1,True,no,off,0,false,0,False, got: False"}
```
This change correctly specifies the argument's type as bool.
@stacywsmith stacywsmith merged commit 1b442c3 into Juniper:master Sep 21, 2017
@stacywsmith stacywsmith deleted the fix_junos_commit_check_arg branch September 21, 2017 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant