Pallet 0.6 API documentation

Instantiate an admin-user.

If passed no arguments, then the blobstore service is looked up in the following order: - from a var referenced by pallet.config.admin-user system property - from pallet.config/admin-user if defined - the :admin-user top level key in config.clj

Service specific admin-user values should be specified through a :user key on the :environment for the service.

The other arguments are keyword value pairs. - :identity username or key - :credential password or secret - :extensions extension modules for jclouds - :node-list a list of nodes for the "node-list" provider. - :environment an environment map with service specific values.

Set the admin user based on a config map

Create an admin user form a configuration map.

Set the admin user based on pallet.config setup.

If the pallet.config.admin-user property is defined, and refers to a var then return its value.

Create a blobstore service form a configuration map.

Create a blobstore service from a credentials map. Uses :provider, :identity, :credential and :blobstore-provider, :blobstore-identity and :blobstore-credential. Blobstore keys fall back to the compute keys

Create a blobstore service from ~/.m2/settings.xml propery settings.

Translate compute provider to associated blobstore provider

Instantiate a blobstore service.

If passed no arguments, then the blobstore service is looked up in the following order: - from a var referenced by pallet.config.blobstore-service system property - from pallet.config/blobstore-service if defined - the first service in config.clj - the service from the first active profile in settings.xml

If passed a service name, it is looked up in external configuration (~/.pallet/config.clj or ~/.m2/settings.xml). A service name is one of the keys in the :services map in config.clj, or a profile id in settings.xml.

When passed a provider name and credentials, the service is instantiated based on the credentials. The provider name should be a recognised provider name (see pallet.blobstore/supported-providers to obtain a list of these).

The other arguments are keyword value pairs. - :identity username or key - :credential password or secret - :extensions extension modules for jclouds - :node-list a list of nodes for the "node-list" provider. - :environment an environment map with service specific values.

Create a blobstore service form a configuration map.

Checks to see if pallet.config/service is a var, and if so returns its value.

If the pallet.config.service property is defined, and refers to a var, then return its value.

Instantiate a compute service.

If passed no arguments, then the compute service is looked up in the following order: - from a var referenced by the pallet.config.service system property - from pallet.config/service if defined - the first service in config.clj - the service from the first active profile in settings.xml

If passed a service name, it is looked up in external configuration (~/.pallet/config.clj or ~/.m2/settings.xml). A service name is one of the keys in the :services map in config.clj, or a profile id in settings.xml.

When passed a provider name and credentials, the service is instantiated based on the credentials. The provider name should be a recognised provider name (see pallet.compute/supported-providers to obtain a list of these).

The other arguments are keyword value pairs. - :identity username or key - :credential password or secret - :extensions extension modules for jclouds - :node-list a list of nodes for the "node-list" provider. - :environment an environment map with service specific values.

Compute service from a defpallet configuration map and a list of active profiles (provider keys).

Compute service from ~/.pallet/config.clj. Profiles is a sequence of service keys to use from the :services map.

Checks to see if pallet.config/service is a var, and if so returns its value.

Create a compute service from a credentials map. Uses the :provider, :identity, :credential, :extensions and :node-list keys. The :extensions and :node-list keys will be read with read-string if they are strings.

If the pallet.config.service property is defined, and refers to a var, then return its value.

Create a compute service from maven property settings. In Maven's settings.xml you can define a profile, that contains pallet.compute.provider, pallet.compute.identity and pallet.compute.credential values.

Helper to read compute service properties. Given a config file return the selected service definition as a map.

Top level macro for the pallet config.clj file.

Read pallet configuration from config.clj and services/*.clj files. The files are taken from ~/.pallet or $PALLET_HOME if set.

Instantiate service objects. The service objects are returned in a map with keys as expected by configure or lift.