45064d6299
This change introduces the basic requirements for analyzers, as per pulumi/coconut#119. In particular, an analyzer can implement either, or both, of the RPC methods, Analyze and AnalyzeResource. The former is meant to check an overall deployment (e.g., to ensure it has been signed off on) and the latter is to check individual resources (e.g., to ensure properties of them are correct, such as checking style, security, etc. rules). These run simultaneous to overall checking. Analyzers are loaded as plugins just like providers are. The difference is mainly in their naming ("analyzer-" prefix, rather than "resource-"), and the RPC methods that they support. This isn't 100% functional since we need a way to specify at the CLI that a particular analyzer should be run, in addition to a way of recording which analyzers certain projects should use in their manifests. |
||
---|---|---|
.. | ||
coconut.go | ||
deploy.go | ||
env.go | ||
env_config.go | ||
env_destroy.go | ||
env_init.go | ||
env_ls.go | ||
env_rm.go | ||
pack.go | ||
pack_eval.go | ||
pack_get.go | ||
pack_info.go | ||
pack_verify.go | ||
version.go |