Allow to tag all objects #102

Closed
opened 2026-04-05 16:21:41 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @ypid-work on 3/23/2026

NetBox version

v4.5.5

Feature type

Data model extension

Proposed functionality

Allow objects that can be created via API should support tags.

Use case

When Terraform is being used to manage (Create/Update/Delete) objects in NetBox, it is very useful to see which objects are managed by Terraform. I already tag most objects but ran into this limitation when I created users and groups with Terraform.

Alternatives:

  • Include text "Terraform managed" in description of object.
  • Add a prefix to the object name like tf-.

The disadvantage of both is that it is not machine readable so it could not be used for permissions, for example. Also, at least the prefix is not self-documenting.

Dangerous alternatives:

  • Create a fake "Terraform managed" NetBox Group. This is dangerous because if the User that Terraform uses is itself managed by Terraform, then Terraform is also in the Group "Terraform managed". All Permissions managed by Terraform are assigned to the "Terraform managed" Group thus unexpectedly extending permissions of the User.

Database changes

Yes. I noticed that at least Customization and Admin (Authentication and Ownership) object types are missing tags.

External dependencies

No.

*Originally created by @ypid-work on 3/23/2026* ### NetBox version v4.5.5 ### Feature type Data model extension ### Proposed functionality Allow objects that can be created via API should support tags. ### Use case When Terraform is being used to manage (Create/Update/Delete) objects in NetBox, it is very useful to see which objects are managed by Terraform. I already tag most objects but ran into this limitation when I created users and groups with Terraform. Alternatives: * Include text "Terraform managed" in description of object. * Add a prefix to the object name like `tf-`. The disadvantage of both is that it is not machine readable so it could not be used for permissions, for example. Also, at least the prefix is not self-documenting. Dangerous alternatives: * Create a fake "Terraform managed" NetBox Group. This is dangerous because if the User that Terraform uses is itself managed by Terraform, then Terraform is also in the Group "Terraform managed". All Permissions managed by Terraform are assigned to the "Terraform managed" Group thus unexpectedly extending permissions of the User. ### Database changes Yes. I noticed that at least Customization and Admin (Authentication and Ownership) object types are missing tags. ### External dependencies No.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/netbox#102