<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-documentation.git/docs/automation, branch test/ai-validation-e2e-v1.1.0</title>
<subtitle>VyOS readthedocs (mirror of https://github.com/vyos/vyos-documentation.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-documentation.git/atom?h=test%2Fai-validation-e2e-v1.1.0</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-documentation.git/atom?h=test%2Fai-validation-e2e-v1.1.0'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/'/>
<updated>2026-10-31T10:53:23+00:00</updated>
<entry>
<title>T3871: bind interface names to hardware slots instead of hw-id (#2246)</title>
<updated>2026-10-31T10:53:23+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-10-31T10:53:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=f939f4eb05f55e7e4c81e1b5dc954c3fc06d2389'/>
<id>urn:sha1:f939f4eb05f55e7e4c81e1b5dc954c3fc06d2389</id>
<content type='text'>
* docs: T3871: describe how interface names are assigned

Names are no longer derived from the hw-id node. They are bound to the slot
the hardware occupies and recorded in a mapping file, so document what
decides a name, what happens when a card is replaced or added, and how to
rename an interface.

The troubleshooting page said to pin a MAC with hw-id when interfaces were
renamed after a VM migration or a clone. That node no longer exists and the
situation it describes no longer arises, so replace it with a pointer to the
new section and a note on where to look when an interface really is missing.

* docs: T3871: drop hw-id from the example output

The node is gone from the CLI, so example configuration dumps which still
show it no longer match what a reader sees on their own system. Remove it
from the shown output only; no prose changes. The comparison shown on the
testing page is rewritten rather than trimmed, as deleting the lines would
have left an edit level behind with nothing under it.</content>
</entry>
<entry>
<title>T9354: document "reconnect interface" operational command</title>
<updated>2026-09-25T19:15:00+00:00</updated>
<author>
<name>Christian Breunig</name>
<email>christian@breunig.cc</email>
</author>
<published>2026-09-25T19:15:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=8de66862a56a5ed8557c4d0e0ac45e8659284ec5'/>
<id>urn:sha1:8de66862a56a5ed8557c4d0e0ac45e8659284ec5</id>
<content type='text'>
PPPoE, SSTP client and WWAN interfaces can now be restarted with a single
command which survives the loss of the CLI session, so it can be issued over
the very interface being reconnected. The WWAN page gained the connect and
disconnect commands as well - they have always been available there, but were
only documented for PPPoE and SSTP.

The command is also exposed by the HTTP API through a dedicated endpoint,
which replaces the "reset connection" path that was previously used for this.
</content>
</entry>
<entry>
<title>vyos-api: clarify comment regarding commit failure and partial commits (#2178)</title>
<updated>2026-08-03T13:21:55+00:00</updated>
<author>
<name>John Estabrook</name>
<email>jestabro@vyos.io</email>
</author>
<published>2026-08-03T13:21:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=4631db6a1578550dd4c1410a8416575899f36936'/>
<id>urn:sha1:4631db6a1578550dd4c1410a8416575899f36936</id>
<content type='text'>
</content>
</entry>
<entry>
<title>vyos-api: T9087: T9092: apply review feedback (line length, retry safety)</title>
<updated>2026-07-14T21:08:40+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T21:08:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=2510eefadc8e7520e7f85f45a2b29fdab634474a'/>
<id>urn:sha1:2510eefadc8e7520e7f85f45a2b29fdab634474a</id>
<content type='text'>
Convert the multi-field-node table to wrapped list items per the 80-char
docs guideline, and rework the bulk-apply bullet to reconcile state
before retrying after a timeout instead of recommending blind retries.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>vyos-api: T9087: tighten firewall same-request wording (review feedback)</title>
<updated>2026-07-14T21:00:18+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T21:00:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=9e90088827c53f8d61e82e2e29910a9346009e87'/>
<id>urn:sha1:9e90088827c53f8d61e82e2e29910a9346009e87</id>
<content type='text'>
Only port/port-group require protocol in the same request; description
alone is fine on an existing rule but fails on a rule no request has
created yet.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>vyos-api: T9092: add bulk configuration guidance</title>
<updated>2026-07-14T20:50:41+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T20:50:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=af04731c74b0383bc36c66addd6cc22ba41c55e0'/>
<id>urn:sha1:af04731c74b0383bc36c66addd6cc22ba41c55e0</id>
<content type='text'>
Batch sizing, geoip/remote-group commit cost, the 1 MB
request-body-size-limit, and commit-confirm as a remote safety net.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>vyos-api: T9090: T9091: batched /configure semantics; save via /config-file</title>
<updated>2026-07-14T20:50:15+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T20:50:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=f002549a5fe3ae782be8fe02160fa2796e7e0471'/>
<id>urn:sha1:f002549a5fe3ae782be8fe02160fa2796e7e0471</id>
<content type='text'>
Document that an operation list commits as one transaction whose error
may not identify the failing op (bisect / one-op fallback), and that
/configure rejects {"op": "save"} — persistence goes through
/config-file.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>vyos-api: T9089: document /retrieve showConfig on empty paths</title>
<updated>2026-07-14T20:49:48+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T20:49:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=3a952350bf5b5b38a7db1208ed3c910ded7b4b24'/>
<id>urn:sha1:3a952350bf5b5b38a7db1208ed3c910ded7b4b24</id>
<content type='text'>
showConfig returns HTTP 400 'Configuration under specified path is
empty' for schema-valid but unconfigured paths; recommend probing with
exists or treating that error as an empty subtree.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>vyos-api: T9088: document /show configuration commands export</title>
<updated>2026-07-14T20:49:22+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T20:49:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=ca902d4eebd49697f476d538eadfcaeb8ebb2232'/>
<id>urn:sha1:ca902d4eebd49697f476d538eadfcaeb8ebb2232</id>
<content type='text'>
The /show endpoint can return the running config as flat set commands
(op-mode 'show configuration commands' equivalent) — the natural way to
mirror or back up a router over the API; previously undocumented.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>vyos-api: T9087: document commit atomicity for multi-field nodes</title>
<updated>2026-07-14T20:48:59+00:00</updated>
<author>
<name>Brad Kollmyer</name>
<email>bradk@vitalsoft.com</email>
</author>
<published>2026-07-14T20:48:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-documentation.git/commit/?id=0b88b491d043e5f281d8e3ae499c4d045da28f28'/>
<id>urn:sha1:0b88b491d043e5f281d8e3ae499c4d045da28f28</id>
<content type='text'>
Each /configure request is validated and committed on its own, so fields
of one node (task-scheduler executable+interval, NAT translation,
firewall action/protocol before port) must be sent in a single request.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
</feed>
