konveyor/mig-controller: pkg/controller/discovery/web/plan.go; 12 LoC

Found a possible issue in [konveyor/mig-controller](https://www.github.com/konveyor/mig-controller) at [pkg/controller/discovery/web/plan.go](https://github.com/konveyor/mig-controller/blob/cf705e01f0dac48c3a557d61d98776b54b6c3420/pkg/controller/discovery/web/plan.go#L745-L756)

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/konveyor/mig-controller/blob/cf705e01f0dac48c3a557d61d98776b54b6c3420/pkg/controller/discovery/web/plan.go#L745-L756)

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

```go
for _, container := range podContainers {
excluded := false
for _, filter := range filters {
if !filter(&container) {
excluded = true
break
}
}
if !excluded {
list = append(list, container)
}
}

```

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 {filter 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: cf705e01f0dac48c3a557d61d98776b54b6c3420

Start by reading pkg/controller/discovery/web/plan.go at lines 745-756 and the linked analyzer report for the shown range-loop code. Determine whether the finding is a Bug, Mitigated, or Desirable Behavior, then record that classification with the corresponding reaction; no code change or test is specified.

Written by the indexing model from the issue text.