gardener-attic/gardener-extensions: pkg/controller/backupbucket/mapper.go; 10 LoC

Found a possible issue in [gardener-attic/gardener-extensions](https://www.github.com/gardener-attic/gardener-extensions) at [pkg/controller/backupbucket/mapper.go](https://github.com/gardener-attic/gardener-extensions/blob/340b17eb25cbde91f5e71d4ac1634e4213afa6f2/pkg/controller/backupbucket/mapper.go#L67-L76)

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/gardener-attic/gardener-extensions/blob/340b17eb25cbde91f5e71d4ac1634e4213afa6f2/pkg/controller/backupbucket/mapper.go#L67-L76)

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

```go
for _, backupBucket := range backupBucketList.Items {
if !extensionspredicate.EvalGeneric(&backupBucket, m.predicates...) {
continue
}
requests = append(requests, reconcile.Request{
NamespacedName: types.NamespacedName{
Name: backupBucket.Name,
},
})
}

```

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 {EvalGeneric 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: 340b17eb25cbde91f5e71d4ac1634e4213afa6f2

Open pkg/controller/backupbucket/mapper.go at lines 67-76 and inspect the range-loop variable passed to EvalGeneric. Compare the analyzer's finding with the linked code context, then classify it by leaving the requested Bug, Mitigated, or Desirable Behavior reaction; completion is the reaction.

Written by the indexing model from the issue text.