Decommissioning of config_context reverts to the initial state without honouring non-tracked keys

[chadell]

Environment

• Python version:
• Nautobot version: 1.6.22
• nautobot-design-builder version: 1.3.0

Expected Behavior

When a local_config_context is modified by a design deployment, only the keys defined by the deployment should be reverted when the design deployment decommissioned

For example:

• initial state: null
• changed by design: { "mpls_enabled": true }
• manually updated: { "mpls_enabled": true, "something": "else" }
• expected result: { "something": "else" }

Observed Behavior

However, this was the result:

• actual result when decommissioning: null

Steps to Reproduce

[abates]

@chadell can you confirm if this behavior exists in Design Builder 2.1? We included tests and refactored the code for this behavior. If the problem does not exist in 2.1 I will back-port the changes to 1.4.

[chadell]

Hi @abates ,

I have tested with the current develop branch, and I still see the behavior.

Steps to reproduce:

• Deploy the "P2P Connection" design. It updates the local config context of the 2 devices involved.
• Update manually the local config context of one of the devices with a new key/value.
• Decommission the design deployment
• The Local Config Context is reset to {}