Evgeniy Belyi
Evgeniy Belyi
## Short description While working with OPA we (@eyalkraft, @uri-weisman) encountered some weird behavior regarding having both a policy and a data file in the same package. In the bundle,...
### Environment info - NooBaa Version: **VERSION** - Platform: **Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify** ### Actual behavior 1. Currently the MD5 etag is not...
### Environment info - Version: **output of `git rev-parse HEAD`** | **package.json** | **UI** - Deployment: **N/A** | **Dev** | **VBox** | **ESX** | **GCloud** | **AWS** - Customer: **N/A**...
### Environment info - NooBaa Version: **VERSION** - Platform: **Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify** ### Actual behavior 1. Currently, we attempt to create the...
### Environment info - NooBaa Version: **5.4.0-93d9738** - Platform: **OpenShift 4.4** ### Actual behavior Mappers crash with exceptions and flood the logs with lots of chunks data. This is due...
### Environment info - Version: **VERSION** - Deployment: **AZURE|ESX|AWS|GCLOUD|DEV|VBOX** - Customer: **NAME** ### Actual behavior #3570 Take a look at Guy's review comment regarding the refactor of namespace implementation in...
### Environment info - NooBaa Operator Version: **VERSION** - Platform: **Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify** ### Actual behavior 1. Left gaps to remove after...
I can see sensitive data printed in the logs. Example: time="2020-02-12T17:49:09Z" level=warning msg="using existing pool but connection mismatch &{Name:my-backingstore EndpointType:S3_COMPATIBLE Endpoint:http://jenia:80 Identity:*KEY* Secret:*KEY* AuthMethod:AWS_V4} pool &{Name:my-backingstore ResourceType:CLOUD Mode:INITIALIZING Region: PoolNodeType:BLOCK_STORE_S3...
**Describe the bug** There is a requirement from Azure to enroll into the `Microsoft.Security` in order to pull the data that we need for `2.1.*` rules evaluation. This affects pulling...
**Motivation** Resources without certain tags are being purged on Elastic Azure Cloud accounts. We need to follow the tagging policy to make sure that our deployed resources will not be...