DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > A Read-Eval-Print Loop for Ansible

A Read-Eval-Print Loop for Ansible

Did you know that Ansible has a REPL tool available that can help you out with your Ansible coding? It helps you quickly check out the syntax of an API or test an idea.

James Carr user avatar by
James Carr
·
Feb. 24, 17 · DevOps Zone · Opinion
Like (1)
Save
Tweet
4.71K Views

Join the DZone community and get the full member experience.

Join For Free

One must-have tool for any language is the availability of a REPL to quickly check out the syntax of an API or test out an idea really quickly. Ansible is no different, especially since sometimes, you might have a very long running playbook and it may be difficult to wait for it to run before discovering you had the syntax for something off at the end.

Ansible's Lesser-Known Read-Eval-Print Loop Tool

Luckily, Ansible comes with the lesser known ansible-console command. You can use this to execute any one of the modules included in ansible to roughly test something out and can run it against a local or remote host.

vagrant @monitor: ~$ ansible - console localhost[WARNING]: Host file not found: /etc/ansible / hosts

 [WARNING]: provided hosts list is empty, only localhost is available

Welcome to the ansible console.
Type help or ? to list commands.

vagrant @localhost(1)[f: 5] $ setup

# very long json of facts omitted

vagrant @localhost(1)[f: 5] $ debug msg = ”distribution version reversed
is {
 {
  ansible_distribution_version | reverse
 }
}”
localhost | SUCCESS => {“
 msg”: “distribution version reversed is 40.41”
}

You can run ad-hoc commands on the machine through it, as well.

vagrant@localhost (1)[f:5]$ ls /tmplocalhost | SUCCESS | rc=0 >>ansible_busvWCvagrant-ansiblevagrant-shell

This also doubles as an easy and cheap REPL for Jinja2, as well, if you need to test some Jinja2 syntax out.

Ansible (software)

Published at DZone with permission of James Carr, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Remote Debugging and Developer Observability
  • How to Build Microservices With Node.js
  • Major PostgreSQL Features You Should Know About
  • What's the Difference Between Static Class vs. Singleton Patterns in C#?

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo