ngohoa211/kapacitor: services/azure/service.go; 3 LoC

Found a possible issue in [ngohoa211/kapacitor](https://www.github.com/ngohoa211/kapacitor) at [services/azure/service.go](https://github.com/ngohoa211/kapacitor/blob/298395c4f4733c14d0c53a7c7206e4207de10aa9/services/azure/service.go#L68-L70)

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/ngohoa211/kapacitor/blob/298395c4f4733c14d0c53a7c7206e4207de10aa9/services/azure/service.go#L68-L70)

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

```go
for _, d := range s.Configs {
s.registry.RemoveDiscoverer(&d)
}

```

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 {RemoveDiscoverer 1} 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: 298395c4f4733c14d0c53a7c7206e4207de10aa9

Read services/azure/service.go around lines 68-70 and inspect how RemoveDiscoverer handles the range-loop value. Check the linked commit context and repository guidance for classifying analyzer findings; done means leaving the appropriate Bug, Mitigated, or Desirable Behavior reaction.

Written by the indexing model from the issue text.