deleteConnectionPooler function incorrectly checks that the delete api response is ResourceNotFound. Looks like the only consequence is a confusing log message, but obviously it's wrong. Remove negation, since having ResourceNotFound as error is the good case. Co-authored-by: Christian Rohmann <christian.rohmann@inovex.de> |
||
|---|---|---|
| .. | ||
| apis/acid.zalan.do | ||
| apiserver | ||
| cluster | ||
| controller | ||
| generated | ||
| spec | ||
| util | ||