Blueprint Configsets Lookup Locations

Blueprint configsets are configured within a blueprint in it’s config/configsets.rb file. Example:


configset("httpd", resource: "Instance")

Blueprint configsets are searched for in a few locations. It is similiar to how LOAD_PATH works.

Location Type Description
PROJECT/app/configsets project Your project configsets
PROJECT/vendor/configsets vendor Frozen vendor configsets
BLUEPRINT/app/configsets blueprint The blueprint’s local configsets. Useful for blueprint-specific configset that are not really reusable.
gems folder gem The gems folder is the location where the configset gem is installed. You can use bundle show GEM to reveal the location.
gems folder materialized All blueprint configsets and their dependency configset are materialized as gems.

lono configsets BLUEPRINT command

The lono configsets BLUEPRINT command provides a quick way to find out what configsets are used by a specific blueprint.

$ lono configsets ec2
Configsets used by ec2 blueprint:
| Name  |         Path         |  Type   |  From   |
| httpd | app/configsets/httpd | project | project |

Materialized Configsets

Usually, you add a configset to your Gemfile to make it available for use. Sometimes configsets are not specified by you though. Instead they are inferred by a blueprint or dependency of another configset. These types of configsets are automatically downloaded. These are known as “materialized” configsets.

Pro tip: Use the <- and -> arrow keys to move back and forward.

Edit this page

See a typo or an error? You can improve this page. This website is available on GitHub and contributions are encouraged and welcomed. We love pull requests from you!