Resolver Descriptions and Examples

TODO: add YAML examples for each resolver

WarningShot::CoreLibResolver

Detects ruby core libraries. This is currently irresolvable, but useful in some situations where a core library is missing. (Found this to be true with some apt installations).

WarningShot::DirectoryResolver

Detects or creates directories using mkdir -p.

WarningShot::FileResolver

Detects files or resolves from a URI. Current supported protocols are: http, file, https. Support for scp and ftp are in the works.

WarningShot::GemResolver

Detects ruby gems or resolves via installation using the RubyGems API. Alternate gem paths can be given for installation. Great for ‘burning’ or ‘freezing’ in gems.

WarningShot::IntegrityResolver

This piggy backs on the file branch. It is irresolvable, but will process md5 or sha1 digests on files and determine if the file has been modified.

WarningShot::ManualResolver

This is a glorified TODO list. Anything that should be manually done to a machine should be listed here. This will be output after all resolvers have been run. It should also be noted that if something has to be put in the ManualResolver a feature request should be put in to create a resolver that can address the missing need.

WarningShot::PermissionResolver

This resolver is currently in the works. It will piggy back on symlink, directory, and file resolvers to correct permissions on the given resource.

WarningShot::SymlinkResolver

Detects and creates symlinks

WarningShot::UrlResolver

Verifies that a URL is reachable. This is irresolvable, but good for know if other web services you depend on are online. It also extends the command line to offer support for host name verification, http code settings, and some other stuff as well. See WarningShot’s help menu for more info.