Optional Attribute Protection

[chadell]

Environment

• Nautobot version:
• nautobot-design-builder version:

Proposed Functionality

Allow to customize protection at attribute level to allow different use cases. By default, it will default to protected. The information would be then populated into the JournalEntry to provide understanding of the attributes that are NOT protected.

Use Case

For example, when a design creates a Device with Status Planned, we would like to update the Status later to Active. By default, if data protection is enforce, that won't be possible (if not bypassed as superuser). To allow more rich workflows, some attributes of the objects created by a design should be "unprotected" to allow changes.