2013-05-10 19:59:28 -04:00
|
|
|
package packer
|
|
|
|
|
|
|
|
// Implementers of Builder are responsible for actually building images
|
|
|
|
// on some platform given some configuration.
|
2013-06-14 15:32:14 -04:00
|
|
|
//
|
|
|
|
// In addition to the documentation on Prepare above: Prepare is sometimes
|
|
|
|
// configured with a `map[string]interface{}` that has a key "packer_debug".
|
|
|
|
// This is a boolean value. If it is set to true, then the builder should
|
|
|
|
// enable a debug mode which allows builder developers and advanced users
|
|
|
|
// to introspect what is going on during a build. During debug builds,
|
|
|
|
// parallelism is strictly disabled, so it is safe to request input from
|
|
|
|
// stdin and so on.
|
2013-05-10 19:59:28 -04:00
|
|
|
type Builder interface {
|
2013-06-14 15:27:50 -04:00
|
|
|
// Prepare is responsible for configuring the builder and validating
|
|
|
|
// that configuration. Any setup should be done in this method. Note that
|
|
|
|
// NO side effects should take place in prepare, it is meant as a state
|
|
|
|
// setup only. Calling Prepare is not necessarilly followed by a Run.
|
|
|
|
//
|
|
|
|
// The parameters to Prepare are a set of interface{} values of the
|
|
|
|
// configuration. These are almost always `map[string]interface{}`
|
|
|
|
// parsed from a template, but no guarantee is made.
|
|
|
|
//
|
|
|
|
// Each of the configuration values should merge into the final
|
|
|
|
// configuration.
|
|
|
|
Prepare(...interface{}) error
|
2013-06-03 17:44:34 -04:00
|
|
|
|
|
|
|
// Run is where the actual build should take place. It takes a Build and a Ui.
|
2013-06-12 18:58:02 -04:00
|
|
|
Run(ui Ui, hook Hook, cache Cache) (Artifact, error)
|
2013-06-03 17:44:34 -04:00
|
|
|
|
|
|
|
// Cancel cancels a possibly running Builder. This should block until
|
|
|
|
// the builder actually cancels and cleans up after itself.
|
|
|
|
Cancel()
|
2013-05-10 19:59:28 -04:00
|
|
|
}
|