TejaBeta/kopy: internal/kopy.go; 8 LoC

Found a possible issue in [TejaBeta/kopy](https://www.github.com/TejaBeta/kopy) at [internal/kopy.go](https://github.com/TejaBeta/kopy/blob/a4a51ee6b9e6721ddb5b29230f874da29be60b79/internal/kopy.go#L209-L216)

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/TejaBeta/kopy/blob/a4a51ee6b9e6721ddb5b29230f874da29be60b79/internal/kopy.go#L209-L216)

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

```go
for _, v := range *kResource.Ingresses {
koperator.ManipulateResource(&v)
_, err := kOpts.CreateIngress(&v)
if err != nil {
return err
}
log.Infof("Copied resource %v of type Ingress", v.GetName())
}

```

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 {ManipulateResource 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: a4a51ee6b9e6721ddb5b29230f874da29be60b79

Start with internal/kopy.go at lines 209-216 and review the analyzer output about the range-loop variable and pointer arguments. Classify the finding by leaving the requested Bug, Mitigated, or Desirable Behavior reaction; completion is the selected classification.

Written by the indexing model from the issue text.