<div class="highlight highlight-source-shell notranslate position-relative overflow-auto" dir="auto"

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

The fix is available in <a href="https://github.com/apenella/go-ansible/releases/tag/v

Error decoding results stdout_lines about go-ansible HOT 3 CLOSED

mateo08c commented on June 18, 2024

Error decoding results stdout_lines

from go-ansible.

Comments (3)

apenella commented on June 18, 2024 1

Hi @mateo08c!
Thank you for opening that issue. I have analyzed what you shared and the error was produced because the stdout_lines returns a slice of slices, while the struct used to handle that output expects a slice of string

"output.stdout_lines": [
    [
        "Cisco IOS Software, C2960 Software (C2960-LANLITEK9-M), Version 12.2(52)SE, RELEASE SOFTWARE (fc3)",
        "BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(53r)SEY3, RELEASE SOFTWARE (fc1)",
        "Version ID                      : V04",
        "Switch Ports Model              SW Version            SW Image"
    ]
]

That is the struct I referred:

type AnsiblePlaybookJSONResultsPlayTaskHostsItem struct {
	Action           string                 `json:"action"`
	Changed          bool                   `json:"changed"`
	Msg              interface{}            `json:"msg"`
	AnsibleFacts     map[string]interface{} `json:"ansible_facts"`
	Stdout           interface{}            `json:"stdout"`
	StdoutLines      []string               `json:"stdout_lines"`
	Stderr           interface{}            `json:"stderr"`
	StderrLines      []string               `json:"stderr_lines"`
	Cmd              interface{}            `json:"cmd"`
	Failed           bool                   `json:"failed"`
	FailedWhenResult bool                   `json:"failed_when_result"`
	Skipped          bool                   `json:"skipped"`
	SkipReason       string                 `json:"skip_reason"`
	Unreachable      bool                   `json:"unreachable"`
}

I will adapt the struct to be more flexible when handling the generated output.

I keep you updated.

Thanks again.

from go-ansible.

apenella commented on June 18, 2024 1

Hi @mateo08c!
Although I haven't merged this yet, I wanted to give you a heads up about the following commit with the fix: 1b7af13.

from go-ansible.

apenella commented on June 18, 2024

The fix is available in https://github.com/apenella/go-ansible/releases/tag/v2.0.0

from go-ansible.

Recommend Projects