joeduffy 705880cb7f Add the ability to specify analyzers ... This change adds the ability to specify analyzers in two ways: 1) By listing them in the project file, for example: analyzers: - acmecorp/security - acmecorp/gitflow 2) By explicitly listing them on the CLI, as a "one off": $ coco deploy <env> \ --analyzer=acmecorp/security \ --analyzer=acmecorp/gitflow This closes out pulumi/coconut#119.		2017-03-11 10:07:34 -08:00
..
coconut.go	Move coco env deploy to the top-level, coco deploy	2017-03-10 13:17:55 -08:00
deploy.go	Add the ability to specify analyzers	2017-03-11 10:07:34 -08:00
env.go	Add the ability to specify analyzers	2017-03-11 10:07:34 -08:00
env_config.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_destroy.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_init.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_ls.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
env_rm.go	Properly reap child processes	2017-03-07 13:47:42 +00:00
pack.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
pack_eval.go	Add the ability to specify and env config during eval	2017-03-09 15:52:50 +00:00
pack_get.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
pack_info.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
pack_verify.go	Rename the coco nut command to coco pack	2017-03-09 15:43:28 +00:00
version.go	Properly reap child processes	2017-03-07 13:47:42 +00:00