Add name field to acl rules

[markwellis]

Is your feature request related to a problem? Please describe.
I use terraform to add additional ACL rules by merging with the existing rules. Without a way of naming them there's no way to remove these rules automatically whilst preserving existing rules.

E.g.
If I have this array in terraform of acl rules that I will merge with the existing rules via a distinct(merge(old_rules, new_rules))

[
  {
    "action": "accept",
    "src": [
      "tag:foo"
    ],
    "dst": [
      "*:*"
    ]
  },
  {
    "action": "accept",
    "src": [
      "tag:bar"
    ],
    "dst": [
      "*:*"
    ]
  },
]

Some time later, I want to remove the second rule (src: tag:bar) from the acls, I can't just remove it from that array I have to do it manually in the tailscale admin interface.

If there was a name field I could name the rules with a prefix, e.g. tf-added-rule- and I could delete all the rules with that name prefix from old_rules before doing the merge(old_rules, new_rules)

Describe the solution you'd like
Add a name field to acl rules. This should be unique among the rules.

[cyberbutler]

Commenting to support this feature request. Without a proper name or id attribute we cannot achieve idempotency easily using automation tooling. ACLs should be able to be modified in place without damaging existing rules. Additionally, it is my opinion that each ACL object block which is of type object(list(object)) should be able to have an id or name field added to each child object so that we can programmatically choose which rules to add or destroy including acls, tests, and ssh.