cloudinit/datasource/datasource.go

package datasource

type Datasource interface {
	IsAvailable() bool
	AvailabilityChanges() bool
	ConfigRoot() string
	FetchMetadata() ([]byte, error)
	FetchUserdata() ([]byte, error)
	FetchNetworkConfig(string) ([]byte, error)
	Type() string
}
refactor(*): Break apart packages 2014-03-18 09:00:41 -07:00			`package datasource`

			`type Datasource interface {`
datasources: Add support for specifying multiple datasources If multiple sources are specified, the first available source is used. 2014-06-26 15:17:53 -07:00			`IsAvailable() bool`
			`AvailabilityChanges() bool`
refactor(env): Add the config root and netconf type to datasource and env 2014-06-18 11:36:06 -07:00			`ConfigRoot() string`
feat(metadata): Distinguish between userdata and metadata for datasources 2014-06-18 11:58:18 -07:00			`FetchMetadata() ([]byte, error)`
			`FetchUserdata() ([]byte, error)`
datasource: Add FetchNetworkConfig FetchNetworkConfig is currently only used by ConfigDrive to read the network config file from the disk. 2014-08-18 12:20:25 -07:00			`FetchNetworkConfig(string) ([]byte, error)`
Use exponential backoff when fetching user-data from an URL. The user-cloudinit-proc-cmdline systemd unit is responsible for fetching user-data from various sources during the cloud-init process. When fetching user-data from an URL datasource we face a race condition since the network may not be available, which can cause the job to fail and no further attempts to fetch the user-data are made. Eliminate the race condition when fetching user-data from an URL datasource. Retry the fetch using an exponential backoff until the user-data is retrieved. Fixes issue 105. 2014-05-14 22:20:40 -07:00			`Type() string`
refactor(*): Break apart packages 2014-03-18 09:00:41 -07:00			`}`