-
# Motivation
```
As a Developer using the Lacework Platform,
I want to be able to integrate the vulnerability scan/reports into my pipeline,
so I can detect early on of potential threads that coul…
ghost updated
4 years ago
-
We have introduced new AWS Terraform Modules that need to be
documented into the `README.md` inside the `aws/` directory.
**JIRA: ALLY-134**
-
We should create a `README.md` within the `gcp` folder to walk users through the usage
-
```
» lacework events show 34133 -p customerdemo --debug …
-
Let us make sure the AWS README file is updated and ready for opensource it
ghost updated
4 years ago
-
One of the column headers in the events output is misspelled. It says "PINCIPAL" but should say "PRINCIPAL"
https://github.com/lacework/go-sdk/blob/621635884fb9fb34210e7d66964c1aca65b8e537/cli/cmd/…
-
The `cpu_percentage` field inside the `entity_map` looks like a `float32`
instead of an `int32`, the error shown on some events is:
```
ERROR unable to get event details: json: cannot unmarshal num…
ghost updated
4 years ago
-
some users have job visibility that others do not - same github permissions
users with issues show a 404 - and when listing the jobs - some users have different lists showing up
https://app.ship…
-
# Motivation
```
As a Lacework CLI User with multiple Lacework Accounts,
I would like to be able to configure my Lacework CLI with multiple profiles,
So I can switch easily between accounts withou…
ghost updated
4 years ago
-
Revisit the vulnerability command functionality and documentation to have
consistency with the use of Image ID and Image Digest.
**Jira: ALLY-83**
ghost updated
4 years ago