Go-ansible is a package for running Ansible playbooks from Golang applications.
It supports ansible-playbook
command with the most of its options.
To run an ansible-playbook
command you could define four objects, depending on your needs:
- AnsiblePlaybookCmd object is the main object which defines the
ansible-playbook
command and how to execute it.AnsiblePlaybookCmd
definition is mandatory to run anyansible-playbook
command.AnsiblePlaybookCmd
has a parameter that defines theExecutor
to use, the worker who launches the execution. If noExecutor
is specified, is usedDefaultExecutor
.AnsiblePlaybookCmd
also has an attribute to define the stdout callback method to use. Depending on that method,go-ansible
manages the results in a specific way. Actually all stdout callback method's results are treated such the default method instead ofjson
stdout callback, which parses the json an summerizes the stats per host. If no stdout callback method is specified, is useddefault
stdout callback one. - AnsiblePlaybookOptions object has those parameters described on
Options
section within ansible-playbook's man page, and defines how should be theansible-playbook
execution behavior and where to find execution configuration. - AnsiblePlaybookConnectionOptions object has those parameters described on
Connections Options
section within ansible-playbook's man page, and defines how to connect to hosts. - PrivilegeEscalationOptions object has those parameters described on
Escalation Options
section within ansible-playbook's man page, and defines how to become a user.
Go-ansible package has its own and default executor implementation which runs the ansible-playbook
command and prints its output with a prefix on each line.
Whenever is required, you could write your own executor implementation and set it on AnsiblePlaybookCmd
object, it will expect that the executor implements Executor
interface.
type Executor interface {
Execute(command string, args []string, prefix string) error
}
Its possible to define your own executor and set it on AnsiblePlaybookCmd
.
type MyExecutor struct {}
func (e *MyExecutor) Execute(command string, args []string, prefix string) error {
fmt.Println("I am doing nothing")
return nil
}
playbook := &ansibler.AnsiblePlaybookCmd{
Playbook: "site.yml",
ConnectionOptions: ansiblePlaybookConnectionOptions,
Options: ansiblePlaybookOptions,
Exec: &MyExecutor{},
}
When you run the playbook using your dummy executor, the output received is the next one.
$ go run myexecutor-ansibleplaybook.go
I am doing nothing
It is possible to define and specific stdout callback method on go-ansible
. To do that is needed to set StdoutCallback
attribute on AnsiblePlaybookCmd
object. Depending on the used method, the results are managed by one function or another one. The functions to manage ansible-playbook
's output are defined on the package github.com/apenella/go-ansible/stdoutcallback/results
and must be defined following the next signature:
// StdoutCallbackResultsFunc defines a function which manages ansible's stdout callbacks. The function expects and string for prefixing output lines, a reader that receives the data to be wrote and a writer that defines where to write the data comming from reader
type StdoutCallbackResultsFunc func(string, io.Reader, io.Writer) error
Below are defined the ways which could manage ansible playbooks:
Default
By default any stdout callback results will be managed by this results way and it prints the ansible-playbook
's output as it is.
JSON
The json schema expected from ansible-playbook
is the defined on https://github.com/ansible/ansible/blob/v2.9.11/lib/ansible/plugins/callback/json.py.
When the stdout callback method is defined as json
, and specific results method is used. The json method summarizes the ansible-playbooks
's following the pattern below.
[<host>] (<task name>) <task message>
[<host>] (<task name>) <task message>
...
[<host>] (<task name>) <task message>
Host: <host>
<host stats>
For example:
[127.0.0.1] (Gathering Facts)
[127.0.0.1] (simple-ansibleplaybook) Your are running 'simple-ansibleplaybook' example
Host: 127.0.0.1
Changed: 0 Failures: 0 Ignored: 0 Ok: 2 Rescued: 0 Skipped: 0 Unreachable: 0
When there is any host stat is on failure
or unrecheable
stdout callback results method return an error to the Executor
.
When is needed to run an ansible-playbook
from your Golang application using go-ansible
package, you must define a AnsiblePlaybookCmd
,AnsiblePlaybookOptions
, AnsiblePlaybookConnectionOptions
as its shown below.
AnsiblePlaybookConnectionOptions
where is defined how to connect to hosts.
ansiblePlaybookConnectionOptions := &ansibler.AnsiblePlaybookConnectionOptions{
Connection: "local",
}
AnsiblePlaybookOptions
where is defined which should be the ansible-playbook
execution behavior and where to find execution configuration.
ansiblePlaybookOptions := &ansibler.AnsiblePlaybookOptions{
Inventory: "127.0.0.1,",
}
AnsiblePlaybookPrivilegeEscalationOptions
where is defined wether to become another and how to do it.
privilegeEscalationOptions := &AnsiblePlaybookPrivilegeEscalationOptions{
Become: true,
BecomeMethod: "sudo",
}
AnsiblePlaybookCmd
where is defined the command execution.
playbook := &ansibler.AnsiblePlaybookCmd{
Playbook: "site.yml",
ConnectionOptions: ansiblePlaybookConnectionOptions,
Options: ansiblePlaybookOptions,
PrivilegeEscalationOptions: privilegeEscalationOptions,
ExecPrefix: "Go-ansible example",
}
Once the AnsiblePlaybookCmd
is already defined it could be run it using the Run
method.
err := playbook.Run()
if err != nil {
panic(err)
}
The result of the ansible-playbook
execution is shown below.
Go-ansible example =>
Go-ansible example => PLAY [all] *********************************************************************
Go-ansible example =>
Go-ansible example => TASK [Gathering Facts] *********************************************************
Go-ansible example => ok: [127.0.0.1]
Go-ansible example =>
Go-ansible example => TASK [simple-ansibleplaybook] **************************************************
Go-ansible example => ok: [127.0.0.1] =>
Go-ansible example => msg: Your are running 'simple-ansibleplaybook' example
Go-ansible example =>
Go-ansible example => PLAY RECAP *********************************************************************
Go-ansible example => 127.0.0.1 : ok=2 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Go-ansible example =>
Go-ansible example => Playbook run took 0 days, 0 hours, 0 minutes, 1 seconds
Duration: 1.816272213s
go-ansible is available under MIT license.