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

bug fix for AttributeError: 'str' object has no attribute 'get' #17422

Merged
merged 1 commit into from Sep 6, 2016
Merged

bug fix for AttributeError: 'str' object has no attribute 'get' #17422

merged 1 commit into from Sep 6, 2016

Conversation

privateip
Copy link
Contributor

Exception thrown when using cli transport in eos but piping the command
through json

  • eos now checks for | json and automatically changes the output type
  • adds back import of Command object

tested on EOS 4.15.4F

Exception thrown when using cli transport in eos but piping the command
through json

* eos now checks for `| json` and automatically changes the output type
* adds back import of Command object

tested on EOS 4.15.4F
@privateip privateip merged commit 5730c97 into ansible:devel Sep 6, 2016
@privateip privateip deleted the fix-17407 branch September 6, 2016 23:23
@jimi-c jimi-c removed the in progress label Sep 6, 2016
sereinity pushed a commit to sereinity-forks/ansible that referenced this pull request Jan 25, 2017
There is an issue when piping cli commands through json but the output
is specified as either text or the output is none and the transport is
cli.  The results would not be loaded properly for conditional
evaluation.  This is similar to ansible#17422
@ansible ansible locked and limited conversation to collaborators Apr 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants