-
**What happened**:
synopsysctl is using upstream names in the options instead of the downstream names (ie perceiver vs processor). Need to have the option names match the names used in OpsSight.
…
rrati updated
5 years ago
-
**What would you like to be added**:
JIRA Ticket CLOUD-369
```
let's rename this opssight param:
--scannerpod-imagefacade-internal-registries-file-path string Absolute path to a file for s…
-
**What happened**:
Trying to link opssight to blackduck instances is hampered by inability to set hub type when creating opssight
rrati updated
5 years ago
-
**What happened**:
synopsysctl has an option to enable metrics, but has additional flags to control the deployment via prometheus- options. Should rename these options to metrics- to link with enabl…
rrati updated
5 years ago
-
Currently, our instructions for how to install Black Duck manually are basically a big lie:
https://synopsys.atlassian.net/wiki/spaces/BDLM/pages/65863959/Installing+Black+Duck+in+clusters+that+are+n…
-
There are some cases in which a customer may need to install Black Duck into a namespace/project that already exists. Currently, the Synopsys Operator console UI will print a warning, as it does names…
-
**Describe the bug**
Security is set to privileged=true by default for a non-docker (skopeo) environment, which causes the scanner pod to not come up.
**Environment (please complete the following …
-
**Describe the bug**
Exposing a loadbalancer for opssight gets automatically deleted
**Environment:**
- GKE - v1.11.7-gke.12
**To Reproduce**
Steps to reproduce the behavior:
1. `kc expose …
-
**What happened**:
Tried to deploy image processor
**What you expected to happen**:
Successfully deploy image processor
**How to reproduce it (as minimally and precisely as possible)**:
./syn…
rrati updated
5 years ago
-
**What happened**:
Synopsysctl is giving the error "Error loading config file"
**What you expected to happen**:
Alert is successfully deployed
```
time="2019-05-09T11:30:32-04:00" lev…