vmware/priam: core/users.go; 3 LoC

Found a possible issue in [vmware/priam](https://www.github.com/vmware/priam) at [core/users.go](https://github.com/vmware/priam/blob/75f6376a6bb25ccdae7a28653203d44e8c77f6ac/core/users.go#L82-L84)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

>

[Click here to see the code in its original context.](https://github.com/vmware/priam/blob/75f6376a6bb25ccdae7a28653203d44e8c77f6ac/core/users.go#L82-L84)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, v := range newUsers {
userService.AddEntity(ctx, &v)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {AddEntity 2} was not found in the callgraph; reference was passed directly to third-party code
```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 75f6376a6bb25ccdae7a28653203d44e8c77f6ac

Start with core/users.go lines 82-84 at commit 75f6376a6bb25ccdae7a28653203d44e8c77f6ac and read the linked original context. Examine how the range-loop variable is passed to AddEntity, then use the analyzer details and project guidance to choose Bug, Mitigated, or Desirable Behavior. Done means leaving the corresponding reaction.

Written by the indexing model from the issue text.