Ales Raszka
a8a91379d9
Add test for potential namespace
...
Test verifies that potential namespace is stored in database and it can
be loaded back to structure.
The commit also fixes few typos and bugs.
2019-03-08 09:51:19 +01:00
Ales Raszka
60ef726677
Move PotentialNamespace to LayerFeature
...
PotentialNamespace should be in LayerFeature instead of Feature struct.
Feature extractors were updated to return LayerFeature instead of
Feature.
2019-03-07 11:22:54 +01:00
Ales Raszka
44c4a6f3ce
Store PotentialNamespace in database
...
PotentialNamespace is part of layer_feature table and it is also stored
in namespace table.
2019-03-07 11:22:32 +01:00
Sida Chen
79af05e67d
pgsql: Fix postgres queries for feature_type
2019-02-19 16:48:42 -05:00
Ales Raszka
015a79fd5a
Layer: replace arrays with slices
...
The current code is much cleaner because it doesn't use indexes + it
should be more memory efficient.
2019-01-16 09:12:34 +01:00
Sida Chen
0c1b80b2ed
pgsql: Implement database queries for detector relationship
...
* Refactor layer and ancestry
* Add tests
* Fix bugs introduced when the queries were moved
2018-10-08 11:27:15 -04:00
Sida Chen
9c49d9dc55
pgsql: Move queries to corresponding files
...
Aggregate queries in their corresponding files instead of having the
single file for every queries because the database is more complicated.
2018-10-08 10:42:40 -04:00
Sida Chen
e160616723
database: Use LayerWithContent as Layer
2018-09-13 13:21:39 -04:00
Sida Chen
5d725e67b0
Replace Ancestry with AncestryWithContent struct in database models
...
As one of the steps to simplifies the codebase, the AncestryWithContent
struct is renamed to Ancestry, and Ancestry is removed. It will cause
the PostAncestry request to be slower.
2018-09-10 12:48:23 -04:00
Sida Chen
2827b9342b
Update Database and Worker implementation for layer-wise feature
...
Feature extraction algorithm is changed to associate features with
ancestry layer. Database is updated to keep the relationship.
2018-09-06 13:56:03 -04:00
Sida Chen
a5c6400065
database: postgres implementation with tests.
2017-08-10 11:25:29 -04:00
Sida Chen
bffa6499b7
added support for detect multiple namespaces in a layer
...
created table layer_namespace to store the many to many unique mapping of layers and namespaces
changed v1 api to provide a list of namespaces for each layer
changed namespace detector to use all registered detectors to detect namespaces
updated tests for multiple namespaces
Fixes #150
2017-05-24 17:01:51 -04:00
Sida Chen
9306e99368
converted to structured logging by using logrus
...
changed from capnslog to logrus for logging JSON structured message.
finished issue #383
2017-05-04 13:59:57 -04:00
Jimmy Zelinskie
3e4dc3834f
utils: remove string.go
2017-01-22 23:02:51 -05:00
Jimmy Zelinskie
78cef02fda
pkg: cerrors -> commonerr
2017-01-22 23:02:50 -05:00
Jimmy Zelinskie
033709eaea
add registerable version formats
...
Since we only ever used dpkg, this change shims everything into using
dpkg.
2016-12-30 12:51:24 -05:00
Quentin Machu
a38fbf6cfe
worker/database: Move upgrade detection logic out of database to worker
2016-05-20 12:01:30 -05:00
Quentin Machu
e7b960c05b
database: Allow specifying datastore driver by config
...
Fixes #145
2016-05-11 15:29:13 -07:00
Jimmy Zelinskie
363cde29f4
psql: add debug message for duplicate layers
2016-03-08 14:39:53 -05:00
Jimmy Zelinskie
500fc4e407
various: gofmt -s
2016-02-24 19:29:36 -05:00
Jimmy Zelinskie
8fd0aa162b
various: spelling corrections
2016-02-24 18:00:36 -05:00
Quentin Machu
84319507df
database: use constants to store queries
2016-02-24 16:40:40 -05:00
Quentin Machu
06531e01c5
database: disable hash/merge joins in FindLayer
...
Our experiments have shown that PostgreSQL 9.4 makes bad
planning decisions about:
- joining the layer tree to feature versions and feature
- joining the feature versions to affected/fixed feature version and vulnerabilities
It would for instance do a merge join between affected feature versions (300 rows, estimated
3000 rows) and fixed in feature version (100k rows). In this case, it is much more
preferred to use a nested loop.
2016-02-24 16:40:40 -05:00
Quentin Machu
6d2eedf121
api/database: add the layer name that add each feature in getLayer
2016-02-24 16:39:25 -05:00
Quentin Machu
f0816d2c4d
database: add docs about the interface
2016-02-24 16:36:45 -05:00
Quentin Machu
d3b14106a9
database: ignore insertLayer collisions to make it truly idempotent
2016-02-24 16:36:45 -05:00
Quentin Machu
5fdd9d1a07
*: add metadata support along with NVD CVSS
2016-02-24 16:36:45 -05:00
Quentin Machu
baed60e19b
prometheus: add initial Prometheus support
2016-02-24 16:34:54 -05:00
Quentin Machu
563b3825d8
database: let handleErrors deal with the not found case
2016-02-24 16:34:54 -05:00
Quentin Machu
726bd3c0c6
database/api: add layer deletion support
2016-02-24 16:34:54 -05:00
Quentin Machu
82175dcfe9
*: add missing copyright headers
2016-02-24 16:34:54 -05:00
Quentin Machu
92b734d0a4
database: remove an useless query in FindLayer
2016-02-24 16:34:54 -05:00
Quentin Machu
7c70fc1c20
database: add initial vulnerability support
2016-02-24 16:32:21 -05:00
Quentin Machu
3a786ae020
database: add lock support
2016-02-24 16:32:21 -05:00
Quentin Machu
6a9cf21fd4
database: log and mask SQL errors
2016-02-24 16:32:21 -05:00
Quentin Machu
970756cd5a
database: do insert/find layers (with their features and vulnerabilities)
2016-02-24 16:32:21 -05:00
Quentin Machu
2c150b015e
*: refactor & do initial work towards PostgreSQL implementation
2016-02-24 16:32:21 -05:00
