<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tools on Itara</title><link>https://itara.dev/docs/reference/tools/</link><description>Recent content in Tools on Itara</description><generator>Hugo</generator><language>en</language><atom:link href="https://itara.dev/docs/reference/tools/index.xml" rel="self" type="application/rss+xml"/><item><title>itara-cli</title><link>https://itara.dev/docs/reference/tools/itara-cli/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://itara.dev/docs/reference/tools/itara-cli/</guid><description>&lt;p&gt;&lt;code&gt;itara&lt;/code&gt; is the command-line tool for working with an Itara
&lt;a href="https://itara.dev/docs/reference/wiring-configuration/"&gt;wiring configuration&lt;/a&gt; — inspecting
a topology at a glance, and validating it for logical mistakes before it&amp;rsquo;s
deployed. It&amp;rsquo;s implemented once, in Rust, and operates purely on the file
formats — the wiring config YAML and &lt;code&gt;.itara&lt;/code&gt; metadata TOML files — so it
works identically regardless of which language (Java or Rust) actually
produced the artifacts being wired together; there&amp;rsquo;s simply nothing
language-specific for it to know about.&lt;/p&gt;</description></item></channel></rss>