# Implementing 'Undo' Functionality in Network Automation

DevFeed: [Implementing 'Undo' Functionality in Network Automation](<https://devfeed.tech/articles/implementing-undo-functionality-in-network-automation-10951.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2024/02/undo-network-automation/>)

Published: 2024-02-21T07:06:00Z

Content type: opinion

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Git](<https://devfeed.tech/topics/git.md>), [YAML](<https://devfeed.tech/topics/yaml.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [git](<https://devfeed.tech/tags/git.md>), [network](<https://devfeed.tech/tags/network.md>), [transactions](<https://devfeed.tech/tags/transactions.md>), [yaml](<https://devfeed.tech/tags/yaml.md>)

## AI overview

The article examines how to undo network automation changes when a technically valid network change breaks a customer application. It argues that YAML files under Git make rollback straightforward with git revert, while structured data stores require application-level change logs, validation, and undo operations treated as new transactions.

## Source excerpt

Kurt Wauters sent me an interesting challenge: how do we do rollbacks based on customer requests? Here's a typical scenario: You might have deployed a change that works perfectly fine from a network perspective but broke a customer application (for example, due to undocumented usage), so you must be able to return to the previous state even if everything works. Everybody says you need to "roll forward" (improve your change so it works), but you don't always have that luxury and might need to take a step back. So, change tracking is essential. He's right: the undo functionality we take for granted in consumer software (for example, Microsoft Word) has totally spoiled us. Read more ...