x/osel
Code Issues Proposed changes
afe7bbf0ac
osel/fixtures
History
Nate Johnston ca0e1ca769 Initial import of osel code 
This is an initial import of the osel codebase.  The osel tool is a tool that
initiates external security scans (initially through Qualys) upon reciept of
AMQP events that indicate certain sensitive events have occurred, like a
security group rule change.

The commit history had to be thrown away because it contained some non-public
data, so I would like to call out the following contributors:

This uses go 1.10 and vgo for dependency management.

Co-Authored-By: Charles Bitter <Charles_Bitter@cable.comcast.com>
Co-Authored-By: Olivier Gagnon <Olivier_Gagnon@cable.comcast.com>
Co-Authored-By: Joseph Sleiman <Joseph_Sleiman@comcast.com>

Change-Id: Ib6abe2024fd91978b783ceee4cff8bb4678d7b15
2018-03-24 15:30:57 +00:00
..
event_processor/icehouse Initial import of osel code 2018-03-24 15:30:57 +00:00
viper Initial import of osel code 2018-03-24 15:30:57 +00:00
README.md Initial import of osel code 2018-03-24 15:30:57 +00:00

README.md

Test Fixtures

The fixtures folder is meant to hold test files that can be used to create positive and negative tests.

The test files should be organized in a folder per _test.go file. The folder should be named after the test. For example foo_test.go should use a folder called foo. Sub folders are fine. Just don't go nuts and KISS